ljd3000 / shellinabox

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

HTTPS does not work on Mac OSX 10.6.x #110

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.  ./configure
2.  make
3.  mkdir -p certs && sudo ./shellinaboxd -d -p 443 -u user -g staff -c certs/

What is the expected output? What do you see instead?
A shellinabox HTTPS server at https://localhost. Instead you only get a HTTP 
server.   Command produces"Ignoring certificate directory, as SSL support is 
unavailable".

What version of the product are you using? On what operating system?
Mac OSX 10.6.4.

Please provide any additional information below.

Original issue reported on code.google.com by lpsan...@gmail.com on 18 Jan 2011 at 9:21

GoogleCodeExporter commented 8 years ago
HTTPS/SSL is broken because PAM is broken (note output in configure) on OSX.  
This CAN BE FIXED!!!  The fix is to do this:
./configure --disable-runtime-loading --disable-pam
make

--disable-runtime-loading by itself causes SIAB to try to load the broken PAM 
(which may be just a define or code issue on OSX).

Original comment by lpsan...@gmail.com on 18 Jan 2011 at 9:24

GoogleCodeExporter commented 8 years ago
Looks like several OSX build problems exist.

Original comment by beewoo...@gmail.com on 31 Mar 2012 at 10:23

GoogleCodeExporter commented 8 years ago
Need a little help getting shellinabox with ssl support.  One solution involves 
building it from source.
http works but https does not.

# uname -a
Linux linuxpc 3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:58:01 UTC 2014 
i686 i686 i686 GNU/Linux
# 
# shellinaboxd --version
ShellInABox version 2.10 (revision 239)
# 
# /usr/local/bin/shellinaboxd --background --port=80 -v -c /var/lib/shellinabox/
Ignoring certificate directory, as SSL support is unavailable
Command line: /usr/local/bin/shellinaboxd --background --port=80 -v -c 
/var/lib/shellinabox/
Listening on port 80
#

Original comment by vdo...@gmail.com on 26 Oct 2014 at 7:31

GoogleCodeExporter commented 8 years ago
How did you './configure' siab?  How did you build your certs?  You have a 
working PAM install on your linux box? I use the following to build certs:

openssl genrsa -des3 -out server.key 1024
openssl req -new -key server.key -out server.csr
cp server.key server.key.org
openssl rsa -in server.key.org -out server.key
openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt
cat server.crt server.key > certificate.pem

Original comment by lpsan...@gmail.com on 26 Oct 2014 at 4:28