Bug 386 – sudo still resolves hostnames despite Defaults !fqdn

Bug 386 - sudo still resolves hostnames despite Defaults !fqdn


Summary:	sudo still resolves hostnames despite Defaults !fqdn

Status:	RESOLVED FIXED

Product:	Sudo
Classification:	Unclassified
Component:	Sudo
Version:	1.7.2
Hardware:	PC Linux

Importance:	low normal
Assigned To:	Todd C. Miller

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-01-01 15:59 MST by michael+sudo
Modified:	2010-07-09 10:36 MDT (History)
CC List:	0 users

See Also:

Attachments
Patch to defer fqdn setting until after sudoers is parsed (1.65 KB, patch) 2010-06-18 17:54 MDT, Todd C. Miller	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description michael+sudo 2010-01-01 15:59:19 MST

When configuring !fqdn, sudo still tries to resolve some hostname. The only possibility to kill this behaviour is by compiling without --with-fqdn, but I do not want to recompile the package every time a new version is released.

Resolving is unnecessary since I do not plan to use hostnames in my sudoers file and often I am without network access (or with rather slow network access).

Comment 1 Todd C. Miller 2010-06-18 16:44:13 MDT

Sudo currently uses the value of def_fqdn before sudoers is parsed, which means it gets the compiled in value (--with-fqdn) instead of the sudoers value.  Waiting until after sudoers has been parsed should be doable.  I'll look at this for sudo 1.7.3.

Comment 2 Todd C. Miller 2010-06-18 17:54:54 MDT

Created attachment 278 [details]
Patch to defer fqdn setting until after sudoers is parsed

I've attached a patch to defer checking fqdn status until after sudoers is parsed which should resolve this.  This change will be in sudo 1.7.3 due out at the end of June.

Comment 3 Todd C. Miller 2010-07-09 10:36:25 MDT

Fixed in sudo 1.7.3