Christian Laursen wrote:
It is also worth taking a look at the ProxyCommand option.
For the case above something like this should be put in ~/.ssh/config:
Host your.own.host-tunneled
HostKeyAlias your.own.host
ProxyCommand ssh [EMAIL PROTECTED] nc your.own.host 22
The you can just do ssh
Peter Boosten [EMAIL PROTECTED] writes:
No, I was more thinking of:
ssh -L :your.own.host:22 [EMAIL PROTECTED]
and then open a new shell:
scp -P the-file-you-want-to-copy [EMAIL PROTECTED]:
This works easiest with agent forwarding, but I guess any
authentication will do.
It is
On Thursday 08 May 2008 05:50:59 Steve Bertrand wrote:
ssh stream tcp nowait/20/4/10 root /usr/sbin/sshd sshd -i
into /etc/inetd.conf set a limit of
* 20 overall ssh connections
* 4 connection attempts per minute
* at most 10 connections from a single IP
This works very
Hi,
On May 7, 2008, at 01:11 , Gilles wrote:
Hello
I'm a bit tired of people trying to break into SSH:
May 6 16:59:23 freebsd sshd[24649]: Invalid user agatha from
195.43.9.246
May 6 16:59:26 freebsd sshd[24651]: Invalid user cristie from
195.43.9.246
May 6 16:59:29 freebsd sshd[24653]:
** At 07:33 +0200 on 05/08/2008, Peter Boosten wrote:
Vince Sabio wrote:
Note if you choose to do this: scp'ing files becomes a four-step
process (i.e., scp file(s) to intermediate server, log in to
intermediate server, scp to destination server, delete file(s) from
intermediate server).
Vince Sabio wrote:
** At 07:33 +0200 on 05/08/2008, Peter Boosten wrote:
Vince Sabio wrote:
Note if you choose to do this: scp'ing files becomes a four-step
process (i.e., scp file(s) to intermediate server, log in to
intermediate server, scp to destination server, delete file(s) from
On May 8, 2008, Mel wrote:
because:
for FILE in */*.[ch]; do scp ${FILE} host:/backup; done
is quicker to write then setup tunnels.
How about scp */*.[ch] host:/backup?
___
freebsd-questions@freebsd.org mailing list
On May 8, 2008, Norbert Papke wrote:
On May 8, 2008, Mel wrote:
because:
for FILE in */*.[ch]; do scp ${FILE} host:/backup; done
is quicker to write then setup tunnels.
How about scp */*.[ch] host:/backup?
To answer my own silly question, the above doesn't preserve paths. Anyway, as
On Thu, May 08, 2008 at 07:33:13AM +0200, Peter Boosten wrote:
Vince Sabio wrote:
Note if you choose to do this: scp'ing files becomes a four-step process
(i.e., scp file(s) to intermediate server, log in to intermediate server,
scp to destination server, delete file(s) from intermediate
Valeriu Mutu wrote:
On Thu, May 08, 2008 at 07:33:13AM +0200, Peter Boosten wrote:
Vince Sabio wrote:
Note if you choose to do this: scp'ing files becomes a four-step process
(i.e., scp file(s) to intermediate server, log in to intermediate server,
scp to destination server, delete file(s)
On Wednesday 07 May 2008 06:16:19 Norbert Papke wrote:
On May 6, 2008, Gilles wrote:
Is there a way to configure SSHd, so that the wait time between login
attempts increases after X failed tries?
I run sshd via inetd rather than as a stand-alone daemon. inetd provides
optional rate
On May 7, 2008, Mel wrote:
On Wednesday 07 May 2008 06:16:19 Norbert Papke wrote:
On May 6, 2008, Gilles wrote:
Is there a way to configure SSHd, so that the wait time between login
attempts increases after X failed tries?
I run sshd via inetd rather than as a stand-alone daemon.
ssh stream tcp nowait/20/4/10 root /usr/sbin/sshd sshd -i
into /etc/inetd.conf set a limit of
* 20 overall ssh connections
* 4 connection attempts per minute
* at most 10 connections from a single IP
This works very well on a personal server, not sure how it scales up.
So if I copy
** At 09:59 -0800 on 05/06/2008, Beech Rintoul wrote:
On Tuesday 06 May 2008, David Kelly said:
On Tuesday 06 May 2008, Gilles said:
Is there a way to configure SSHd, so that the wait time between
login attempts increases after X failed tries?
Depending on how you use ssh from
Vince Sabio wrote:
Note if you choose to do this: scp'ing files becomes a four-step process
(i.e., scp file(s) to intermediate server, log in to intermediate
server, scp to destination server, delete file(s) from intermediate
server). Still worth it, though.
Never thought of port
Hello
I'm a bit tired of people trying to break into SSH:
May 6 16:59:23 freebsd sshd[24649]: Invalid user agatha from
195.43.9.246
May 6 16:59:26 freebsd sshd[24651]: Invalid user cristie from
195.43.9.246
May 6 16:59:29 freebsd sshd[24653]: Invalid user number from
195.43.9.246
May 6
On Tuesday 06 May 2008, Gilles said:
Hello
I'm a bit tired of people trying to break into SSH:
May 6 16:59:23 freebsd sshd[24649]: Invalid user agatha from
195.43.9.246
May 6 16:59:26 freebsd sshd[24651]: Invalid user cristie from
195.43.9.246
May 6 16:59:29 freebsd sshd[24653]:
On Tue, May 06, 2008 at 09:31:15AM -0800, Beech Rintoul wrote:
Is there a way to configure SSHd, so that the wait time between
login attempts increases after X failed tries?
Not that I know of. You should look into denyhosts (in the ports) it
works well and even has a RBL feature to
On Tuesday 06 May 2008, David Kelly said:
On Tue, May 06, 2008 at 09:31:15AM -0800, Beech Rintoul wrote:
Is there a way to configure SSHd, so that the wait time between
login attempts increases after X failed tries?
Not that I know of. You should look into denyhosts (in the ports)
it
David Kelly wrote:
On Tue, May 06, 2008 at 09:31:15AM -0800, Beech Rintoul wrote:
Is there a way to configure SSHd, so that the wait time between
login attempts increases after X failed tries?
Not that I know of. You should look into denyhosts (in the ports) it
works well and even
Beech Rintoul wrote:
On Tuesday 06 May 2008, David Kelly said:
On Tue, May 06, 2008 at 09:31:15AM -0800, Beech Rintoul wrote:
Is there a way to configure SSHd, so that the wait time between
login attempts increases after X failed tries?
Not that I know of. You should look into denyhosts (in
On May 6, 2008, at 10:57, Randy Ramsdell wrote:
David Kelly wrote:
On Tue, May 06, 2008 at 09:31:15AM -0800, Beech Rintoul wrote:
Is there a way to configure SSHd, so that the wait time between
login attempts increases after X failed tries?
Not that I know of. You should look into
Doug Hardie wrote:
On May 6, 2008, at 10:57, Randy Ramsdell wrote:
David Kelly wrote:
On Tue, May 06, 2008 at 09:31:15AM -0800, Beech Rintoul wrote:
Is there a way to configure SSHd, so that the wait time between
login attempts increases after X failed tries?
Not that I know of. You
On Tue, 06 May 2008 19:11:45 +0200
Gilles [EMAIL PROTECTED] wrote:
Is there a way to configure SSHd, so that the wait time between login
attempts increases after X failed tries?
It shouldn't be too hard to patch
/usr/src/crypto/openssh/sshd.c:server_accept_loop()
by adding code for per-IP
On May 6, 2008, at 14:24, Randy Ramsdell wrote:
Doug Hardie wrote:
On May 6, 2008, at 10:57, Randy Ramsdell wrote:
David Kelly wrote:
On Tue, May 06, 2008 at 09:31:15AM -0800, Beech Rintoul wrote:
Is there a way to configure SSHd, so that the wait time between
login attempts increases
On May 6, 2008, Gilles wrote:
Is there a way to configure SSHd, so that the wait time between login
attempts increases after X failed tries?
I run sshd via inetd rather than as a stand-alone daemon. inetd provides
optional rate limiting functionality. For instance. putting
ssh stream
26 matches
Mail list logo
