Bug#863179: apt: GPG errors on update and other operations

> Yeah, sorry, there should be --export. > Great! gpg --no-default-keyring --export --keyring /etc/apt/trusted.gpg > /etc/apt/trusted.gpg.new fixed the problem. I now need to decide whether I should nuke and pave. The only question that remains is: how did this happen? There must be an issue

Bug#863179: apt: GPG errors on update and other operations

On Thu, Jun 01, 2017 at 07:52:04PM +1000, Peter Miller wrote: > > That's your problem. Run > > > > > gpg --no-default-keyring --keyring /etc/apt/trusted.gpg > > > /etc/apt/trusted.gpg.new > > mv /etc/apt/trusted.gpg.new /etc/apt/trusted.gpg > > > > To convert the keybox file back to a key

Bug#863179: apt: GPG errors on update and other operations

> That's your problem. Run > > gpg --no-default-keyring --keyring /etc/apt/trusted.gpg > > /etc/apt/trusted.gpg.new > mv /etc/apt/trusted.gpg.new /etc/apt/trusted.gpg > > To convert the keybox file back to a key ring. > > The gpg command hangs. If I issue it without the pipe I get: gpg: Go

Bug#863179: apt: GPG errors on update and other operations

On Wed, May 31, 2017 at 07:45:51PM +1000, Peter Miller wrote: > > What about /etc/apt/trusted.gpg > > > trusted.gpg: GPG keybox database version 1, created-at Fri Apr 28 07:45:49 > 2017, last-maintained Fri Apr 28 07:45:49 2017 That's your problem. Run gpg --no-default-keyring --keyring

Bug#863179: apt: GPG errors on update and other operations

> ... In the gmail web UI, > you click on the three dots and then move your cursor to the position > where you want to start writing (I actually forgot to add this to the > previous email...). > OK. I'm not a fan of a UI where the same element does very different things. In the past there was a

Bug#863179: apt: GPG errors on update and other operations

On 29 May 2017 at 09:53, Peter Miller wrote: > Hi, > > > If you'd like to show me how I can use the gmail web interface to respond > inline and select what to quote, do go ahead. I really don't like to be > called names, especially when there is no basis for it. Oh, I

Bug#863179: apt: GPG errors on update and other operations

Hi, If you'd like to show me how I can use the gmail web interface to respond inline and select what to quote, do go ahead. I really don't like to be called names, especially when there is no basis for it. Sorry, but I did miss the stuff from David. But, all files in that directory are

Bug#863179: apt: GPG errors on update and other operations

On Fri, May 26, 2017 at 06:21:23PM +1000, Peter Miller wrote: > Julian, > > Sorry, but gmail does not allow me to reply inline, or to select what I > quote. I am using the only option I have. Yeah, right. No. That's a lie. > > I am not and did not ignore Frank's advice, which included a

Bug#863179: apt: GPG errors on update and other operations

Julian, Sorry, but gmail does not allow me to reply inline, or to select what I quote. I am using the only option I have. I am not and did not ignore Frank's advice, which included a *count* of the files in /etc/apt/trusted.gpg.d. That advice was followed and was a dead end. Frank's advice was

Bug#863179: apt: GPG errors on update and other operations

On Thu, May 25, 2017 at 08:23:34PM +1000, Peter Miller wrote: > Julian, > > There is no such thing as perfect security. I was and am using a trusted > mirror, so I'm much more worried about the Windows machines I have to use > at work, and are necessarily linked to my linux boxes. So, please, >

Bug#863179: apt: GPG errors on update and other operations

Julian, There is no such thing as perfect security. I was and am using a trusted mirror, so I'm much more worried about the Windows machines I have to use at work, and are necessarily linked to my linux boxes. So, please, understand that I understand the (small) risk I have taken. I wouldn't even

Bug#863179: apt: GPG errors on update and other operations

On Thu, May 25, 2017 at 06:49:31PM +1000, Peter Miller wrote: > David, > > Thanks for your time on this. I am surprised that the answer to this issue > is a re-install: it's only the keys that are corrupt somehow, and I am > surprised there is not a simple way to fix this. I have an unusual setup

Bug#863179: apt: GPG errors on update and other operations

David, Thanks for your time on this. I am surprised that the answer to this issue is a re-install: it's only the keys that are corrupt somehow, and I am surprised there is not a simple way to fix this. I have an unusual setup with a mirrored ZFS pool as my home directory, so I'm a little

Bug#863179: apt: GPG errors on update and other operations

On Tue, May 23, 2017 at 10:59:32AM +1000, Pete Miller wrote: > Subsequently, I have run "apt update --allow-insecure-repositories", which > worked, but a subsequent "apt-get update --allow-unauthenticated" and similar > failed to update any packages due to key errors as detailed in the thread.

Bug#863179: apt: GPG errors on update and other operations

Julian, I thought doing one update might fix the issue, since nothing else was working, hence --allow-unauthenticated. I did not install or update anything in /etc/apt/trusted.gpg.d, or anywhere else similar, so how did it get corrupted? Is there a source issue? Are there automated checks after

Bug#863179: apt: GPG errors on update and other operations

On Tue, May 23, 2017 at 10:59:32AM +1000, Pete Miller wrote: > Package: apt > Version: 1.4.1 > Severity: important > Tags: d-i > > Dear Maintainer, > > I installed Stretch from the CD image to new physical hardware, and then > updated the system. I can't remember if errors started straight away,

Bug#863179: apt: GPG errors on update and other operations

Package: apt Version: 1.4.1 Severity: important Tags: d-i Dear Maintainer, I installed Stretch from the CD image to new physical hardware, and then updated the system. I can't remember if errors started straight away, or took a while to manifest. See this thread for some background: