This is for Debian policy.
----------------------------------------
cupsys (1.1.19candidate4-1) unstable; urgency=low
Move /etc/printcap.cups to /var/run/cups/printcap, since it's
generated and non-editable. Also, take care of the /etc/printcap
symlink. Closes: #187954.
----------------------------------------
--
Kenshi Muto
<email address hidden>
Message-Id: <email address hidden>
Date: Fri, 06 Aug 2004 21:47:28 +0900
From: Kenshi Muto <email address hidden>
To: <email address hidden>
Subject: Re: Bug#263953: cupsys: New configuration file doesn't enable access and error logging by
default
At Fri, 06 Aug 2004 13:54:20 +0200,
Michal Pasternak wrote:
> Package: cupsys
> Version: 1.1.20final+rc1-5
> Severity: grave
> Justification: user security hole
Do you really understand what 'grave' means?
> Here are differences that I've found, while installing latest cupsys package:
What did you compare?
> -AccessLog /var/log/ cups/access_ log cups/access_ log cups/error_ log cups/error_ log cups/page_ log cups/page_ log
> +#AccessLog /var/log/
> -ErrorLog /var/log/
> +#ErrorLog /var/log/
> -PageLog /var/log/
> +#PageLog /var/log/
>
> I think those settings should be enabled.
Of course they are already enabled. You would show correct log if you
check once. They are default value.
> Also, cups/printcap
> -Printcap /etc/printcap.cups
> +Printcap /var/run/
This is for Debian policy. ------- ------- ------- ------- ----- e4-1) unstable; urgency=low cups/printcap, since it's ------- ------- ------- ------- -----
-------
cupsys (1.1.19candidat
Move /etc/printcap.cups to /var/run/
generated and non-editable. Also, take care of the /etc/printcap
symlink. Closes: #187954.
-------
--
Kenshi Muto
<email address hidden>