4 ms·

I absolutely love the idea of simple and beautiful. OpenSSL/GPG are overwhelming in the knobs/dials. Couple thoughts that I'll never remember after my 5 minut

I absolutely love the idea of simple and beautiful. OpenSSL/GPG are overwhelming in the knobs/dials. Couple thoughts that I'll never remember after my 5 minutes of using it but will likely be experienced by a lot of people in their first 5 minutes. o It's odd that -e (encrypt) can recognize an age-keygen file, but -d (decrypt) errors out with: age: error: failed to parse recipient file "person.pub": "person.pub": malformed recipient at line 1 I mean, I get it - the recipient should be the key, but you would think that age would be able to recognize its own "# public key: " string and parse it? (Like I said - noticed only in the first 5 minutes of use) o In the vein of user friendliness/simplicity - why not just default to armored? It doesn't hurt anything to be armored, and if someone really wants a binary output, they could specify it specifically. Given they are both (mostly) equivalent, could as well default to the user friendly version. I get that it's too late to make the change now. o Not available as a brew install, so I had to armwrestle with MacOS to let me even run it (Security was clever enough to recognize when I was copying something downloaded, had to defeat it with `dd if=age of=age2`) o I do love `age -e -o out.enc -p somefile.txt`

rdpintqogeogsaa 5y ago
> why not just default to armored? I assume this is because the author really does not want people to use age to encrypt e-mail because e-mail encryption is hopelessly and unfixably broken. By making armored not be the default, it's an extra little thorn in the side.
str4d 5y ago
> o It's odd that -e (encrypt) can recognize an age-keygen file, but -d (decrypt) errors out with: > > age: error: failed to parse recipient file "person.pub": "person.pub": malformed recipient at line 1 I'm confused as to how you reached this error message; "age -d" doesn't support recipient files / -R, only identity files (which is what age-keygen produces). It would be helptul to open an issue showing how to reproduce; either there's a bug, or documentation could be improved. > o Not available as a brew install While age was in beta, it provided a brew tap. But now that 1.0.0 has been released, it has just (3 hours ago!) been added to homebrew-core: https://github.com/Homebrew/homebrew-core/pull/84805 https://github.com/Homebrew/homebrew-core/pull/84805
FiloSottile 5y ago
Thank you for the friction log! This kind of feedback is extremely valuable! 1. It sounds like you were passing an identity file to --recipients-file. We do support using identity files with --encrypt, but you need to pass it to --identity. We can make the error message more helpful when we notice this is happening. 2. Armoring has a lot of space overhead, and most applications don't need it. (age is not for encrypting messages and emails!) 3. It's now in Homebrew Core :) 4. :D

rdpintqogeogsaa 5y ago

> why not just default to armored? I assume this is because the author really does not want people to use age to encrypt e-mail because e-mail encryption is hopelessly and unfixably broken. By making armored not be the default, it's an extra little thorn in the side.

str4d 5y ago

> o It's odd that -e (encrypt) can recognize an age-keygen file, but -d (decrypt) errors out with: > > age: error: failed to parse recipient file "person.pub": "person.pub": malformed recipient at line 1 I'm confused as to how you reached this error message; "age -d" doesn't support recipient files / -R, only identity files (which is what age-keygen produces). It would be helptul to open an issue showing how to reproduce; either there's a bug, or documentation could be improved. > o Not available as a brew install While age was in beta, it provided a brew tap. But now that 1.0.0 has been released, it has just (3 hours ago!) been added to homebrew-core: https://github.com/Homebrew/homebrew-core/pull/84805 https://github.com/Homebrew/homebrew-core/pull/84805

FiloSottile 5y ago

Thank you for the friction log! This kind of feedback is extremely valuable! 1. It sounds like you were passing an identity file to --recipients-file. We do support using identity files with --encrypt, but you need to pass it to --identity. We can make the error message more helpful when we notice this is happening. 2. Armoring has a lot of space overhead, and most applications don't need it. (age is not for encrypting messages and emails!) 3. It's now in Homebrew Core :) 4. :D