What values should be used for SELinux (pam_selinux) "context" and "level"? about shellinabox

[GoogleCodeExporter]

ShellInABox does not have support for SELinux, and I cannot find any good
documentation on how to add it.

So, your best bet would be to ask RedHat to officially include ShellInABox in 
Fedora.
Presumably, they know how to configure programs for use with SELinux. I'd 
certainly
accept any patches that they would like to submit.

In the meantime, avoiding calls to /bin/login will work around the problem that 
you
are seeing. You could launch ShellInABox as:

  shellinaboxd -t -s '/:AUTH:HOME:/bin/bash'

This won't give you exactly the same environment that /bin/login would set up, 
but
maybe it is close enough for your purposes.

For now, I changed the status of the issue to "WontFix". If any new information 
on
how to configure SELinux does become available, I can reopen the issue.

Original comment by [email protected] on 17 Jun 2009 at 1:11

• Changed state: WontFix

[GoogleCodeExporter]

While I still don't know what RedHat specific magic is necessary to make 
shellinaboxd 
work on Fedora, there now is a viable work-around available, if you check out 
the most 
recent code from SVN.

Instead of calling /bin/login, which seems to cause problems on Fedora, you can 
tell 
shellinaboxd to connect to your local SSH server. Just pass it the command line 
"--
service /:SSH" and things should start working.

Original comment by [email protected] on 30 Jul 2009 at 7:01

[GoogleCodeExporter]

I now added a README.Fedora file to the subversion tree. It gives some more 
hints on 
how to configure ShellInABox for use on Fedora.

Original comment by [email protected] on 23 Nov 2009 at 4:59

[GoogleCodeExporter]

why running `shellinaboxd -t -s '/:AUTH:HOME:/bin/bash'` gives me
Cannot look up user id "AUTH"?

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