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

Benson (spam-protected)
Sat Jun 25 21:05:30 CEST 2011

Hi, I'm Benson. I am hoping to get up to speed on mesh networks and help out
if I can.

I can't help thinking the worst case scenario is that some unsavory person
makes a seemingly innocuous commit that introduces a backdoor or other
security flaw which they can then exploit in real-world installations of
olsrd. I think this is unlikely, but if I owned the repository I'd give it
serious consideration.

I look forward to becoming more involved in the project as I collect the
necessary hardware to begin using mesh networks.

On Jun 25, 2011 8:42 AM, "Ferry Huberts" <(spam-protected)> wrote:
> On 06/25/2011 01:37 PM, Henning wrote:
>> On Friday 24 June 2011 23:38:19 Ferry Huberts wrote:
>>> no no, please
>>> I'm sorry for the misunderstanding!
>>> it's ok you did this.
>>> it's just that this commit triggered something I had on my mind for a
>>> while now.
>>> nothing against anyone in the project. I just would be more comfortable
>>> with not the entire world having commit access :-)
>> Why ?
>> I have to say we never had problems with this for years.
>> We have problem getting people supporting the project, building up more
>> barriers for them is not a sollution.
>> 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
>> 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
>> 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 ;-)
> grtz
> --
> Ferry Huberts
> --
> Olsr-dev mailing list
> (spam-protected)
> https://lists.olsr.org/mailman/listinfo/olsr-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20110625/48abfcc4/attachment.html>

More information about the Olsr-dev mailing list