-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Wrong cypher name in docs #2141
Comments
tsg
pushed a commit
to tsg/beats
that referenced
this issue
Aug 1, 2016
Closes elastic#2141. The AES128 and AES256 need a dash in their name, so AES-128 and AES-256 is what the code expect.
urso
pushed a commit
that referenced
this issue
Aug 1, 2016
Closes #2141. The AES128 and AES256 need a dash in their name, so AES-128 and AES-256 is what the code expect.
tsg
added a commit
to tsg/beats
that referenced
this issue
Aug 1, 2016
Closes elastic#2141. The AES128 and AES256 need a dash in their name, so AES-128 and AES-256 is what the code expect.
Merged
tsg
added a commit
to tsg/beats
that referenced
this issue
Aug 1, 2016
Closes elastic#2141. The AES128 and AES256 need a dash in their name, so AES-128 and AES-256 is what the code expect.
tsg
added a commit
to tsg/beats
that referenced
this issue
Aug 1, 2016
Closes elastic#2141. The AES128 and AES256 need a dash in their name, so AES-128 and AES-256 is what the code expect.
urso
pushed a commit
that referenced
this issue
Aug 1, 2016
urso
pushed a commit
that referenced
this issue
Aug 1, 2016
urso
pushed a commit
that referenced
this issue
Aug 1, 2016
11 tasks
leweafan
pushed a commit
to leweafan/beats
that referenced
this issue
Apr 28, 2023
Closes elastic#2141. The AES128 and AES256 need a dash in their name, so AES-128 and AES-256 is what the code expect.
leweafan
pushed a commit
to leweafan/beats
that referenced
this issue
Apr 28, 2023
Closes elastic#2141. The AES128 and AES256 need a dash in their name, so AES-128 and AES-256 is what the code expect.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A bug report coming via the sales team says that on the cyphers listed on this page we write
ECDHE-ECDSA-AES256-GCM-SHA384
when actually correct isECDHE-ECDSA-AES-256-GCM-SHA384
(note the extra dash inAES-256
).The text was updated successfully, but these errors were encountered: