unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Cc: Lee Hambley <leehambley@me.com>
Subject: Re: PID file ownership and group
Date: Tue, 20 Sep 2011 18:03:14 +0000	[thread overview]
Message-ID: <20110920180314.GA30482@dcvr.yhbt.net> (raw)
In-Reply-To: <6F8DA070-5CC5-4107-8706-34D3F61D57C2@me.com>

Lee Hambley <leehambley@me.com> wrote:
> I'm using unicorn in an environment with /very/ strict permissions
> (one might so as far as to say that the sysadmin is being too careful)
> and I've observed that when starting Unicorn via `upstart` (runs as
> root) with unicorn.rb configured to suid and sguid, the logs and other
> files are correctly owned by `selected user:group` but the pidfile is
> owned by root:root. Owing to very restrictive unmasking and other
> permissions, this file is not readable by any lower-level users, and
> thus one has to be root to read the pidfile.
> 
> What's the logic here, is it a bug, an oversight or an intentional
> design, naturally one can use `ps` or any other number of ways to get
> a pid, so protecting the pidfile doesn't seem like a security concern/

I didn't think of it until now, but I don't think it's necessary to
expose.  With the exception of creating Unix domain sockets, unicorn
always respects the umask given to it, and unicorn only changes
permissions inside worker processes.

Also, nginx (where unicorn draws many design elements from) does not
change the permissions of the pid file, either.

> Of course this is somewhat academic, as one must be root to signal the
> process anyway, but I'll cross that particular bridge when I come to
> it!

Yeah, there's no point in knowing it unless you can send signals to it.

-- 
Eric Wong
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying

  reply	other threads:[~2011-09-20 18:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-20  8:18 PID file ownership and group Lee Hambley
2011-09-20 18:03 ` Eric Wong [this message]
     [not found]   ` <FF8DE317-F98B-4D13-B8D7-95B4B922A6BF@me.com>
2011-09-20 20:23     ` Eric Wong

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

  List information: https://yhbt.net/unicorn/

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

  git send-email \
    --in-reply-to=20110920180314.GA30482@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --cc=leehambley@me.com \
    --cc=mongrel-unicorn@rubyforge.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.
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/unicorn.git/

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 read-only IMAP folder(s) and NNTP newsgroup(s).