> On Apr 16, 2015, at 10:04, Chris Ross <[email protected]> wrote:
>> On Apr 16, 2015, at 09:51, Chris Ross <[email protected]> wrote:
>>> On Apr 16, 2015, at 03:01, Jan Just Keijser <[email protected]> wrote:
>>> One thing you could try is to run the underlying openssl command on both
>>> client and server:
>>> server:
>>> openssl s_server -msg -CAfile ca.crt -cert server.crt -key server.key
>>> client:
>>> openssl s_client -connect <server-IP>:4433
>>>
>>> (adjust ca.crt and server.{crt,key} to your setup).
>>> The server should print the list of shared ciphers.
>>
> Interesting. While googling around for openssl errors saying “no shared
> cipher", rather than openvpn errors, I found someone suggesting a similar set
> of commands for debugging an application programming problem. But, they used
> “-tls1” on each side. When I retried your commands above adding “-tls1” to
> the client side, it established a connection successfully […]
A few more trials showed that adding “-tls1” to the s_client command caused a
successful connection, so did “-no_ssl2”. I don’t understand the full nature
of the problem, but this sounds like something I should be able to configure
openvpn to enact.
And I’m not sure how much I care, but I might want better than RC4-MD5
anyway, right?
- Chris
------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Openvpn-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openvpn-users
