+++ /dev/null
---- sudo-1.7.2p1/visudo.pod 2008-11-15 13:34:01.000000000 -0500
-+++ sudo-1.7.2p1-manpage/visudo.pod 2009-11-07 18:54:00.841321731 -0500
-@@ -39,15 +39,18 @@
-
- There is a hard-coded list of editors that B<visudo> will use set
- at compile-time that may be overridden via the I<editor> I<sudoers>
--C<Default> variable. This list defaults to the path to L<vi(1)> on
--your system, as determined by the I<configure> script. Normally,
-+C<Default> variable. On Debian systems, this list defaults to
-+/usr/bin/editor, which is meant to be a system-wide default editor
-+chosen through the alternatives system. Normally,
- B<visudo> does not honor the C<VISUAL> or C<EDITOR> environment
- variables unless they contain an editor in the aforementioned editors
--list. However, if B<visudo> is configured with the I<--with-enveditor>
-+list. However, if B<visudo> is configured with the I<--with-env-editor>
- option or the I<env_editor> C<Default> variable is set in I<sudoers>,
- B<visudo> will use any the editor defines by C<VISUAL> or C<EDITOR>.
- Note that this can be a security hole since it allows the user to
- execute any program they wish simply by setting C<VISUAL> or C<EDITOR>.
-+Despite this potential risk, sudo on Debian is compiled with the
-+I<--with-env-editor> flag.
-
- B<visudo> parses the I<sudoers> file after the edit and will
- not save the changes if there is a syntax error. Upon finding