Weird problem with makepkg

mvtab · 2024-11-02 20:35:41

Hi,

whenever I compile something with 'makepkg -sirc' I am prompted 3 times for a sudo password: when installing deps, when removing them, and when installing the package.

here's an asciinema: https://asciinema.org/a/wF8YwpkaZRVNSEm4GAI3R5ott

anybody got any idea how can I fix this? (as in, get it respect the system sudo timestamp)

seth · 2024-11-02 21:20:13

This is strictly makepkg related?

sudo pacman -S cmatrix
cmatrix -abs # wait 30s, press the any key
sudo pacman -R cmatrix
sudo pacman -S cmatrix # because of course you want to have it back :P

does not cause this?

WorMzy · 2024-11-02 21:56:31

sudo -l

May be helpful to see.

Lone_Wolf · 2024-11-02 22:56:08

I'm almost certain this is intentional.

from pacman NEWS file

- Drop sudo permissions after use

See https://gitlab.archlinux.org/pacman/pac … quests/180 .

In theory this could lead to 4 times sudo requires a password entry with -sirc :
installing buildtime deps
installing runtime deps
removing all installed deps
installing the build packages.

Allan · 2024-11-02 23:05:54

You can set "PACMAN_AUTH='sudo' in makepkg.conf to stop that behaviour. But it does allow a rogue PKGBUILD to do what it wants...

mvtab · 2024-11-03 09:32:07

seth wrote:

This is strictly makepkg related?

Yup, I only noticed it here at least. Every other sudo action works as expected.

Lone_Wolf wrote:

I'm almost certain this is intentional.

The timeline does fit with when I started noticing it.

Allan wrote:

You can set "PACMAN_AUTH='sudo' in makepkg.conf to stop that behaviour. But it does allow a rogue PKGBUILD to do what it wants...

It's not disturbing me very much, I just couldn't figure it out and it was bugging me.

Thanks for the explanations guys, makes sense. At least now I know a little more what's up, I'll see how to handle it.
The problem might be in conjunction with makepkg starting to use isolation internally, I also saw a post about relevant recent makepkg updates but can't find it anymore.

Update:
Setting "PACMAN_AUTH=('sudo')" does fix the problem. What exactly are the implications of this? Doesn't makepkg try 'sudo' and 'su' anyway? And isn't 'sudo' basically safer than 'su'?

Last edited by mvtab (2024-11-03 09:53:50)

Allan · 2024-11-03 12:56:13

mvtab wrote:

Setting "PACMAN_AUTH=('sudo')" does fix the problem. What exactly are the implications of this? Doesn't makepkg try 'sudo' and 'su' anyway? And isn't 'sudo' basically safer than 'su'?

If a PKGBUILD has a sudo call inside it (or calls a script with a sudo call inside it), you will not be prompted for a password and thus may not notice what it is doing.

mvtab · 2024-11-03 18:01:11

Allan wrote:

If a PKGBUILD has a sudo call inside it (or calls a script with a sudo call inside it), you will not be prompted for a password and thus may not notice what it is doing.

I understand, so basically equivalent of running makepkg with sudo? Pretty hardcore.

Arch Linux

#1 2024-11-02 20:35:41

Weird problem with makepkg

#2 2024-11-02 21:20:13

Re: Weird problem with makepkg

#3 2024-11-02 21:56:31

Re: Weird problem with makepkg

#4 2024-11-02 22:56:08

Re: Weird problem with makepkg

#5 2024-11-02 23:05:54

Re: Weird problem with makepkg

#6 2024-11-03 09:32:07

Re: Weird problem with makepkg

#7 2024-11-03 12:56:13

Re: Weird problem with makepkg

#8 2024-11-03 18:01:11

Re: Weird problem with makepkg

Board footer