Am Sonntag, 22. September 2024, 19:05:35 CEST schrieb Charles Curley: > When you do these things, *exactly* what results do you get? Copy and > paste the entire command line, including the prompt, the results, and > the next command line prompt.
[ … ] On Sun 22 Sep 2024 at 20:01:02 (+0200), Hans wrote: > But I found the reason! > > The eys are set "rw- --- ---", so they could not read. > > This adds another problem: Looks like gpg or sq is setting wrong rights. > > Several minutes ago I discovered another issue: /usr/bin/dpkg was set > to "rwx r-- r--", what is also wrong. As I did not change this, it must have > been changed by some upgrade. Had this issue already in 2014 (with a > mediathekview problem, same reason), > > I suppose, we can safely close this. Thanks for your help, again laerned > something. From the clues left dotted around, my bet is that you've messed up your system with the way you become root, affecting its umask. A couple of months ago (and back in 2020), you were exhorting Debian to set a mask for users of at least 027, and I'm wondering whether, in your case, it might have been changed to 077 since around one of those times. Back in 2014, you had the permissions on dpkg set to -rwxr-x---, which would correspond to a umask of 027, so perhaps you had already tightened your system from the Debian default, 022, to 027 by then. So it now comes down to why system components are getting the user's umask applied to them. For that, I looked back to 2014 when you seemed to be a bit more forthcoming with pasting prompts into your posts. Your first post in the thread¹ starts with: | Ok, so let’s start as root: | | su -p | root@protheus2:~# LANG=C mediathekview Well, three cases of su are: ~$ umask 0027 ← the securer default was set for this user. ~$ su Password: /home/auser# umask 0022 ← correct /home/auser# exit ~$ su - Password: ~# umask 0022 ← correct ~# logout ~$ su -p Password: ~# umask 0027 ← wrong for root ~# exit ~$ So I'm guessing that you've been installing things after having become root with -p. I don't know whether APT and dpkg can themselves modify any excessively restrictive umask, and I'm unwilling to test that here. ¹ https://lists.debian.org/debian-user/2014/07/msg00053.html Cheers, David.
