On 2014-10-23, Romel Khan wrote:
> Here is what is happening: different users are actually running a
> program called myedit. So user are running say 'myedit file1'. The
> myedit program is actually running vim in it and editing a
> different file file2. People who run myedit edits the file using
> normal vi commands & thinking they are editing file1. They would
> be saving the normal :w, :wq or :x. I don't want the users to know
> that they actually ended up editing the file2 as that could be a
> security issue.
> I am not clear on how I can implement what you suggested and meet
> the above need.
If it's a security issue, then you don't want Vim to know the name
of the file, either. If Vim knows the name of the file, it would be
very easy for the user to find it.
A more secure approach would be to have myedit copy file2 to file1,
run vim on file1, then copy file1 to file2 when vim exits.
Regards,
Gary
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment