* Re: Write access from compile farm
2010-12-05 7:08 ` Christopher Faylor
@ 2010-12-05 8:33 ` Christopher Faylor
2010-12-05 18:28 ` Christopher Faylor
` (3 subsequent siblings)
4 siblings, 0 replies; 9+ messages in thread
From: Christopher Faylor @ 2010-12-05 8:33 UTC (permalink / raw)
To: overseers, Daniel Kraft, Hans-Peter Nilsson
On Sat, Dec 04, 2010 at 07:21:35PM -0500, Hans-Peter Nilsson wrote:
>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.
This is actually a better way of doing this than what I suggested since
what I suggested means copying a private key to a semi-public machine.
>(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".)
Yeah, ditto, there too.
cgf
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Write access from compile farm
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
` (2 subsequent siblings)
4 siblings, 0 replies; 9+ messages in thread
From: Christopher Faylor @ 2010-12-05 18:28 UTC (permalink / raw)
To: overseers, Daniel Kraft, Hans-Peter Nilsson
On Sat, Dec 04, 2010 at 07:21:35PM -0500, Hans-Peter Nilsson wrote:
>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.
This is actually a better way of doing this than what I suggested since
what I suggested means copying a private key to a semi-public machine.
>(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".)
Yeah, ditto, there too.
cgf
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Write access from compile farm
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
4 siblings, 0 replies; 9+ messages in thread
From: Christopher Faylor @ 2010-12-06 14:14 UTC (permalink / raw)
To: overseers, Daniel Kraft, Hans-Peter Nilsson
On Sat, Dec 04, 2010 at 07:21:35PM -0500, Hans-Peter Nilsson wrote:
>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.
This is actually a better way of doing this than what I suggested since
what I suggested means copying a private key to a semi-public machine.
>(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".)
Yeah, ditto, there too.
cgf
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Write access from compile farm
2010-12-05 7:08 ` Christopher Faylor
` (2 preceding siblings ...)
2010-12-06 14:14 ` Christopher Faylor
@ 2010-12-06 17:36 ` Daniel Kraft
2010-12-06 19:25 ` Christopher Faylor
4 siblings, 0 replies; 9+ messages in thread
From: Daniel Kraft @ 2010-12-06 17:36 UTC (permalink / raw)
To: overseers, Daniel Kraft, Hans-Peter Nilsson
Hi,
Christopher Faylor wrote:
> On Sat, Dec 04, 2010 at 07:21:35PM -0500, Hans-Peter Nilsson wrote:
>> 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.
>
> This is actually a better way of doing this than what I suggested since
> what I suggested means copying a private key to a semi-public machine.
thanks a lot for the useful tipps!
Yours,
Daniel
--
http://www.pro-vegan.info/
--
Done: Arc-Bar-Cav-Kni-Ran-Rog-Sam-Tou-Val-Wiz
To go: Hea-Mon-Pri
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Write access from compile farm
2010-12-05 7:08 ` Christopher Faylor
` (3 preceding siblings ...)
2010-12-06 17:36 ` Daniel Kraft
@ 2010-12-06 19:25 ` Christopher Faylor
4 siblings, 0 replies; 9+ messages in thread
From: Christopher Faylor @ 2010-12-06 19:25 UTC (permalink / raw)
To: Daniel Kraft, overseers, Hans-Peter Nilsson
Sorry for the duplication. I don't know why that happened. Guess it will be interesting
to see if this triggers it too.
cgf
^ permalink raw reply [flat|nested] 9+ messages in thread