Configuration Utility on SSH/Telnet

tfrankwoods · 11-30-2010, 09:39 AM

I would like to write a small configuration utility that will act as a daemon on the telnet port and SSH port that will only allow access to, and modification of, specific information in a structure imposed by the utility. How do I set this utility up so that when a user opens a telnet connection (or ssh) to the device, they are actually connected to the utility?

Thanks

TB0ne · 11-30-2010, 09:49 AM

Quote:

Originally Posted by tfrankwoods

I would like to write a small configuration utility that will act as a daemon on the telnet port and SSH port that will only allow access to, and modification of, specific information in a structure imposed by the utility. How do I set this utility up so that when a user opens a telnet connection (or ssh) to the device, they are actually connected to the utility?

Thanks

You don't say anything about the utility, or what it's written in, but a simple way may be to set the program to be the users shell. Instead of BASH, just do a "useradd -s /your/program/name <user name>".

tfrankwoods · 11-30-2010, 10:05 AM

Quote:

Originally Posted by TB0ne

You don't say anything about the utility, or what it's written in, but a simple way may be to set the program to be the users shell. Instead of BASH, just do a "useradd -s /your/program/name <user name>".

The utility is yet to be written and I can write it in C, C++, Perl or any other language. The I/O model is non-GUI, TTY only with basic ANSI text commands (remember the Wyse 50?). The utility will be running on an embedded system that may or may not have bash running.

TB0ne · 11-30-2010, 10:41 AM

Quote:

Originally Posted by tfrankwoods

The utility is yet to be written and I can write it in C, C++, Perl or any other language. The I/O model is non-GUI, TTY only with basic ANSI text commands (remember the Wyse 50?). The utility will be running on an embedded system that may or may not have bash running.

You don't need bash running. If your program is set to be the users shell, when the user logs in, your program starts, and runs with the users permissions. So again, just set your program to be the 'shell' of your user(s), and when they log in, that's what they'll see.