[Cyberduck-trac] [Cyberduck] #11059: My credentials are not being read
Cyberduck
trac at cyberduck.io
Tue May 26 11:51:50 UTC 2020
#11059: My credentials are not being read
------------------------------------+----------------------
Reporter: maeglin | Owner:
Type: defect | Status: new
Priority: normal | Milestone:
Component: s3 | Version: 7.3.1
Severity: normal | Resolution:
Keywords: credentials unreadable | Architecture: Intel
Platform: Linux |
------------------------------------+----------------------
Description changed by maeglin:
Old description:
> I've made a question on AskUbuntu just in case I get a resolution there:
> https://askubuntu.com/questions/1243823/cyberduck-does-not-remember-my-
> credentials
>
> Please see it for details on this issue.
>
> To summarise: I run `duck --list <s3 address here>` and it prompts for
> the key and pass which are supplied, I confirm <y> to save my details and
> those details are stored in ~/.duck/credentials successfully with perms
> 664 with .duck perms 775 both owned by my user and the credentials appear
> to have been written successfully into the credentials file. But when I
> run a similar operation (in this case exactly the same request to list
> the dir), it prompts me again having told me it can't find the
> credentials.
>
> Listing directory path…
> Login s3.amazonaws.com. Login s3.amazonaws.com – S3 with username and
> password. No login credentials could be found in the Keychain.
> Access Key ID:
New description:
I've made a question on AskUbuntu just in case I get a resolution there:
https://askubuntu.com/questions/1243823/cyberduck-does-not-remember-my-
credentials
Please see it for details on this issue.
To summarise: I run `duck --list <s3 address here>` and it prompts for the
key and pass which are supplied, I confirm <y> to save my details and
those details are stored in `~/.duck/credentials` successfully with perms
664 with .duck perms 775 both owned by my user and the credentials appear
to have been written successfully into the credentials file. But when I
run a similar operation (in this case exactly the same request to list the
dir), it prompts me again having told me it can't find the credentials.
{{{#!sh
Listing directory path…
Login s3.amazonaws.com. Login s3.amazonaws.com – S3 with username and
password. No login credentials could be found in the Keychain.
Access Key ID:
}}}
--
--
Ticket URL: <https://trac.cyberduck.io/ticket/11059#comment:6>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows
More information about the Cyberduck-trac
mailing list