Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#10949 closed Bug report (wontfix)

Missing Private Key Locks Site Manager

Reported by: Ben Yanke Owned by:
Priority: low Component: FileZilla Client
Keywords: Cc:
Component version: 3.20.1 Operating system type: Windows
Operating system version: Windows 10 (build 10586.545)

Description

When scrolling through sites on the site manager, if you select a site that uses keys to authenticate, and those key files are missing, a pop up appears saying:

title: "Could not load key file"
body: "The file '[path to key]' could not be loaded or does not contain a private key.

However, when you attempt to select another site from the list, the pop up still appears, and does not allow you to use the site manager without closing and reopening the window.

While the bug could be fixed by simply stopping the pop-up from appearing again after you select another site, I would like to propose that the key not found be moved into the site manager itself, instead of a popup, perhaps as a colored warning below the key file selector. This would have the benefit of not stopping a user from scrolling down through the list and getting pop-ups for sites he is not interested in, only getting the alert within the window when he stops on a site.

note: this also happens on the linux versions of filezilla.

Change History (2)

comment:1 Changed 3 years ago by Tim Kosse

Resolution: wontfix
Status: newclosed

This is intentional so that incomplete or invalid Site Manager entries cannot be created.

Please correct the invalid Site Manager entry to proceed.

comment:2 Changed 3 years ago by Ben Yanke

Frankly, that's rather silly. I have about 200 entries in my site manager, and 3 have public keys. I sync the site manager file between multiple systems, and only use the key auth clients a few times a year, so I don't worry about syncing the keys (I can just VPN and RDP home if I need to access one of those clients). I know that I have keys missing, and I am fine with that. That doesn't mean I should have the site manager crippled.

This feels like a microsoft decision: "this is how we say you can use our software and you're going to like it." Even if it takes digging down deep into settings to fix it, this is something that should be able to be overridden.

Last edited 3 years ago by Ben Yanke (previous) (diff)
Note: See TracTickets for help on using tickets.