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

[L. Aaron Kaplan]

(...)
>> 
>> 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?
It is an interesting discussion indeed. And I have to admit, I sort of like the Linux kernel approach because it automatically enforces some quality control / self checking. If everybody who wants to commit something knows that the big benevolent dictator will indeed look at it, the code might be cleaner.

On the other hand , I believe a well written backdoor will escape even Linus...

Ferry, what solution would you propose for preventing these backdoors?


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/92726dba/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/92726dba/attachment.sig>