Jeremy C. Reed
unread,Aug 25, 2017, 2:13:09 PM8/25/17Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to aptly-...@googlegroups.com
Any way to gpg dual-sign the Release file with aptly? I don't see as an
option. (I am researching to replace reprepro with aptly.)
I don't see a way to pass two different passphrases also.
I am using a key rollover scenario. One key is old (and not supported
for some Debian systems) and will be deprecated and removed.
Currently I am using reprepro and two keys are used to sign the package
metadata (using multiple keys set with reprepro "SignWith"). (And
gpg-agent to sign both in my automated continuous integration. Or for
manual builds I enter the two phrases when reprepro prompts twice.)
The apt-get update works if it can verify using one of the keys.
(On a related note, I see aptly prompts for phrase twice for same key
for sign and clearsign.)
If aptly doesn't support signing multiple times, I can work around that.
(One idea is to -skip-signing and then post process the Release file
with gpg without aptly.)
If you have any experiences with key replacement using aptly, please
share.
Thanks,
Jeremy C. Reed
echo 'EhZ[h ^jjf0%%h[[Zc[Z_W$d[j%Xeeai%ZW[ced#]dk#f[d]k_d%' | \
tr '#-~' '\-.-{'