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. |

| Subject: | Re: Propagating terminal settings |
|---|---|
| Date: | Thu, 08 Nov 2007 08:09:42 +0100 |
Hi, Thanks for the response.
Sipos,
Three options: 1) A short 'expect' script
This seems easiest for me. I think I will do this for now.
2) Modify your login script of the target machine to detect a login
from your primary PC (env SSH_TTY, SSH_CLIENT, etc.).
3) Write your own interface to set the terminal environment.
I like #2 the best.
William Estrada MrUmunhum@popdial.com Mt-Umunhum-Wireless.net ( http://Mt-Umunhum-Wireless.net ) Ymessenger: MrUmunhum
Sipos wrote:
I can fix this by doing stty erase ^? to change the setting after I log in but it is impractical to do this every time. Is it possible to get ssh to propagate the terminal settings from the terminal it is run in to the one started on the remote machine?
Cheers, Nick
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Public Key Format conversions, kodumuri |
|---|---|
| Next by Date: | tput error, Christian Hennig |
| Previous by Thread: | Re: Propagating terminal settings, william estrada |
| Next by Thread: | Public Key Format conversions, kodumuri |
| Indexes: | [Date] [Thread] [Top] [All Lists] |