sudo-1.8.10

[Fernando de Oliveira]

​http://www.sudo.ws/sudo/dist/sudo-1.8.10.tar.gz

[Fernando de Oliveira]

--with-timedir=DIR deprecated

use now:

  --with-rundir=DIR
        Set the directory to be used for sudo-specific files that
        do not survive a system reboot.  This is typically where
        the time stamp directory is located.  By default, configure
        will use the first existing directory in the following list:
	    /var/run, /var/db, /var/lib, /var/adm, /usr/adm
	This directory should be cleared when the system reboots.
	On systems that lack /var/run, the default rundir and vardir
	may be the same.  In this case, only the ts directory inside
	the rundir needs to be cleared at boot time.

Since we have /var/run and it apparently is cleared on reboot, I can replace

--with-timedir=/var/lib/sudo

by

--with-rundir=/var/run/sudo

Or, as suggested, just remove --with-timedir and leave the application use its defaults.

As this is a security issue, I will sopt with sudo and go to another package, while waiting some input, please.

Thanks in advance.

[Fernando de Oliveira]

Forgot: was it decided to leave sudo with --libexec?

[Pierre Labastie]

Replying to fo:

Forgot: was it decided to leave sudo with --libexec?

Looks like it has been forgotten, since the installed directories line has /usr/libexec/sudo.

[Pierre Labastie]

About rundir: I think configure adds sudo, that is, if you input:

--with-rundir=/some/path

you'll end up with the timestamp parent dir being /some/path/sudo. So, I think the default is OK.

[Fernando de Oliveira]

OK. Thanks, Pierre

[bdubbs@…]

What's the default for rundir? How about using /run/sudo?

[Fernando de Oliveira]

Default: /var/run/sudo

--with-rundir=/var/run/sudo: same as default

--with-rundir=/run/sudo: as the value indicates (/run/sudo)

--with-rundir=/run: /run (no "sudo' created, if not explicitly written, unless they are the defaults).

The deprecated hada in the book the explanation:

"--with-timedir=/var/lib/sudo: This switch places the variable time stamp files in a FHS compatible location."

The reason I asked was if there is some FHS rule for the new variable or some particularity from (B)LFS to not be in the default /var/run/sudo.

My preference, if there is no special reason, is /var/run/sudo. The developpers there like /var/run. Even there is a new directory /var/db/sudo.

So, Bruce, if you do not have a special reason, I would prefer /var/run/sudo (default, no switches, no explanations needed at the text).

What do you think?

[bdubbs@…]

That's OK, but remember /var/run -> /run. I just wanted to be direct.

[Fernando de Oliveira]

Understood, if a switch was needed, I would put that, then. Good enough reason, being direct. When time comes, will use this advice. Thanks.

[Fernando de Oliveira]

Fixed at r12852.

[ken@…]

Replying, belatedly, to Fernando and Pierre about libexecdir :

I reinstated it with the following command explanation: --libexecdir=/usr/lib/sudo: This switch controls where private programs are installed. Everything in that directory is a library, so they belong under /usr/lib instead of /usr/libexec.

And yes, I did forget to check the list of directories. I still think that libs don't belong in /usr/libexec (I'm taking a *pedantic* view of the FHS, since I believe it is intended for pedants :-) but Bruce queried this - thread at ​http://www.mail-archive.com/blfs-dev@linuxfromscratch.org/msg16480.html and I'm not going to press the point.

The people doing the work (that's you guys, until you burn out) get to make the decisions. Whether I agree with them, or use them in my own builds, is neither here nor there. Live Long And Prosper!

[Fernando de Oliveira]

Will get it back to what you intended. Sorry for undoing your work.

[Fernando de Oliveira]

Thanks. Switch is back at r12854.

[Fernando de Oliveira]

LLAP!