Get recipient keys from https:// and file:// URLs

[paulc]

This patch includes support for https:// and file:// URLs as recipient arguments. The URL is fetched and each line is added as a recipient.

e.g.

-r https://github.com/<user>.keys       (Use GitHub keys)
-r file:///home/<user>/.ssh/<key>.pub   (Use local SSH key)

This is mostly useful to allow recipient keys to be specified directly from a GitHub URL (or other service which provides an equivalent)

[mohammed90]

Awesome! Should resolve #34 😃

[geek-at]

Any ETA on a merge?

[Fastidious]

I think this is a very useful PR. Any reasons why it should not be merged, @FiloSottile?

[geek-at]

seems like the project is dead. Development wise

[cyb3rz3us]

Not dead...just not a lot to really do. People are always free to pull and develop as they wish...

[Fastidious]

@cyb3rz3us something like this is mentioned on age's design document. From it:

$ echo "_o/" | age -o hello.age -r https://github.com/FiloSottile.keys
$ echo "_o/" | age -r https://filippo.io/.well-known/age.keys

[cyb3rz3us]

I wasn't arguing for or against the feature (but I do agree it is a good thing) but rather that the project is dead...it's not dead...just not on fire. And if folks want to see stuff happen quicker, then pull and fork...

[Fastidious]

@cyb3rz3us I disregarded the "project is dead" comment altogether. I was just pointing out this PR is something that is/was wanted originally.

[cyb3rz3us]

Agreed...

[FiloSottile]

Hi! Thank you for contributing! I took a different path in #173, but it was useful to look at open PRs for the users' expectations. Let me know if that implementation works for you!

I wrote up an explanation of why I ended up implementing recipient files and not HTTPS sources on the mailing list, and I appreciate feedback! https://groups.google.com/g/age-dev/c/StmWsOyb-H8/m/a44rSBIWCAAJ