← Back to team overview

nssbackup-team team mailing list archive

[Bug 240988] [NEW] sbackup uses old ssh key value

 

Public bug reported:

Binary package hint: sbackup

I'm using Ubuntu 8.04 and version of sbackup is 0.10.4. 
The openssh packge in destination server updated recently which also assigned a new key to the server. I removed the the old key from /etc/known_hosts file (in the machine that is accessing the destination server) so that I can ssh to the destination server. However, SBACKUP is still using the old ssh key value and decides that the destination folder (ssh:/login@servername/home/user/backup) is not writable (I guess due to failed login). I deleted all the values in gnome-keyring as well and it didn't help.
If I try "different_login@different_servername/home/different_user/backup" it works fine. 
Other softwares (such as: gvfs-sftp) have no problem accessing the login@servername (the server with updated ssh key), only sbackup is not able to access to that server.

** Affects: sbackup (Ubuntu)
     Importance: Undecided
         Status: New

-- 
sbackup uses old ssh key value
https://bugs.launchpad.net/bugs/240988
You received this bug notification because you are a member of NSsbackup
team, which is subscribed to sbackup in ubuntu.



Follow ups

References