Re: vi secure

2008-05-22 Thread Derek Ragona
At 09:26 AM 5/22/2008, William O. Yates wrote: On 21/May/2008 19:26 Frank Shute wrote .. > On Wed, May 21, 2008 at 01:51:03PM -0700, William O. Yates wrote: > > > > [sent the below message thru the freebsd-security list with no > > answers, hope for more from freebsd-questions] > > > > Recently s

Re: vi secure

2008-05-22 Thread Christian Zachariasen
On Thu, May 22, 2008 at 4:39 PM, Frank Shute <[EMAIL PROTECTED]> wrote: > On Thu, May 22, 2008 at 07:26:20AM -0700, William O. Yates wrote: > > > > On 21/May/2008 19:26 Frank Shute wrote .. > > > On Wed, May 21, 2008 at 01:51:03PM -0700, William O. Yates wrote: > > > > > > > > [sent the below mess

Re: vi secure

2008-05-22 Thread Frank Shute
On Thu, May 22, 2008 at 07:26:20AM -0700, William O. Yates wrote: > > On 21/May/2008 19:26 Frank Shute wrote .. > > On Wed, May 21, 2008 at 01:51:03PM -0700, William O. Yates wrote: > > > > > > [sent the below message thru the freebsd-security list with no > > > answers, hope for more from freebsd-

Re: vi secure

2008-05-22 Thread William O. Yates
On 21/May/2008 19:26 Frank Shute wrote .. > On Wed, May 21, 2008 at 01:51:03PM -0700, William O. Yates wrote: > > > > [sent the below message thru the freebsd-security list with no > > answers, hope for more from freebsd-questions] > > > > Recently started using vi macros. > > Show us the macro.

Re: vi secure

2008-05-21 Thread Frank Shute
On Wed, May 21, 2008 at 01:51:03PM -0700, William O. Yates wrote: > > [sent the below message thru the freebsd-security list with no > answers, hope for more from freebsd-questions] > > Recently started using vi macros. Show us the macro. > > When attempting to use one which accessed the extern

vi secure

2008-05-21 Thread William O. Yates
[sent the below message thru the freebsd-security list with no answers, hope for more from freebsd-questions] Recently started using vi macros. When attempting to use one which accessed the external shell, got the following message: "The ! command is not supported when the secure edit option i