search

mattytravisza / shellinabox

Automatically exported from code.google.com/p/shellinabox
Other
0 stars 0 forks source link

ssl cert not respected: ssl_error_no_cypher_overlap #66

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Install verisign intranet certificate
2. Access shellinaboxd via cgi
3.

What is the expected output? What do you see instead?
I would expect to see the web terminal

What version of the product are you using? On what operating system?
Tried latest release, as well as svn trunk with the same output.

Please provide any additional information below.
All implementations work provided I a.) Disable SSL, b.) use a self signed
cert.

Original issue reported on code.google.com by tcp...@gmail.com on 14 May 2010 at 7:49

GoogleCodeExporter commented 9 years ago 
I was able to get this to work, I believe it's because I had not appended the
intermediate cert to the certificate.pem

Original comment by tcp...@gmail.com on 14 May 2010 at 8:18

GoogleCodeExporter commented 9 years ago 
Hi, i am on a debian lenny system and I have the same error. I tried both .deb 
precompiled package and .deb self-compiled package from source.
Th certificate.pem is in the /var/lib/shellinabox directory self-generated by 
installation. What can I do?

Original comment by mgiulian...@gmail.com on 30 Jun 2010 at 11:09

GoogleCodeExporter commented 9 years ago 
Hi, same error here too, wich changes do i need to do to certificate.pem to get 
this to work?

Original comment by erus.ilu...@gmail.com on 23 May 2011 at 3:34

GoogleCodeExporter commented 9 years ago 
I'm running the precompiled armel .deb on a Squeeze server and the precompiled 
amd64 .deb on my Testing/Wheezy laptop - the armel version works fine, but even 
connecting from the same machine (https://localhost:4200/) I get that same 
error.

Original comment by jonathan...@gmail.com on 6 Jun 2011 at 9:32

GoogleCodeExporter commented 9 years ago 
I can't get this working... Same thing, and it works if I disable SSL, but I 
really need security. On Archlinux.

Can you say precisely what you did?

Original comment by feilen1...@gmail.com on 18 Jul 2011 at 8:08

GoogleCodeExporter commented 9 years ago 
Am using shell-in-a-box a wile already and using an older cert, auto generated 
by shellinaboxd - it works fine. Not sure if all certs generated after some 
point in the past fail. Tried an own certificate - can't bring it to run. 
Anyone else still fiddling around on that ?

Original comment by oli.schm...@gmail.com on 6 Dec 2011 at 10:03

GoogleCodeExporter commented 9 years ago 
Same problem, until I opened the file "certificate.pem", and changed:

-----BEGIN PRIVATE KEY-----
MIICdgIBADANBgkqhkiG9w0BAQEFAASCAmAwggJcAgEAAoGBALCtdQCfbYAOM+35
...
-----END PRIVATE KEY-----

in:

-----BEGIN RSA PRIVATE KEY-----
MIICdgIBADANBgkqhkiG9w0BAQEFAASCAmAwggJcAgEAAoGBALCtdQCfbYAOM+35
...
-----END RSA PRIVATE KEY-----

Now it's working fine !

Original comment by stefano....@gmail.com on 24 Dec 2011 at 2:31

GoogleCodeExporter commented 9 years ago 
https://github.com/jayschwa/shellinabox/commit/28ff61e1c6b622c565ff7d1b5fbeba306
e937598

I have made an update that seems to resolve this issue for me.

Original comment by Jayschwa on 2 Feb 2012 at 6:28

GoogleCodeExporter commented 9 years ago 
Patch applied for 2.11.

Original comment by beewoo...@gmail.com on 31 Mar 2012 at 9:36