[3019] in bugtraq
Re: vulnerability in vi under AIX 3.2 (IN LINUX)
daemon@ATHENA.MIT.EDU (kay hashimoto)
Thu Jul 25 22:12:41 1996
Date: Thu, 25 Jul 1996 21:36:56 -0400
Reply-To: Bugtraq List <BUGTRAQ@netspace.org>
From: kay hashimoto <kjhashim@hcs.HARVARD.EDU>
To: Multiple recipients of list BUGTRAQ <BUGTRAQ@netspace.org>
In-Reply-To: <4t7vne$40c@fludd.myrus> from "Zygo Blaxell" at Jul 25,
96 10:18:22 am
>'vim file' will happily scribble all over 'file.swp', without regard to
>who owns it, what it's a symlink to, etc. Further, in the event of a
>system crash, the .swp file is left lying around, causing unpredictable
>results if you use vim to edit files in SysV-style init runlevel
>directories.
When does vim do this? One of the purposes of the .swp file is to
prevent concurrent editing of one file, so when vim sees file.swp in
the current directory, it gives a warning and writes to file.swo.
