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
AES Encryption instead of 3DES #498
Conversation
Update README.md to correct 'thier' to 'their'
Added support for FamilyShield DNS from OpenDNS/CISCO
Previous commits removed the duplicate cn option all together, this adds a comment to inform users of their options/choice.
Added FamilyShield DNS server as option
This sounds like a no-brainer; I like this! |
Added fix to prevent DNS leak on Windows 10
DNS leak fix in server_config.txt
First off, thanks for contributing! I think we were using 3DES for compatibility with iPhones or something. A quick seach through the open issues found #171. |
@redfast00 AES128 works fine with iPhones (AES256 works too). |
@orazioedoardo thanks. I can now merge this, but this PR contains a lot of unrelated commits and I don't think it's been tested yet. Any input @cfcolaco ? |
@redfast00 think this PR is actually cool ... will merge into test all commits to master that are ahead of Test branch! so should be fairly safe to merge this PR into test ( as it is ) =)
|
Changed permission bits on text files.
Great for readable naming conventions.
Changing name validation regex to allow dashes
so are we merging this, i'm all for it |
Merge commits
I was wondering why in the script the encryption method 3DES is used. This algorithm is long outdated and deprecated. By simply choosing the AES with 128 bits key length the saved key would be safer for being brute-forced. Therefore it would be a security bonus without changing much.