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,
> understand that I understand the (small) risk I have taken. I wouldn't even
> take the time to verify my packages later, as it's not worth the
> investment. I have good backups of all my important stuff, and I would
> notice a bot eventually. So, could we please get back to my question?
>
> Is there any way to fix my keys?
This is getting ridiculous. David told you precisely what to do and I
quoted it for you in the previous email again, if you keep ignoring that,
that's your problem. This is likely the last time I'll quote that for you:
> On 25 May 2017 at 19:00, Julian Andres Klode <j...@debian.org> wrote:
> > You know, that bit:
> >
> > > On 23 May 2017 at 21:35, David Kalnischkies <da...@kalnischkies.de>
> > wrote:
> > > > Julian was asking basically for running both:
> > > > ls -l /etc/apt/trusted.gpg{,.d}
> > > > file /etc/apt/trusted.gpg{,.d/*}
> > > >
> > > > As he thinks it might be a permission/wrong-file-in-there problem,
> > which
> > > > is the most likely cause… I would add a "stat /tmp" as I have seen it
> > > > a few times by now that people had very strange permissions on /tmp
> > > > – all of which usually caused by "fixing" some problem earlier…
Also please reply properly, as explained below.
--
Debian Developer - deb.li/jak | jak-linux.org - free software dev
| Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline'). Thank you.
