5 ms·
Ideally you'd be able to add the alternative store's public key to the existing snap client. Like you can do with existing package managers to include alternati
by __s 6y ago
Ideally you'd be able to add the alternative store's public key to the existing snap client. Like you can do with existing package managers to include alternative repos
- gjsman-1000 6y agoThey deliberately designed the software to not allow that without you forking. I mean, it is trivially easy for Canonical to just put the public key in a file and have Snap read from that key. Instead, they've hard-compiled it in. Three years ago, I actually had a discussion with them about External Repositories. It's called "External Repositories?" on the forum and has, like, over 200 messages on it. They didn't budge one bit despite our arguments on why this was a very bad idea on their part.
- simion314 6y agoWas there a competent patch submitted about keys and was this discussed in public? I imagine you can't just drop the keys in a random text file, it must be protected like the passwords file.
- renewiltord 6y agoThey're public keys so they can be in plaintext and protected by 0644. They don't really have to be different from apt keys.
- simion314 6y agoYou still need to protect from getting updated by errors or malicious code. For apt you have utilities to edit the keys you don't edit a test file by hand.
- renewiltord 6y agoSure. I only hope to answer "like the passwords file".
- ifmpx 6y agoWould canonical be interested in accepting such a patch?
- simion314 6y agoNo idea, but honestly I would not spend my time on writing such a patch yet , only if I intend to create a great snap store to rival Canonical , otherwise we have enough working alternatives for all use cases that are not about third party binaries that are reviewed by Canonical.