Re: Git cvsserver serious issue

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Git cvsserver serious issue
Date: 2010-09-23 15:32:06
Message-ID: 4C9B72F6.3050201@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: buildfarm-members pgsql-hackers

On 09/23/2010 11:18 AM, Magnus Hagander wrote:
> On Thu, Sep 23, 2010 at 17:16, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Magnus Hagander<magnus(at)hagander(dot)net> writes:
>>> So, I found (with some helpful hints from Robert who caught the final
>>> nail in the coffin) a good reason why we really can't run a
>>> git-cvsserver globally.
>>> Any user can point their cvs client at the repository. And check out
>>> an arbitrary branch, tag *or individual commit*. Doing so will create
>>> a 50Mb sqlite database on the server with cache information about that
>>> head.
>> I'm still wondering why we don't simply lobotomize git-cvsserver to
>> refuse requests to check out anything except the active branch tips.
>> It's only a Perl script. I could probably hack it in an hour,
>> there are those here who could do it in ten minutes.
> Yeah, that would not be a bad idea - if someone can do it who feels
> comfortable doing it :-)
>
> I could probably hack it up as well, but I wouldn't trust myself to
> have convered all the bases.
>

Are we sure that's going to stop the DOS issue?

cheers

andrew

In response to

Responses

Browse buildfarm-members by date

  From Date Subject
Next Message Stefan Kaltenbrunner 2010-09-23 15:36:33 Re: Git cvsserver serious issue
Previous Message David Fetter 2010-09-23 15:19:41 Re: Git cvsserver serious issue

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2010-09-23 15:32:38 Re: Configuring synchronous replication
Previous Message David Fetter 2010-09-23 15:19:41 Re: Git cvsserver serious issue