Bug 200 – Allow changing of SysLog facility and good/bad priorities via sudoers

Bug 200 - Allow changing of SysLog facility and good/bad priorities via sudoers


Summary:	Allow changing of SysLog facility and good/bad priorities via sudoers

Status:	RESOLVED INVALID

Product:	Sudo
Classification:	Unclassified
Component:	Sudo
Version:	1.6.8
Hardware:	All All

Importance:	normal normal
Assigned To:	Todd C. Miller

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-11-18 08:40 MST by Ashley Hooper
Modified:	2005-11-18 10:48 MST (History)
CC List:	0 users

See Also:

Attachments
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 Ashley Hooper 2005-11-18 08:40:02 MST

I believe that Sudo's SysLog features should be configurable without requiring a
recompile of Sudo.

At present many (if not most) installations of Sudo are probably from packages
produced by Linux distros and other entities such as Sunfreeware. 
Unfortunately, if a change to the SysLog funcionality is desired by the
end-user, these packages must be binned and a new version of Sudo compiled by
the end-user.

Comment 1 Todd C. Miller 2005-11-18 08:48:44 MST

Please see the sudoers manual, specicially the syslog_goodpri and syslog_badpri defaults 
options.  Of course, if sudoers cannot be parsed then the builtin defaults have to be used.