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

READY: Use well-known cipher list #126

Merged
merged 1 commit into from
Jan 16, 2016

Conversation

lukebakken
Copy link
Contributor

Fixes #104 (CLIENTS-640)

To test:

  • Set up your Riak 2.1.3 devrel to use security:
git clone git://github.com/basho/riak-client-tools
cd riak-client-tools
devrel/setup-dev-cluster -s -p PATH/TO/riak/dev
  • Clone riak-nodejs-client and, on master branch:
npm install
grunt security
  • Check error.log from your first devrel node. You'll see the following:
no function clause matching tls_v1:enum_to_oid(28)
  • Check out the fixes/lrb/clients-640-cipher-list branch
  • Re-run grunt security and tests should pass

@lukebakken lukebakken changed the title Use well-known cipher list READY: Use well-known cipher list Jan 15, 2016
@lukebakken lukebakken added this to the riak-nodejs-client-2.1.1 milestone Jan 15, 2016
@@ -157,9 +160,9 @@ RiakConnection.prototype._receiveHealthCheck = function(data) {

RiakConnection.prototype._receiveStartTls = function(data) {
logger.debug("[RiakConnection]: receive StartTls response");
this._connection.removeListener('data', this._boundReceiveStartTls);
Copy link

Choose a reason for hiding this comment

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

So you are now removing the listener no matter what?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It makes more sense to do it this way but there is no need to change this for just a bug fix. I'll revert it.

@hazen
Copy link

hazen commented Jan 15, 2016

@lukebakken Had some problems setting up the cluster, so here's a tweak: basho/riak-client-tools#2

@hazen
Copy link

hazen commented Jan 16, 2016

Works fine, now that I know the secret incantation

@hazen
Copy link

hazen commented Jan 16, 2016

👍 6aa7bf3

@lukebakken lukebakken force-pushed the fixes/lrb/clients-640-cipher-list branch from 6aa7bf3 to 59bf8d4 Compare January 16, 2016 15:33
Add known good list of ciphers for Riak SSL and Erlang R16
@lukebakken lukebakken force-pushed the fixes/lrb/clients-640-cipher-list branch from 59bf8d4 to fc8b4b2 Compare January 16, 2016 16:10
lukebakken added a commit that referenced this pull request Jan 16, 2016
@lukebakken lukebakken merged commit 1bcf344 into master Jan 16, 2016
@lukebakken lukebakken deleted the fixes/lrb/clients-640-cipher-list branch January 16, 2016 16:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Connect using authentication - Cipher list not correct #104 [JIRA: CLIENTS-640]
2 participants