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

Edit digest separately despite GCM cipher #74

Closed
keeshux opened this issue Apr 27, 2019 · 0 comments
Closed

Edit digest separately despite GCM cipher #74

keeshux opened this issue Apr 27, 2019 · 0 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@keeshux
Copy link
Member

keeshux commented Apr 27, 2019

I also noticed that if I change the 'Cipher' to CBC, the 'Authentication' type chosen is what the debug log lists under 'Digest' when switching the Cipher from CBC to GCM. E.g., If I choose AES-256-CBC and HMAC-SHA1, change Cipher to AES-256-GCM, and attempt to connect, then the Debug log lists Digest: HMAC-SHA1.

Digest is also used for --tls-auth, so leave it editable regardless of the cipher.

@keeshux keeshux changed the title Edit digest separately despite of GCM cipher Edit digest separately despite GCM cipher Apr 27, 2019
@keeshux keeshux self-assigned this Apr 27, 2019
@keeshux keeshux added the bug Something isn't working label Apr 27, 2019
@keeshux keeshux added this to the 1.6.0 milestone Apr 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant