Opened 6 years ago
#11808 new Bug report
Allow key file reference to not exist
Reported by: | J D | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | FileZilla Client |
Keywords: | keyfile key file storage | Cc: | |
Component version: | 3.38.1 | Operating system type: | OS X |
Operating system version: | 10.14 (18A391) |
Description
Whenever you save a configuration in the site manager, it is possible to select the key file for the logon type.
Unfortunately, the key file always has to exist in order to be able to leave the configuration. I have some key files on external devices and therefore the path is not always available. When I want to connect to another configuration, I can not click on this configuration since the still open configuration gives me an error the key file can not be found.
Steps to reproduce
- Create site A, choose for logon type 'key file'
- Add a key file from an existing location
- Create site B, it does not matter what you configure here
- Connect to site A
- Close filezilla
- The last item you connected to was Site A, so this is still selected in the Site manager. Now delete the key file (or move it) like you are disconnecting the storage volume the key file is stored on.
- Try connecting to site B. This is not possible due to the key file not existing.
Since it does not matter our key file is not available at this moment, since we are trying to connect to Site B (not A), this error should not be in the way of selecting another configuration.