Re: Inbound SSH allowed to be used with Code for i and other tools ? -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Hello Richard,

Am 31.10.2024 um 14:15 schrieb Richard Schoen <richard@xxxxxxxxxxxxxxxxx>:

Thanks for the reply Patrik.

I didn't realize there were all those extra things you can add to an authorized_keys file.

Glad to have given you new ideas!

OpenSSH is very feature-rich, but most of that stuff is entirely optional and thus often not known

Interesting about not allowing interactive shell to spawn.

Yes, indeed! I'm using this functionality to have a secure channel for good old plain text UUCP, spawning the UUCP login task "uucico" directly.

https://en.wikipedia.org/wiki/UUCP

(If you know SNADS, UUCP smells suspiciously similar.)

What would be really cool is if there were exit points that could be monitored to limit which commands could be executed.

Since IBM put together this version of OpenSSH why not make it better and more securable.

Probably a wish that won't come true, but worth pontificating.

Well, I've read there's an ideas site for meaningful proposals. :-)

:wq! PoC

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.