[Popcon-developers] Encrypted popcon submissions
- Subject: [Popcon-developers] Encrypted popcon submissions
- From: Bill.Allombert@math.u-bordeaux1.fr (Bill Allombert)
- Date: Fri, 12 Jul 2013 14:05:26 +0200
- Message-id: <[🔎] 20130712120526.GB8175@yellowpig>
- In-reply-to: <1373555758.6487.6.camel@haktar.debian.wgdd.de>
- References: <20130621150808.GJ12511@yellowpig> <20130702212712.GA5230@yellowpig> <20130710141402.GA18996@yellowpig> <1373492162.7721.3.camel@haktar.debian.wgdd.de> <20130711133321.GC21383@yellowpig> <1373555758.6487.6.camel@haktar.debian.wgdd.de>
On Thu, Jul 11, 2013 at 05:15:58PM +0200, Daniel Leidert wrote:
> Am Donnerstag, den 11.07.2013, 15:33 +0200 schrieb Bill Allombert:
>
> [use gpg but don't write to root/.gnupg]
> > Below is the code in /etc/cron.daily/popularity-contest
> >
> > GPG=/usr/bin/gpg
> > if [ "$ENCRYPT" = "yes" ] && [ -x "$GPG" ]; then
> > POPCONGPG="$POPCON.gpg"
> > rm -f "$POPCONGPG"
> > $GPG --no-default-keyring --keyring "$KEYRING" --trust-model=always \
> > --armor -o "$POPCONGPG" -r "$POPCONKEY" --encrypt "$POPCON"
> > POPCON="$POPCONGPG"
> > fi
>
> I suggest you add trustdb.gpg and secring.gpg
> to /usr/share/popularity-contest/ or (maybe even
> better) /etc/popularity-contest/. apt(-secure) does similar in /etc/apt.
> JFTR: The file secring.gpg can be avoided using
> --secret-keyring=/dev/null but I don't know how to suppress the creation
> of trustdb.gpg.
Well yes, but creating empty, dummy trustdb.gpg and secring.gpg is precisely
what I tried to avoid. Does --homedir=/dev/null would work ?
Cheers,
Bill.
Reply to: