On 11/15/2012 08:18 AM, james gray wrote:
i am just wondering.
why would vim be slapped around thru many links just to come back to its
original file path origin with out write privileges to the end usr who
is not root.
path = /usr/local/bin, usr/bin, /bin, usr/local/game
ls -l /usr/bin/vim
lrwxrwxrwx -> etc/alternatives/vim
ls -l etc/alternatives/vim
lrwxrwxrwx -> /usr/bin/vim.basic
ls -l /usr/bin/vim.basic
Try replacing the 'ls -l' in the above examples with 'file' and you will
see why you don't have write privileges.
are there programming or script conditionals placed on vim by vim being
passed through each different directory environment ?.
is there a for see able security issue coming from the programers view
point , to have vim.basic with its file access as they are root root
can the end usr mutilate the file access and group of vim.basic and
root admin rwxrwx---
- From: james gray <firstname.lastname@example.org>