9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] https/factotum question
Date: Tue, 21 Feb 2006 18:00:34 -0500	[thread overview]
Message-ID: <110ac39c99871b98c5739a23de17b6e2@swtch.com> (raw)
In-Reply-To: <2245.1140562458@piper.nectar.cs.cmu.edu>

> But it looks to me as if the closest I can come at
> present is for the factotum behind /srv/factotum to
> contain the RSA key tagged with "owner=none", which I
> think means that anybody who is "none", not just the
> one web server process and its descendants, can sign
> things.

true.

> I notice in httpd.c that some things are opened before
> becomenone()... would it make sense to somehow latch
> onto a "private" factotum at this point and then use
> it after becomenone()?

nope, can't do that.  becomenone() is only useful if you
then reconstruct your name space from scratch, and that 
means remounting factotum.

your only option is to open the fd for mounting the secret
factotum, then call becomenone(), then mount the fd,
which is still open but otherwise inaccessible to you.

the web server isn't signing pages, just that the connection
is to the right machine.  we figure if you can talk to that factotum,
you're on the machine, so close enough.  so we just run httpd
as none and let any process use the ssl certificate.

russ



  reply	other threads:[~2006-02-21 23:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-21 22:54 Dave Eckhardt
2006-02-21 23:00 ` Russ Cox [this message]
2006-02-22 23:31   ` Dave Eckhardt

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=110ac39c99871b98c5739a23de17b6e2@swtch.com \
    --to=rsc@swtch.com \
    --cc=9fans@cse.psu.edu \
    /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).