Re:Show HN: Age 1.0 – Simple, modern and secure file encryption
by str4d on Tuesday September 07, 2021 @08:26AM
(#28443833)
> For some reason, I was under the impression age itself had some logic for keys.txt files.
An early version of the draft spec did include a default keys.txt path, and I implemented it in rage. However, during the beta phase discussions we made the decision Filippo described above, and I removed support for a default path in rage 0.5.0.
Re:Show HN: Age 1.0 – Simple, modern and secure file encryption
by ricardobeat on Monday September 06, 2021 @04:53PM
(#28437991)
Where do you store the key that decrypts your key file?
Re:Show HN: Age 1.0 – Simple, modern and secure file encryption
by xoa on Monday September 06, 2021 @07:49PM
(#28439363)
Hardware? I assume if someone was concerned about key access they wouldn't want keys on their filesystem at all but move them into an HSM instead. Since age identities can come from standard input I assume it'd be feasible to put together a workflow there coming from one of the various cli utilities for interacting with keys. There is already a YubiKey specific age plugin [0] getting worked on as well. Currently in beta but looks interesting. Hopefully that will continue to expand to cover other common options. HSM support is pretty important for a modern encryption utility IMO but unfortunately the landscape is pretty all over the place too, so makes sense to just leave it to plugins or as part of a unix flow.
----
Re:Show HN: Age 1.0 – Simple, modern and secure file encryption
by jchw on Monday September 06, 2021 @05:47PM
(#28438477)
You can encrypt with a passphrase.
Re:Show HN: Age 1.0 – Simple, modern and secure file encryption
by ricardobeat on Tuesday September 07, 2021 @09:57AM
(#28444918)
Then why not encrypt the files directly with the passphrase? I think this is where the author mentions “questionable” security improvement from supporting key files.
I understand that it is an ugly and imperfect layer of security to secure keys this way, but I still prefer it over nothing. Maybe applications could try implementing OS-level 'secure' keyring storage; that seems marginally better... No idea, though, I'm no expert on security.
Thanks for age regardless. I'm sure I'll be using it a lot in the future.