From: Andrew Reilly on
Hi there,

I haven't changed my configuration recently, but I've noticed
that sudo processes have stopped inheriting my environment
variables like MAKEOBJDIRPREFIX and PORTSDIR. I read the man
page, and tried sudo -E, and that brings back the "old"
behaviour, but that implies (according to the man page) that my
sudoers file has env_reset enabled, and it just doesn't.

Hmm. Closer reading of man 5 sudoers says that env_reset is
*on* by default. This is new to me.

Hmm. More digging in man pages: I need to add
Defaults !env_reset
under the #Defaults specification line.

Any thoughts or suggestions?

OK, so I've figured out the answer to my problem now, but since
I have seen one other post about the sudden disappearance of
MAKEOBJDIRPREFIX, and no obvious conversation about changes to
sudo, I'll post this anyway. Hope it helps someone.

Cheers,

--
Andrew
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: jhell on
On 05/22/2010 05:52, Andrew Reilly wrote:
> Hi there,
>
> I haven't changed my configuration recently, but I've noticed
> that sudo processes have stopped inheriting my environment
> variables like MAKEOBJDIRPREFIX and PORTSDIR. I read the man
> page, and tried sudo -E, and that brings back the "old"
> behaviour, but that implies (according to the man page) that my
> sudoers file has env_reset enabled, and it just doesn't.
>
> Hmm. Closer reading of man 5 sudoers says that env_reset is
> *on* by default. This is new to me.
>
> Hmm. More digging in man pages: I need to add
> Defaults !env_reset
> under the #Defaults specification line.
>
> Any thoughts or suggestions?
>
> OK, so I've figured out the answer to my problem now, but since
> I have seen one other post about the sudden disappearance of
> MAKEOBJDIRPREFIX, and no obvious conversation about changes to
> sudo, I'll post this anyway. Hope it helps someone.
>
> Cheers,
>

Attached is the copy of the sudoers.default take a look through it to
see how to set a environment variable for use with portupgrade or
portmaster etc...

--

jhell
From: Christian Weisgerber on
Andrew Reilly <areilly(a)bigpond.net.au> wrote:

> Hmm. Closer reading of man 5 sudoers says that env_reset is
> *on* by default. This is new to me.

Yes, the default for this changed a while back.

--
Christian "naddy" Weisgerber naddy(a)mips.inka.de

_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Andrew Reilly on
On Sat, May 22, 2010 at 08:02:19AM -0400, jhell wrote:
> Attached is the copy of the sudoers.default take a look through it to
> see how to set a environment variable for use with portupgrade or
> portmaster etc...

Hmm. I see that that is now the installed default, but of
course (by design) the fact that it has changed in this
significant way is not automatically reflected in the
already-in-use sudoers file. I think that this could usefully
have been flagged in UPDATING. I also prefer my fix (reverting
the default sense of env_reset): I know that I'm not going to
try to subvert any of my root processes by fiddling with LD_PATH
or whatever paranoia has produced this change. Sudoers(5) is too
complicated as it is, with too many options.

Cheers,

--
Andrew
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"