Re: Git cvsserver serious issue - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Git cvsserver serious issue
Date
Msg-id AANLkTikiz7amu4zzR7iLs8w5mttc3iSS=UnZL_zOUonq@mail.gmail.com
Whole thread Raw
In response to Re: Git cvsserver serious issue  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Git cvsserver serious issue
List pgsql-hackers
On Thu, Oct 7, 2010 at 21:31, Andrew Dunstan <andrew@dunslane.net> wrote:
>
>
> On 10/07/2010 10:11 AM, Magnus Hagander wrote:
>>
>>> OTOH, this patch seems pretty small and simple to maintain.
>>
>> True, it is rather small.
>>
>> Does anybody know if there's an automated way to maintain that on
>> freebsd ports, and if so, how that works? I want to be *sure* we can't
>> accidentally upgrade git-cvsserver *without* the patch, since that is
>> a security issue.
>>
>
> Why not just make a local copy somewhere else and patch and run that? It's
> just a Perl script, no?

Yeah, but then we have to remember to manually patch that one when
somebody *else* finds/fixes a security issue. We have automatic
monitoring on the ports stuff to detect when that happens..

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/


pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: On Scalability
Next
From: Josh Berkus
Date:
Subject: Timeout and Synch Rep