RE: Vim does not do encryption no more on RHEL5?

 Thanks for the reply. After sending that e-mail, I kept looking. What I noticed was there are two vi binaries, /bin/vi and /usr/bin/vim. As a regular user, 'vi' is aliased to /usr/bin/vim, which does support the -x flag. As root, it gets /bin/vi - which does not support the -x flag. Note that when one does a /bin/vi -h it is vim and the same version as /usr/bin/vim, but cut down to size.
Thanks again.

~smbinyon

-----Original Message-----

From: redhat-list-bounces@redhat.com
[mailto:redhat-list-bounces@redhat.com] On Behalf Of George Magklaras Sent: Friday, October 12, 2007 2:15 AM
To: General Red Hat Linux discussion list Subject: Re: Vim does not do encryption no more on RHEL5?

That's a bit weird. I just checked and vim -x works on my RHEL 5 box. Also vim -h displays the -x option. Are you sure you are not using some other version of vim compiled locally in your system outside the RHEL distro and overriding your path? In my box:

# type vim
vim is hashed (/usr/bin/vim)
# ldd /usr/bin/vim

         libtermcap.so.2 => /lib64/libtermcap.so.2 (0x00000033cde00000)
         libselinux.so.1 => /lib64/libselinux.so.1 (0x00000033d0600000)
         libacl.so.1 => /lib64/libacl.so.1 (0x00000033d4800000)
         libgpm.so.1 => /usr/lib64/libgpm.so.1 (0x00000033cae00000)
         libperl.so =>

         libresolv.so.2 => /lib64/libresolv.so.2 (0x00000033d1e00000)
         libutil.so.1 => /lib64/libutil.so.1 (0x00000033d8a00000)
         libc.so.6 => /lib64/libc.so.6 (0x00000033c9e00000)
         libm.so.6 => /lib64/libm.so.6 (0x00000033ca200000)
         libdl.so.2 => /lib64/libdl.so.2 (0x00000033ca600000)
         libpthread.so.0 => /lib64/libpthread.so.0 (0x00000033caa00000)
         libsepol.so.1 => /lib64/libsepol.so.1 (0x00000033d0200000)
         /lib64/ld-linux-x86-64.so.2 (0x00000033c9a00000)
         libattr.so.1 => /lib64/libattr.so.1 (0x00000033d3e00000)
         libnsl.so.1 => /lib64/libnsl.so.1 (0x00000033d2200000)
         libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00000033dca00000)

Libcrypt is at the bottom. Can you check your vim path?

GM

Do you need help?

In addition to our free technical library, Pantek provides professional IT services to companies who utilize Open Source software: Learn more about Pantek's Technical Support offerings Place an order for 24/7/365 Technical Support here Learn more about Pantek, who we are, and what we do Chat with a Live Operator Related redhat.com Links fedora-list pump-list redhat-announce-list redhat-devel-list redhat-install-list redhat-list redhat-watch-list Request more information about Pantek

--
--

George Magklaras

Senior Computer Systems Engineer/UNIX Systems Administrator EMBnet Technical Management Board The Biotechnology Centre of Oslo, University of Oslo http://www.biotek.uio.no/

EMBnet Norway: http://www.no.embnet.org/

Binyon Steve Contr 705 CTS/ASRCC wrote:

> We are evaluating RHEL 5 and found this:
> 
> Under RHEL 3 and 4, one could do 'vi -x' to have the file password 
> protected and encrypted.  Under RHEL 5, this appears to be no longer 
> true.  So, what is used under RHEL 5 that replaces this functionality?
> Btw the man page states that its still valid, but vim -h does not show

> the -x flag.
> 
> Thanks in advance.
> 
> ~smbinyon

--

redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list

--

redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list Received on Fri Oct 12 09:27:59 2007