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

Re: Apt trusted.gpg file problems



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, Mar 26, 2017 at 09:03:31AM +0000, Miltiades Vasiliades wrote:
> I tried switching the mirrors through synaptic then synaptic as usual asked to refresh however the refresh ended with the following errors
> 
> W: http://repo.steampowered.com/steam/dists/precise/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
> W: http://security.debian.org/…/dists/stretch/updates/InRelease<http://security.debian.org/debian-security/dists/stretch/updates/InRelease>: The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
> W: http://ftp.de.debian.org/debian/dists/stretch/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
> 
> 
> Any ideas how to resolve that issue?

Hm. Some newfangled sandboxing stuff, it seems. On my system (no synaptic,
no desktop environment), the trusted keys are just readable by root:

  tomas@rasputin:~$ ls -l /etc/apt/trusted.gpg
  -rw------- 1 root root 0 Aug  7  2012 /etc/apt/trusted.gpg

I *gues* this _apt thing is to allow running synaptic as non-root (which
in itself is a Good Thing, one might guess).

Can you do the following, on a console:

  grep "_apt" /etc/passwd

(this is to see whether, and how an user named _apt is known to your
system) and

  ls -l /etc/apt/trusted.gpg

(this is to see the file's permissions, etc.), and then perhaps

  getfacl /etc/apt/trusted.gpg

(more info about the access controls to that file) and post your
results here?

Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAljXjtYACgkQBcgs9XrR2kbKowCfXaHGW1yy4nJgc5v84893a6yg
lv8Anj2/q5fq5pm5S9GIVUhuvc7+87VL
=uVEh
-----END PGP SIGNATURE-----


Reply to: