Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

All of my changes #71

Open
wants to merge 70 commits into
base: master
Choose a base branch
from
Open

All of my changes #71

wants to merge 70 commits into from

Conversation

afcady
Copy link

@afcady afcady commented Oct 9, 2022

I'm pushing the rest of my changes to tuntox that I didn't push earlier when I wrote them, for whatever reasons. I think I didn't want to expose the LOG_IP_ADDRESS functionality since it requires my patches to c-toxcore so I stopped making PRs after adding that feature. But it's disabled by #ifdef anyway. Most of this stuff is a few years old, but I made some commits today.

I see that you've added some commits too and not merged my previous PRs. So maybe these further commits will never be merged. Either way I'm posting this just so you (and/or others) are aware of this development.

There is a new script toxish that edits ssh_config so one can use tuntox with a simple ssh command, and some improvements to the old scripts too. There are improvements and fixes to the build process. There are minor bug fixes, and lots of cleanups and simplifications.

I see there are some mistakes and reverted commits that should be edited out/squashed with rebase. Not really a clean PR here. I actually wouldn't mind cleaning it up or even would prefer to erase my mistakes before they are merged here, but that may be moot so I'm just sending it immediately.

Once again, thanks for making tuntox!

Andrew Cady added 30 commits August 19, 2020 01:29
This produced a nonsensical warning in client mode.

It is also redundant as there is this line:

log_printf(L_INFO, "Server in ToxID whitelisting mode - only clients listed with -i can connect");
The client and server blocks were nearly identical.  Now they share code.

Both client and server now call memset() on tox_printable_id.

The distinct client message "Generated Tox ID: %s\n" was not preserved;
both client and server will say "Using Tox ID: %s\n" which is more
accurate (Tox ID might be persistent with -C).
This relies on a patched c-toxcore. For that reason, it is disabled by
an #ifdef.
Renamed some variables. Improved clarity of conditional.
The hostname "*" is treated as a wildcard.

Port 0 is treated as a wildcard.

Closes gjedeer#56
This reflects the fact that the rules constitute a whitelist.
The rules are reloaded as needed upon every connection.
@sonarcloud
Copy link

sonarcloud bot commented Oct 9, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@gjedeer
Copy link
Owner

gjedeer commented Oct 11, 2022

Hey,

Thank you for the PRs. They're so big they require a lot of time to review and merge. Some of the commits were OK, some I didn't want to merge, and it was too much time to cherry pick all of them - so I did not merge the PRs.

I hope to eventually review your code but if you make future contributions, please please submit one functionality per PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants