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 http://arctic.org/~dean/rdiff-backup/unattended.html for examples.) -dean On Thu, 31 May 2007, RudySC wrote: > 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, > > > > On Thu, 31 May 2007, RudySC wrote: > > > > > 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. > > > > I'm not sure it's possible by giving rdiff-backup command-line parameters. > > What I normally do is edit /etc/ssh/ssh_config to set the default port for > > the specified remote host: > > > > Host xxx.yyy.com > > Port 2222 > > > > Cheers, Chris. > > > > _______________________________________________ > rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org > http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users > Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki > _______________________________________________ rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
