Received: from localhost (maia-1.hub.org [200.46.204.191])
	by postgresql.org (Postfix) with ESMTP id 338629FB323;
	Fri,  6 Apr 2007 14:09:07 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024)
	with ESMTP id 25071-05; Fri,  6 Apr 2007 14:08:56 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.4
X-Greylist: from auto-whitelisted by SQLgrey-1.7.4
Received: from cronos.madness.at (madness.at [217.196.146.217])
	by postgresql.org (Postfix) with ESMTP id EEBB19FB20E;
	Fri,  6 Apr 2007 14:08:55 -0300 (ADT)
Received: from mastermind.kaltenbrunner.cc ([83.215.233.60])
	by cronos.madness.at with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.63) (envelope-from <stefan@kaltenbrunner.cc>)
	id 1HZrvd-0006RM-Hv; Fri, 06 Apr 2007 19:08:55 +0200
Message-ID: <46167E9F.9000707@kaltenbrunner.cc>
Date: Fri, 06 Apr 2007 19:08:47 +0200
From: Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>
User-Agent: Icedove 1.5.0.9 (X11/20061220)
MIME-Version: 1.0
To: Dave Page <dpage@postgresql.org>
CC: PostgreSQL www <pgsql-www@postgresql.org>
Subject: Re: pgFoundry tracker spam
References: <200704061655530000@294230686>
In-Reply-To: <200704061655530000@294230686>
X-Enigmail-Version: 0.94.2.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200704/15
X-Sequence-Number: 11765

Dave Page wrote:
> 
>> ------- Original Message -------
>> From: Dave Page <dpage@postgresql.org>
>> To: Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>
>> Sent: 06/04/07, 08:26:25
>> Subject: Re: [pgsql-www] pgFoundry tracker spam
>>> sorry for the late response but there is actually a way to change that
>>> setting afterwards though it is not that obvious how ...
>>> For your reference - log into pgfoundy and choose your project.
>>> Now go to "admin" - and choose "edit observer" from the list of the
>>> developers on the right side and on that page you can change edit the
>>> permission on your trackers.
>> Thanks Stefan. You're right - it's not exactly obvious is it!
> 
> Unfortunately, it doesn't seem to have worked :-(

yeah - it seems there are multiple issues involved with that. The
(modified) version of gforge we are running is simply not checking for
proper login status and anonymous posting rights in a number of code paths.
It seems that upstream fixed a lot of similiar issues already but
upgrading requires quite a lot of work :-(
I have already started a discussion about that on the gforge-admin list
and I hope we have a final solution to that sooner than later ...

Meanwhile I have backported some of the relevant locking upstream
changes to our version though I'm not totally convinced that this will
fix it fully.


regards

Stefan