Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]

Configuring SSH to use our own CLI application in an embedded Linux syst

Subject: Configuring SSH to use our own CLI application in an embedded Linux system
Date: Sun, 26 Mar 2006 15:45:38 +0200
Hello,

I have a question about configuring SSH to connect to a specific CLI
application. This is for an Embedded Linux project.

A telnet server can be configured to run a given application (By default
it is 'login', but you can set it to whatever you want).
I could not find any way to configure OpenSSH in such a manner. All I
could find is a configuration flag 'UseLogin' which tells it to run
login, but it is not sufficient to what I want.

I want SSH to:
1. Always run my CLI application, and ignore any 'command' that the
client wanted to run.
2. Not check the user home directory for anything. My CLI application
will do the authentication using a simple user-name + password scheme
against a local user DB (The users in that DB are NOT Linux accounts). 
3. Since the SSH client asks the user for a user-name before even
connecting to the SSH server, and it passes this user-name to the SSH
server, I want the SSH server to pass this user-name to my CLI
application so that the user will not have to type the user-name again
for my CLI application.

Basically, I want SSH to encrypt the traffic for protection against
eavesdropping, but I do not want it's client-authentication features
(Since the logged-in users do not exist as Linux accounts anyway).

I would imagine that many embedded Linux systems with SSH support would
want to use SSH this way, yet I could not find any method of configuring
OpenSSH to function in such a way. Maybe I need to tweak the OpenSSH
sources ? Use a different SSH solution (i.e. not OpenSSH) ? What do
other Embedded-linux systems do ?

Thanks a lot, Oren.


<Prev in Thread] Current Thread [Next in Thread>