[Olsr-dev] [Olsr-commit] OLSR.org main repository branch, GSOC, updated. OLSRD_0_6_1_fixed-33-gd7b6715

[L. Aaron Kaplan]

On Jul 28, 2011, at 11:31 PM, Ferry Huberts wrote:

> 
> 
> On 07/28/2011 07:28 PM, L. Aaron Kaplan wrote:
>> (...)
>>>> 
>>>> What could be the worst thing happening ? Someone manages to remove all 
>>>> branches from our git repository. I get the mail, have some work and just put 
>>>> up a fresh repository from my mirror at git.hrogge.de.
>>>> 
>>>> After this I would have some more work to implement a write commit ACL system 
>>>> on our webpage (Most likely one that look at the bugtracker to see if the 
>>>> commiter has write access).
>>>> 
>>>> But I really see no purpose to do it now.
>>>> 
>>> 
>>> ok fair enough.
>>> 
>>> I'll adjust ;-)
>>> 
>> Ferry how would you adjust?
> 
> adjust == accept :-)

Hehe, ok. But do you have any better idea how to prevent backdoors?
It is actually IMHO a quite interesting discussion...

The only way I could think of is to have really thorough independent code reviews.

a.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2213 bytes
Desc: not available
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20110728/d257804b/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 243 bytes
Desc: This is a digitally signed message part
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20110728/d257804b/attachment.sig>