Open mika opened 3 months ago
For clarification where it would be beneficial
/etc/apt/sources.list.d/grml.sources
Types: deb deb-src
URIs: http://deb.grml.org
Suites: grml-stable grml-testing
Components: main
Enabled: yes
Signed-By: /etc/apt/keyrings/deb.grml.org.gpg
Here you could replace the Signed-By: filepath
with the output of the following commannd (which is currenly a bit of a mess).
wget -qO- https://deb.grml.org/repo-key.asc | gpg --armor --export | sed 's/^$/./;s/^/ /g;1 i Signed-By:' |tee -a /etc/apt/sources.list.d/grml.sources
That way you don't even have to put a file in e.g. /etc/apt/keyrings/
.
Do we expect people to have the archive keyring package installed? If not, how will people get the new key?
There needs to be an grml-common
which all other packages depend on and so it will be pulled it automatically and then you could add a script like myon's script in postgresql-common. But that needs to be on the debian side.. enough time for trixie? :P
/me duckt sich schonmal
As noted by cb on IRC (thx!):
Our key is very long as plain text, something newer might be shorter. Also would be nice to use our repository signing key as-is in
/etc/apt/keyrings/
viagrml.sources
.Last but not least, our latest signing key change dates back to 2015, and we might consider creating a more modern/fresh one also for security reasons.
FTR:
I'd be more than happy for any suggestions regarding best practices in terms of GPG implementation usage, key generation settings and command line options. @anarcat maybe might have valuable input for us here? :)