Add tls_ciphers option to allow specifiying custom ciphers list
#113
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is needed in particular when running pagekite.py on debian >=11 where the cipherlist must be set to `DEFAULT@SECLEVEL=1` to allow current (at the time of writing this) libpagekite embedded backends to connect, as these use TLSv1 even on platforms which do support TLSv2 and later.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is needed in particular when running pagekite.py as a frontend server on debian >=11, where the cipherlist must be set to
DEFAULT@SECLEVEL=1to allow current (at the time of writing this) libpagekite embedded backends to connect, as these use TLSv1 even on platforms which do support TLSv2 and later.Also, this PR adds a help text for
tls_legacy(which existed, but was not listed in help so far)