You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upload a file to a saved FTP server through the context menu in Finder
Quit OneWay
Upload another file to the same saved FTP server through the context menu in Finder
Quit OneWay
Upload another file to the same saved FTP server through the context menu in Finder
OneWay will read the saved keychain password with an extra character appended. It will then try to authenticate with the FTP server with this extra character appended to the password. This will cause an authentication failure and prompt the user to re-enter the password. Authentication with the FTP server will continue failing for the same reason until the user deletes the last character from the saved password text field on the login retry action sheet and pushes the "OK" button. Deleting the last character of the password from the Editing Bookmark action sheet and hitting OK does not solve this issue, even if OneWay is reloaded after the bookmark action sheet is dismissed.
Note: The correct password is always stored within the keychain file. Through the Keychain Access program I confirmed the saved password was being stored correctly, even when OneWay was failing upon reading the password from the keychain. I suspect this may be an issue with the UTF8 conversion and possibly a null character being appended, but I have no evidence to support this so take it with a grain of salt.
The text was updated successfully, but these errors were encountered:
Thanks for tracking this down, I noticed there was an issue with keychain passwords too but had no idea what was happening.. I'll look into this extra character thing and hopefully get a fix out soon.
Note: The correct password is always stored within the keychain file. Through the Keychain Access program I confirmed the saved password was being stored correctly, even when OneWay was failing upon reading the password from the keychain. I suspect this may be an issue with the UTF8 conversion and possibly a null character being appended, but I have no evidence to support this so take it with a grain of salt.
The text was updated successfully, but these errors were encountered: