UX: Better recipient support to match reference implementation

[uhthomas]

What were you trying to do

Encrypt for recipients listed via GitHub or HTTP(S) resources. The spec, age v1, has many examples of using recipients like github:<username> or providing a HTTP URL. This doesn't work with rage 0.6.0.

What happened

❯ rage -r github:uhthomas test.txt
Error: Invalid recipient 'github:uhthomas'

[ Did rage not do what you expected? Could an error be more useful? ]
[ Tell us: https://str4d.xyz/rage/report                            ]
❯ rage -r https://github.com/uhthomas.keys test.txt
Error: Invalid recipient 'https://github.com/uhthomas.keys'

[ Did rage not do what you expected? Could an error be more useful? ]
[ Tell us: https://str4d.xyz/rage/report                            ]

[str4d]

Hmm, those were supposed to be removed from the spec. cc @FiloSottile

They were part of the early draft spec, and in fact rage did implement support for them! But during the beta development phase, we decided that they weren't appropriate for the age tool, and could easily be handled by composing age with tools like curl. So I removed support for them.

[mihaigalos]

Not sure if this is a separate issue or you want to consolidate it as part of this one:

Any plans to enable recipient removal from already encrypted files? Specifically, when used with a YubiKey-hosted identity and that YubiKey gets lost/stolen?

[AlexCzar]

This issue should probably be closed, as age removed the functionality as well.