[Cyberduck-trac] [Cyberduck] #11059: My credentials are not being read
Cyberduck
trac at cyberduck.io
Mon Jun 1 08:35:25 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 |
------------------------------------+----------------------
Comment (by maeglin):
Replying to [comment:8 TobyEggitt]:
> However, I am able to specify credentials on the command line using the
-u and -p options.
>
> (side note, I tried using -i <my access key> and also using -i <path to
file containing my key> and both forms result in: "Login s3.amazonaws.com.
Login failed. The AWS Access Key Id you provided does not exist in our
records." I presume I misunderstand what -i is intended for?)
>
The -i flag is intended for an SSH key, the kind you generate with the
command `ssh-keygen` that gets saved to `~/.ssh/`. We could probably solve
our issue temporarily by using the -u username/access key flag and -p
password. But it is not a fix.
--
Ticket URL: <https://trac.cyberduck.io/ticket/11059#comment:11>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows
More information about the Cyberduck-trac
mailing list