| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Aidan Van Dyk <aidan(at)highrise(dot)ca>, 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-10-07 19:37:48 |
| Message-ID: | AANLkTikiz7amu4zzR7iLs8w5mttc3iSS=UnZL_zOUonq@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | buildfarm-members pgsql-hackers |
On Thu, Oct 7, 2010 at 21:31, Andrew Dunstan <andrew(at)dunslane(dot)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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2010-10-08 01:52:33 | Re: Git cvsserver serious issue |
| Previous Message | Andrew Dunstan | 2010-10-07 19:31:22 | Re: Git cvsserver serious issue |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2010-10-07 19:50:32 | Timeout and Synch Rep |
| Previous Message | Greg Stark | 2010-10-07 19:35:10 | Re: On Scalability |