Bug#680624: vim-addon-manager - Create stuff in /var/lib/vim unreadable for users

James McCoy jamessan at debian.org
Tue Dec 3 04:20:28 UTC 2013

Control: clone -1 -2
Control: severity -2 normal
Control: retitle -2 Honor root's umask when performing root-user (not system) actions

On Mon, Jul 16, 2012 at 09:50:41PM -0300, Antonio Terceiro wrote:
> James McCoy escreveu isso aí:
> > On Sat, Jul 07, 2012 at 02:53:13PM +0200, Bastian Blank wrote:
> > > vim-addons respects umask a bit too much. It creates anything in
> > > /var/lib/vim, aka for any user, respecting the umask of the calling
> > > process, 027 in my case. So no user can read the stuff.
> > 
> > Attached patch uses a specific mode when installing an addon as root.
> > 
> > However, this doesn't correctly handle the case of an actual root user
> > installing addons for themself.  This would be better handled by
> > tracking whether it's a "system" install or not, instead of an install
> > being performed by root.
> Right. I can't think ATM of a way to get that information ("is this a
> system-wide install?") available in a sane way down to the addon level
> without a major refactoring of the code ... :-/

Ok, I'm creating a separate issue to track detecting that difference and
I'll push my proposed fix for the original issue shortly.

GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <jamessan at debian.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-vim-maintainers/attachments/20131202/4a82a850/attachment.sig>

More information about the pkg-vim-maintainers mailing list