Both look interesting, but they can't be started from inetd - can they? If one uses KNC, one needs to write a wrapper around it that it is started again when it exits?
KR, Oliver Am 03.12.2012 um 19:37 schrieb Booker Bense <[email protected]>: > Remctl is also a great solution to the "kerberized" inetd problem. > > http://www.eyrie.org/~eagle/software/remctl/ > > > On Sat, Dec 1, 2012 at 2:40 PM, Oliver Loch <[email protected]> wrote: > Hello, > > while playing around with some ideas on sending notifies from/to a machine, I > started playing with inetd and ended up missing a Kerberos wrapper. > > I'm not even sure if it can be done with Kerberos, but the idea is to have a > tool similar to "stunnel" ( https://www.stunnel.org/index.html ), that can be > "intercepted" into the data stream between the executed command of inetd and > the client on the other end. Besides providing authentication (and > authorization), it could also provide encryption, like Kerberos/GSSAPI does > in some OpenLDAP scenarios. > > KR, > > Oliver > > > ________________________________________________ > Kerberos mailing list [email protected] > https://mailman.mit.edu/mailman/listinfo/kerberos > >
________________________________________________ Kerberos mailing list [email protected] https://mailman.mit.edu/mailman/listinfo/kerberos
