New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CLI --upload / --list Vault does nothing #12812
Comments
Also, a little update: the vault passphrase shows up in plain text, not in asterisks (I've no idea if this is by design or maybe related to the vault "kicking" me out without saying a word).
I entered the right passphrase and it kicks me out anyway... |
Did another test with another newly created vault: same thing. The passphrase prompt shows up, but for some reason, even after the right credentials have been entered, the login never happens. I'm not sure if this has something to do with the vault being located on an amazon server. |
Confirmed, Vault listing doesn't work.
Edit: |
Glad to know it wasn't just me. Maybe this has to do with Cryptomator and not with Cyberduck? |
We have our own interoperable handling of the Cryptomator vault format independent from the implementation in the Cryptomator project. |
Question: how can I know when the version with the fixed bug gets published? (and how can I update the CLI?) |
You get a notification when this issue is closed, then you should expect it being fixed in the following release (if you opted for GitHub-notification emails). Depending on how you installed duck you can update automatically through |
I cannot seem to reproduce the problem
Note the |
Regression from 20d1a7f with upgrade of |
AliveDevil was able to. I just gave it a try myself and I still can't get in, even with the --vault parameter added. If you let the prompt walk you through, at the end, it will just close the connection. |
We have been able to reproduce the problem (Windows only) and a fix is in review. |
Workaround .NET assembly loading IKVM ServiceLoader interoperability screw-up
Always print failure message on exception.
I'm attempting to upload a simple pdf file to a test vault on my s3 bucket, but it ain't working.
This is what I do:
$ duck --upload s3://s3.amazonaws.com/s3folder/ "~/file.pdf"
Duck asks me for my Access Key and Secret Access Key, so good so far.
I can
--list
and--upload
to other directories, as long as they are not vaults.So at this point it says:
file.pdf?file.pdf
Is getting ready to upload, but then it realizes it is a locked vault.
It asks me for my phrase.
I enter my phrase and hit enter.
It asks me to save the password.
Then it just disconnects and goes back to cmd, without telling me anything or giving me a reason.
I'm on a Windows 10 using CMD.
I have successfully uploaded to my S3 bucket as long as they are not vaults. When they are vaults, this happens. I can upload to my vault from the cyberduck app, but I cannot upload from the CLI. I cannot also
--list
anything.The text was updated successfully, but these errors were encountered: