[SOLVED]
Sometimes the shortest responses are the most profound. Thanks to everyone
who contributed.
Ben, you saved my sanity, my hours, in some ways my life.
Although I'd upgraded nodejs to version 5.10 under the current user (AWS
ec2-user), this latest version was installed to
Did you also update the -ciphers option in your openssl s_client command?
--
Job board: http://jobs.nodejs.org/
New group rules:
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
---
You
On Mon, Apr 25, 2016 at 11:34 AM, Eugene Williams
wrote:
> Thanks again for the suggestion Johnny.
>
> I updated the server configuration with the new cipher suite. The final
> setup is:
>
> var ciphersall =
>
Thanks again for the suggestion Johnny.
I updated the server configuration with the new cipher suite. The final
setup is:
var ciphersall =
Yes, sorry for my ramblings, it was late and there was information I
totally left off that would have made the last part of the comment make
actual sense..
The end of my comment is the important part about changing your cipher
suite.
You see, you used the option "-cipher
Thanks for the comment Johnny. It's a good idea to install wireshark. I'll
do that and run some tests. Changing the "honorCipherOrder" parameter had
no effect.
-Eugene
On Thursday, April 21, 2016 at 9:46:24 PM UTC-7, johnny somethingerman
wrote:
>
> I'm not an SSL expert, and probably only a
I'm not an SSL expert, and probably only a few people on this list are, but
my hunch is you are doing something wrong with your config and the
"honorCipherOrder: true" property of your opetions objet is causing it to
show up in node.js when it didn't in openssl s_server.
That hex blob the