KEYS (ssh, gpg) appear to ONLY work in desktop site, NOT Mobile or even desktop site loaded on mobile! Workaround
KEYS (ssh, gpg) appear to ONLY work in desktop site, NOT Mobile or even desktop site loaded on mobile! That is, I saw no menu or way to select/enter such information on mobile. Android 9, but I think 12 does not show it either.
Also gitlab demands ed25519 keys (or at least openssh format, who knows?) but abuild only signs with openssl rsa!!! Showstopper. Refactoring abuild to accept ed25519/openssh seems in order.
Workaround: Use ed25519 key for gitlab (push/pull/merge), and openssl/rsa for 'local' builds, for now. Hopefully remedied soon :-)
Activity
Not sure what you are attempting to do.
Adding ssh keys to your gitlab account allows you to push to repositories over ssh. Adding gpg keys to gitlab allows it to verify commits you've signed. This all is about git and not about abuild
Keys used for abuild are for signing packages abuild produces, and those signatures are checked by apk when installing packages. This all is about packages and not git.
There seems to be a few issues here. Are they all related to GitLab?
- If you are having a problem managing your SSH/GPG keys for your GitLab account using Android, you will need to contact GitLab themselves. Note that it works fine for me in "Fennec" (Android Firefox):
-
GitLab supports many types of keys, but yes, they must be OpenSSH keys.
-
Package signing is not meant to use the same key you use for Git. Git keys identify you and authenticate you as a person, while package signing keys identify and authenticate a computer that built the software. You might be able to share RSA key material between SSH and abuild, but it is certainly not recommended and may be a security issue.
Mea culpa. The confusion between SSH and GPG keys and ways to access them through the web interface is on me. Though me being confused, when trying to understand and not very tired, stressed or whatever isn't a good sign, not because of me but potential to confuse others. If explanations similar to the replies above are in the documentation, great, and I wish I'd spotted it. If not, they should be, and I'd be glad to help put it in.
The interface (which I suspect is mostly due to gitlab, and not specifically editable for Adelie, just to be clear who I think deserves any credit/blame!) screams to me "I was designed by someone for whom the 1980's was decades before I was born and I have nothing to learn from that ancient history!" and on whom concepts like Fitts Law and Human Interface Guidelines are "useless anachronisms" to be ignored.
The path from login to SSH keys is so lacking in discoverability, that I can only compare it to the old Zork text adventures! You are in a dark place full of twisty passages. You are likely to be eaten by a grue. I'll have screenshots how undiscoverable it is. It can be used as a textbook titled "How to design a website badly to torture innocent gitlab victims". By gitlab. Violates pretty much 100% of concepts like those above. My only interest is does it work for making Adelie better, not assigning blame, though I do feel gitlab probably deserves the lion's share or even all of it.