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]

Re: Problem with scp and SSH on Arch Linux

Subject: Re: Problem with scp and SSH on Arch Linux
Date: Mon, 18 Jun 2007 08:21:04 -0400
On Thu, Jun 14, 2007 at 10:08:27PM +0200, Stijn Segers wrote:
I tried to use scp today, and got this weird behaviour:

[stijn@hephaistos ~]$ scp -2 .ssh/id_rsa-olympos2.pub \
stijn@olympos:/home/stijn/.ssh/id_rsa-olympos2.pub
Enter passphrase for key '/home/stijn/.ssh/id_rsa-olympos': 
Arch Linux (Duke) 2.6.21.4-cks-server 
[stijn@hephaistos ~]$

Your .bashrc (or analogous file for your login shell) on the remote
system is writing stuff to stdout.  You need to stop it from doing that.
If you still want it to do that when you open a regular interactive
shell (e.g. an xterm), then wrap all your output-producing commands in
a test, such as this:

if test -t 1; then
  uname ....
  stty ...
  echo ...
fi

The exact details will depend on just what you've got in the .bashrc.

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