public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@bitrange.com>
To: Daniel Kraft <d@domob.eu>
Cc: overseers@gcc.gnu.org
Subject: Re: Write access from compile farm
Date: Sun, 05 Dec 2010 00:21:00 -0000	[thread overview]
Message-ID: <alpine.BSF.2.00.1012041908010.12189@dair.pair.com> (raw)
In-Reply-To: <4CFA1571.5030300@domob.eu>

On Sat, 4 Dec 2010, Daniel Kraft wrote:

> some time ago I started using the GCC compile farm for development; so I'm
> wondering whether it is ok to have SVN write access from the accounts there --
> or this is considered insecure.  What are the policies there?
>
> As SVN write authentication is done with a public key, I guess that this means
> you have to set the access up appropriately up for any machine I want to use
> for check-in, right?  So... in case the write-access from compile farm is ok,
> can I generate a public key there and submit it to you -- or what should I do?

Assuming those who set policies don't disagree, and you're
talking about interactive session (i.e. not a cron job or robot)
just forward the *auhentication session*, no need to forge a new
key or deal with copying keys.  Look at what ssh says about its
-A option and ForwardAgent config.  (It might even be the
default for you.)  I'm not sure, but you might have to have
ssh-agent running.

(FWIW, no I wouldn't do that.  I just copy the patch and commit
from my "console" machine.  You say "tin-foil", I say "hats".)

brgds, H-P

  parent reply	other threads:[~2010-12-05  0:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-04 10:11 Daniel Kraft
2010-12-04 17:28 ` Christopher Faylor
2010-12-05  0:21 ` Hans-Peter Nilsson [this message]
2010-12-05  7:08   ` Christopher Faylor
2010-12-05  8:33     ` Christopher Faylor
2010-12-05 18:28     ` Christopher Faylor
2010-12-06 14:14     ` Christopher Faylor
2010-12-06 17:36     ` Daniel Kraft
2010-12-06 19:25     ` Christopher Faylor

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=alpine.BSF.2.00.1012041908010.12189@dair.pair.com \
    --to=hp@bitrange.com \
    --cc=d@domob.eu \
    --cc=overseers@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).