ssl support doesn't work on openbsd 4.4 about shellinabox

[GoogleCodeExporter]

Ups I forgot to mention the port, it uses the 1001/tcp

Original comment by [email protected] on 24 May 2009 at 12:58

[GoogleCodeExporter]

This was a result of OpenBSD not being able to automatically load 
"libcrypto.so" as
dependency of "libssl.so". No idea, why that doesn't work on OpenBSD. I now 
fixed the
code to link against both libraries explicitly (when run-time loading has been
disabled in "./configure"), or to load "libcrypto.so" with "dlopen()", if 
resolving
symbols from "libssl.so" otherwise fails.

The upshot is, that everything should work correctly now, if you build the 
latest SVN
release on OpenBSD.

PAM support is still not available, but that seems to be a short-coming of 
OpenBSD.
So, you will not be able to use the "AUTH" token in any service definitions. Use
"LOGIN" and run as "root" instead, or provide your own authentication module in 
your
web server; for the latter, you should use the "--cgi" option.

I also noticed that on OpenBSD, "shellinaboxd" cannot retrieve symbolic group 
names.
This appears to be a permission problem. Just use numeric group names instead.

Sorry for all these caveats when running on OpenBSD. That OS is just a little 
more
restrictive and tends to make different design choices than other operating 
systems.
So, it is sometimes not possible to support every feature. If you are aware of
OpenBSD-specific work-arounds, please let me know, though.

Original comment by [email protected] on 25 May 2009 at 6:25

• Changed state: Fixed