[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#619558: marked as done (Does not need a GPG trustdb (/etc/apt/trustdb.gpg), just the trusted keyring)

Your message dated Tue, 11 Aug 2015 14:12:02 +0200
with message-id <20150811121202.GB6091@crossbow>
and subject line Re: Bug#619558: Does not need a GPG trustdb (/etc/apt/trustdb.gpg), just the trusted keyring
has caused the Debian Bug report #619558,
regarding Does not need a GPG trustdb (/etc/apt/trustdb.gpg), just the trusted keyring
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
619558: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619558
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apt
Version: 0.8.13
Severity: wishlist

apt doesn't need to maintain the GPG trustdb in /etc/apt/trustdb.gpg;
apt trusts all keys in /etc/apt/trusted.gpg and /etc/apt/trusted.gpg.d/*
..  Please consider getting rid of the trustdb, and if necessary just
telling GPG to trust all keys in the trusted keyring.

- Josh Triplett

--- End Message ---
--- Begin Message --- 
Version: 0.9.10

On Tue, Aug 11, 2015 at 02:10:33PM +0200, David Kalnischkies wrote:
> On Wed, Mar 30, 2011 at 10:27:57PM +0200, David Kalnischkies wrote:
> > On Sun, Mar 27, 2011 at 03:13, Josh Triplett <josh@joshtriplett.org> wrote:
> > > On Sat, Mar 26, 2011 at 10:33:17AM +0100, David Kalnischkies wrote:
> > >> I think this is very similar to --secrect-keyring which isn't really needed,
> > >> but gpg seems to insist on having it around…
> > >
> > > --trustdb-name /dev/null seems to work just fine, as does
> > > --secret-keyring /dev/null.
> > 
> > It works as long as the keyring isn't changed, but if a key is added or
> > remove you will get the lovely message:
> > 
> > gpg: fatal: /dev/null: invalid trustdb
> > secmem usage: 1408/1408 bytes in 2/2 blocks of pool 1408/32768
> > 
> > The action is executed non the less, but gpg exits with non-zero status
> > and i don't think ignoring gpg failures is a good idea…
> 
> In the meantime we figured something out in apt 0.9.10 by enlarging and
> rewriting the wrapping in apt-key and so the /etc/apt/trustdb.gpg is
> positively gone since DebConf13, but the bug was never closed, so I am
> doing it now.

This time sending it to the right address even…

Best regards

David Kalnischkies

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: