[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#698793: Patch

Hi Joost,

On Sun, Jan 27, 2013 at 12:30:37PM +0100, Joost van Baal-Ilić wrote:
> Thanks a lot!  I'll wait for your next revision of this patch, as we've
> just discussed IRL.

Here it is.  I've tested the proposed solution (moving your sudoers to
sudoers.d and keeping the default one) after an upgrade to
sudo-1.8.5p2-1, and it works.

Tim Marston
Index: en/upgrading.dbk
--- en/upgrading.dbk	(revision 9557)
+++ en/upgrading.dbk	(working copy)
@@ -1227,6 +1227,37 @@
 may be required, either before or during the upgrade; these are detailed
 below on a per-package basis.
+<section id="issues-sudo">
+If you have modified <filename>/etc/sudoers</filename> then you should be aware
+of changes made to how <systemitem role="package">sudo</systemitem>
+configuration is handled.  The default <filename>/etc/sudoers</filename> now
+includes the following two directives:
+<programlisting>Defaults        secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"</programlisting>
+<programlisting>#includedir /etc/sudoers.d</programlisting>
+Neither of these entries are added to your <filename>/etc/sudoers</filename>
+automatically during the upgrade.  (Although you will still be able to run
+<command>sudo</command> commands by specifying their fully-qualified path.)  So
+you might wish to consider migrating your changes to the new
+<filename>/etc/sudoers.d</filename> directory and using the default
+<filename>/etc/sudoers</filename> file.  For example:
+# mv /etc/sudoers /etc/sudoers.d/mychanges
+# mv /etc/sudoers.dpkg-new /etc/sudoers
+You may also need to edit your <filename>/etc/sudoers.d/mychanges</filename> to
+remove unwanted <literal>Defaults</literal> and <literal>#includedir</literal>
+entries.  You should use <command>visudo</command> for this:
+# visudo -f /etc/sudoers.d/mychanges
 <section id="issues-evolution">

Reply to: