On Sat, 2005-05-07 at 13:48 +0200, Micha Lenk wrote:
> Severity #307366 Grave
> Merge #307784 #307366
> Thanks dear bugtracking system.
>
> On Fri, May 06, 2005 at 09:10:17PM +0200, Primoz wrote:
> > Is there a way to revert the upload to the NMUed one (which had security
&g
retitle 303198 ITA: pam-pgsql -- PAM module to authenticate using a
PostgreSQL database
signature.asc
Description: This is a digitally signed message part
On Fri, 2005-05-06 at 16:03 +0200, Joerg Wendland wrote:
> On Fri, May 06, 2005 at 09:33:09AM +0200, Primoz wrote:
> > I would be willing to fix and maintain the package if there is someone who
> > would be willing to sponsor the upload.
>
> Please go ahead, I'll sponso
Is there a way to revert the upload to the NMUed one (which had security
problems fixed), so package stays in sarge. I would need at least a week
to 14 days to port pam-mysql to pgsql (which seems like the best way to
go).
Primoz
On Fri, 2005-05-06 at 16:03 +0200, Joerg Wendland wrote:
> On
> On Thu, May 05, 2005 at 03:41:13PM +0200, Primoz Bratanic wrote:
> > Package: pam-pgsql
> > Severity: critical
> > Tags: security
> > Justification: root security hole
>
> > The problem reported in BUG#230875 and marked as fixed (NMU upload) was open
>
5 matches
Mail list logo
