-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
Passcode option (command-line) #10
Comments
To solve the visibility on the command line, I regularly use for gpg |
Christoph submitted a PR addressing this issue. we are planning to pipe the passphrase through stdin using |
Writing an actual file to disk with the plaintext pswd inside is probably more useful for long keys (such as your private ssh key). When it comes to crypto, maybe we should also have a --passphrase-fd option (since I only implemented the fix for gpg)? |
think that this is widely used? |
Not really :) I was thinking the whole |
Definitely agree about the passphrase option given this issue. I like the authentication on the encryption end, agree that it is unnecessary on the decryption side. Will create a new issue and remove it. — On Thu, May 28, 2015 at 7:41 AM, chrisidefix notifications@github.com
|
It could be useful at times to allow the user to provide the passcode at the time of calling crypto. It is partially related to issue #8, but not really a solution to it. Right now I basically am imagining the same option that
gpg
provides on the command-line with--passphrase
.Of course the passphrase will be visible on the commandline (and in the commandline history), if you are using this option, but the same is true if you use it with
gpg
directly. There are many scenarios though, where I would like to be able to call crypto, but not have to wait for it to ask for a passphrase or I might want to call it multiple times from another script and not have to manually type in the passphrase.I already have a rough implementation for this, if you like to have a look.
The text was updated successfully, but these errors were encountered: