This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
UX: Missing option for noninteractive use of passwords #130
Comments
Can you explain a bit more about how you are trying to use the PW w/ As an aside, I know the dev is working to expose an |
@cyb3rz3us OP is trying to pass passwords as an argument (or having |
Thanks @Fastidious --- I'm aware of what |
@cyb3rz3us that will require a third party tool, like |
"...would use public key to encrypt instead..." --- Indeed. Hence my query... |
The scenario in which I am opting to use age does not allow to store something like keyfiles for each user. Additionally there is one requirement where new users need to get access to previously encrypted files, which is easy when using a shared password. In an additional use case, data is encrypted for long term storage (decades) and one of the requirements that were set for this is symmetric crypto, as it is deemed more reliable in the long run. At the moment the implementation for all of this is planned with a custom encryption file format, but I would like to prefer age if possible to make it easier to access the data in the future and to help age become a standard. Also I do not see much reason to design and implement yet another format if age is already available for this. If #63 provides an API that allows this use case, that is exactly what I am looking for. |
Thanks @x97x53x81 --- So just considering this at a high-level, I can say it is definitely possible to use something simple like a Tcl\Expect script to collect the requisite password information and then pass it to If the API ends up working for you, then of course all the better. But if you need something in the interim, then technically speaking, I don't really see an issue making this work with |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
What were you trying to do
Writing an application that uses age as a backend for encryption using passwords
The application uses passwords for various things and I would like the use age to encrypt data by using the preexisting passwords. Using public keys is not an option in this scenario.
What happened
Age only allows the use of passwords interactively, making it hard to use if (preexisting) passwords need to be used.
For age to become a global standard for encryption, it should consider use cases like this and allow to use of passwords without being used interactively.
The text was updated successfully, but these errors were encountered: