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

do not advertise RC4 #223

Merged
merged 1 commit into from
Jan 15, 2015
Merged

do not advertise RC4 #223

merged 1 commit into from
Jan 15, 2015

Conversation

hannesm
Copy link
Member

@hannesm hannesm commented Jan 12, 2015

disable RC4 by default (users who need RC4 can tweak the configuration)

fixes #8

disable RC4 by default (users who need RC4 can tweak the configuration)

fixes #8
@@ -39,8 +39,6 @@ module Ciphers = struct
`TLS_RSA_WITH_AES_256_CBC_SHA ;
`TLS_RSA_WITH_AES_128_CBC_SHA ;
`TLS_RSA_WITH_3DES_EDE_CBC_SHA ;
`TLS_RSA_WITH_RC4_128_SHA ;
`TLS_RSA_WITH_RC4_128_MD5
]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, this is a bit of a lie; removing ciphers we support from the list of supported ciphers is, um... yeah.

Nothing that couldn't be helped by a little rename and little rethink of what this list exactly means, or what potential similar lists defined next to it could mean.

pqwy added a commit that referenced this pull request Jan 15, 2015
@pqwy pqwy merged commit e7b6259 into master Jan 15, 2015
@pqwy pqwy deleted the no-rc4 branch January 15, 2015 00:24
@pqwy
Copy link
Contributor

pqwy commented Jan 15, 2015

Evil, evil RC4.

@hannesm
Copy link
Member Author

hannesm commented Jan 15, 2015

I agree we need multiple sets here - of what the protocol implementation implements and what we're happy to use by default..

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

Successfully merging this pull request may close these issues.

RC4 security in TLS
2 participants