Skip to content
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

Decryption does not allow an output directory #8

Open
fieala opened this issue Sep 20, 2016 · 3 comments
Open

Decryption does not allow an output directory #8

fieala opened this issue Sep 20, 2016 · 3 comments

Comments

@fieala
Copy link

fieala commented Sep 20, 2016

Is there a way to specify an output directory instead of a file name when decrypting? I do not know the file names in the encrypted file.

@soukoku
Copy link
Owner

soukoku commented Sep 20, 2016

That doesn't sound like it's going to work. If you don't know the file name then the lib won't know it either. Names are not part of the encrypted data.

@fieala
Copy link
Author

fieala commented Sep 21, 2016

It would be the equivalent of "gpg --decrypt my-file.gpg"
my-file.gpg is the only file specified. The file would be decrypted in the same directory and GPG knows the original file name; the same file name that was supplied with the "gpg --encrypt" command.

@rokx
Copy link

rokx commented Sep 13, 2017

In most cases only gpg extension is the difference in the filename.
Encrypt: test.txt ->test.txt.gpg
Decrypt: test.txt.gpg -> test.txt

Like @soukoku said, there is no filename information in the encrypted data, Just the content is encrypted. You can basically name it to whatever you like.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants