util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bernhard Voelker <mail@bernhard-voelker.de>
To: kerolasa@gmail.com, Sami Kerola <kerolasa@iki.fi>
Cc: util-linux <util-linux@vger.kernel.org>
Subject: Re: [PATCH 5/5] vipw: make vim writebackup mode work
Date: Mon, 6 Aug 2012 10:28:32 +0200 (CEST)	[thread overview]
Message-ID: <1829782354.1276693.1344241712777.JavaMail.open-xchange@email.1und1.de> (raw)
In-Reply-To: <CAG27Bk157so8J93EfTCQ1YBjXBUtYVVLcgpKg4eJdN6o77cN3A@mail.gmail.com>

On August 6, 2012 at 9:30 AM Sami Kerola <kerolasa@iki.fi> wrote:

> On Mon, Aug 6, 2012 at 8:14 AM, Bernhard Voelker
> <mail@bernhard-voelker.de> wrote:

> Hi Berny,
>
> Yes, I did mention file exchange should probably warn.  When I
> added the warning it looked like noise, and I could not get
> message right.
>
> > We're talking about the intermediate file (in /tmp), but as it's
> > name is visible e.g. in ps listings, I'd recommend to be cautious
> > about it.
>
> The temporary file in vipw case is created to /etc/ and moved in
> place within directory.  Earlier /tmp/ was used, but it resulted
> to non-atomic move and rename(2) complaining about device
> boundary.  See following commit for details.

yes, /etc right.

> I am assuming /etc/ is not normally writable for users, so the
> security problem should be mostly theoretical.  That said perhaps
> a message such as
>
> vipw: intermediate /etc/vipw.XXXXX file change
>
> might be appropriate, if it is explained in vipw(8).  Or is it
> simply noise no-one cares?

Right, /etc is quite safe. Therefore, as vipw is deprecated anyway,
I'd say your patch is okay.

Have a nice day,
Berny


  reply	other threads:[~2012-08-06  8:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-04  7:33 [PATCH 0/5] pull: release preparations, umount.8 and vipw fix Sami Kerola
2012-08-04  7:33 ` [PATCH 1/5] docs: ftp server does no longer support util-linux-ng Sami Kerola
2012-08-04  7:33 ` [PATCH 2/5] docs: update TODO Sami Kerola
2012-08-04  7:33 ` [PATCH 3/5] docs: add sys-utils/umount.8 manual page Sami Kerola
2012-08-04  7:33 ` [PATCH 4/5] build-sys: add files make check generates in gitignore Sami Kerola
2012-08-04  7:33 ` [PATCH 5/5] vipw: make vim writebackup mode work Sami Kerola
2012-08-06  6:14   ` Bernhard Voelker
2012-08-06  7:30     ` Sami Kerola
2012-08-06  8:28       ` Bernhard Voelker [this message]
2012-08-06 13:40 ` [PATCH 0/5] pull: release preparations, umount.8 and vipw fix Karel Zak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1829782354.1276693.1344241712777.JavaMail.open-xchange@email.1und1.de \
    --to=mail@bernhard-voelker.de \
    --cc=kerolasa@gmail.com \
    --cc=kerolasa@iki.fi \
    --cc=util-linux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).