Opened 15 months ago

#12833 new Bug report

Filezilla uses old key for SFTP after a key is changed

Reported by: Matt Owned by:
Priority: normal Component: FileZilla Client
Keywords: sftp Cc:
Component version: 3.62.2 Operating system type:
Operating system version: mac and windows

Description

Filezilla client latest (3.62.2)

Both mac and windows, so probably not an OS-related issue.

Repro...

Have an SFTP connection using pubkey auth.

Change the public key on the server (authorized_keys) and change the key file on the filezilla client for the connection to use the new private key.

Connecting and browsing with the new key works fine but when you go to upload files, you get a key error as filezilla starts using the old key if it still exists (resulting in "Server refused our key" error) or if the old key no longer exists on disk: "Skipping non-existing key file" as filezilla attempts to use the old key.

A possibly related issue (seen by 2 users on Windows10Pro, Filezilla 3.62.2) is that after deleting the connection from Filezilla's connection manager and restarting Filezilla, the deleted connection reappears in connection manager and has to be re-deleted.

Work around

To work around this you need to delete the connection in the connection manager and re-create from scratch using the new key. If the connection keeps re-appearing you may have to try multiple times (some users reported to me it took 3 tries to get the old connection to delete and the new one to work restarting filezilla between each).

Change History (0)

Note: See TracTickets for help on using tickets.