In my FAS account I can only use RSA keys. I moved away from RSA since my new YubiKey has support for the better ed25519 ECC keys. Would it be possible to enable support for these keys? For both GPG and SSH? When I try to save these keys into FAS I get the error that the key is not recognized.
Furthermore, does the GPG key lookup use the new and more secure hkps://keys.openpgp.org to lookup keys? More info: https://keys.openpgp.org/about
This is an old RFE for FAS: https://github.com/fedora-infra/fas/issues/210
However, we are currently in the process of moving away from FAS to a replacement which is IPA-based (you can learn more about it in the recording from nest this summer: https://www.youtube.com/watch?v=x1SevUmkE60 ).
We have just received confirmation that IPA supports ssh-rsa, ssh-dss, ecdsa-sha2-* and ssh-ed25519. So this issue should no longer be one in the coming months once we've made the switch.
In the mean time you will have to create a RSA key just for FAS if you need to use ssh. You may also use the procedure at: https://docs.fedoraproject.org/en-US/ci/pull-requests/#_you_are_not_a_packager which allows to push over http to dist-git. It will not solve the issue of accessing fedorapeople though.
Another precision that was made to me and that I'm including here for the record:
OpenSSH has two different key format for ED25519: ed25519 and ed25519-sk (this one being for FIDO devices). IPA may not support ed25519-sk.
Metadata Update from @smooge: - Issue close_status updated to: Will Not/Can Not fix - Issue status updated to: Closed (was: Open)
I closed this as won't fix in FAS as we are moving to a new system which will fix it. It would be better closed as UPSTREAM
Metadata Update from @smooge: - Issue status updated to: Open (was: Closed)
Metadata Update from @smooge: - Issue close_status updated to: Upstream - Issue status updated to: Closed (was: Open)