Like the subject says, I'm using PuTTY to connect to a server with
private login and password. Has been working fine for the last few
weeks but since Friday i have just being t/o'ing to the server. Any1
have any idea what could have changed somewhere so i can fix it.
Thanks in advance.

Luke

I logged in through a command shell on a Linux system and entered a command:

nohup rsync ... >my.log &2>1

I expected that after the command issue the command prompt

ml@server [/]#

gets visible again.

But the ssh terminal is blocked as if I would have NOT entered "nohup".

Why is the rsync command still running in foreground although I prepended the command with "nohup" ?

Matthew

Wymień swojego Windowsa na darmowe oprogramowanie opensource i zapomnij
o wykupywaniu licencji. To naprawdę wielkie oszczędności. Zachęcamy do
współpracy.
www.emerge.pl

I have a script running nightly, logs into a FTP server with PSFTP, &
downloads a monsterous directory w/ a ton of sub directories so I have
local backups.

mget -r public_html

Is there a way to do this large directory backup but specify to only
get certain file types? i.e. no images

Or maybe there is a better tool for doing this? Any help is
appreciated :)

I have an account called mdmbuild on my machine that does not have a
password. It's a headless account. I have ssh public and private keys
for the account. The public keys are already there on the machine I
want to log on to.
But the problem is the remote machine is not accepting my private keys
as they were generated on a different machine.

Say keys were generated on saturn and public keys copied to venus. My
mars machine has the private keys but venus won't accept it as it has
public keys generated on saturn. Is there any way I can login on venus
with the keys
I have got? mdmbuild does not have a password. The only way to login
is with the keys.

In regards to this giant fuckup:

http://www.ubuntu.com/usn/usn-612-2

What exactly is the impact of this vulnerability?

1) Does it let a attacker, who has listening ability on a local
network, to intercept keys? (ie reduce security of SSH to that of telnet)

2) Does it allow an attacker, who does NOT have a listening ability,
to log on to remote machines using known weak keys? (ie brute force a
fully remote machine)

Just what is the extent of this sad story?

As I use ssh and keys a lot, this means that I had to spend a lot of
time fixing all the trust network that I have. I think that I am done,
finally.

--
Due to extreme spam originating from Google Groups, and their inattention
to spammers, I and many others block all articles originating
from Google Groups. If you want your postings to be seen by
more readers you will need to find a different means of
posting on Usenet.
http://improve-usenet.org/

Currently, SSH has 2 ways to do address binding for port forwarding:

1. The SSH encrypted connection itself can be bound to a specific IP address
with the -b command line option (BindAddress in the config file).

2. Port forwarding can bind to a specific address on the listening host,
the local host for -D and -L (DynamicForward and LocalForward), or the
remote host for -R (RemoteForward).

What I would like to have is an option to bind the source address of the
outbound connections being forwarded.

An example with -L (LocalForward) would work like this. The ssh client will
listen to the port and optionally also the specified address on the local host.
For each connection coming in to that port, a connection is made from the
remote host to the destination host and port specified. What my suggested
option would do is specify what address that remote-to-destination connection
would come from. It would only make sense to use addresses configured on a
working interface on the remote machine.