look at fail2ban for the ssh probes... there are similar packages for
non-linux as well. (although it shouldn't be too hard to port.)
someone pointed out --remote-schema already... what i tend to prefer for
ssh is to make up fake hostnames in .ssh/config. (see
hi,
what parameters should i add when doing rdiff-backup to a remote host
with its ssh port not using default port 22. i dont want to put back the
remote host on port 22 as part on the security on SSH. any ideas guys?
thanks.
rudy
___
You can supply parameters to the --remote-schema switch:
--remote-schema 'ssh -p port -l login %s rdiff-backup --server'
Hope this helps,
- michael
Am Donnerstag, 31. Mai 2007 10:06 schrieb RudySC:
hi,
what parameters should i add when doing rdiff-backup to a remote host
with its ssh port
Hi Chris,
Yeah thats what i did initially, but there are lots of scanning on port
22 the reason why i changed default port. I was thinking of editing the
source, but dont know what file the ssh -C $IP_ADDRESS is associated.
-Rudy
On Thu, 2007-05-31 at 09:14 +0100, Chris Wilson wrote:
Hi Rudy,
Hi Rudy
On Thu, 31 May 2007, RudySC wrote:
Yeah thats what i did initially, but there are lots of scanning on port
22 the reason why i changed default port. I was thinking of editing the
source, but dont know what file the ssh -C $IP_ADDRESS is associated.
Please re-read my answer. This is
