Simon Ruderich wrote:
> Making viminfo readable by other users is most likely not useful. To
> prevent information leakage enforce mode 0600.
>
> The race condition fixed in the last patch could also cause viminfo
> files readable by other uses. Enforcing mode 0600 restores the
> originally indented permissions.
I still don't see how the original problem could occur. If we can't
write a test for it, I don't see a reason to take away the documented
feature, that two users (likely to be the same person with two user
accounts) can share a viminfo file. This won't be used often, but can
be very annoying if it stops working.
If the problem somehow does occur, then the problem will fix itself with
the new Vim when it happens again.
I'll make the check for the group stricter, like what we did with the
swap file.
--
ARTHUR: ... and I am your king ....
OLD WOMAN: Ooooh! I didn't know we had a king. I thought we were an
autonomous collective ...
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_dev" 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_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
