-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/11/2009 12:41 PM, Stephen Gallagher wrote:
> On 11/11/2009 09:22 AM, Sumit Bose wrote:
>> Hi,
>
>> this patch fixes a bug in the procy provider and makes
>> proxy_pam_target a mandatory option, because we do not ship a matching
>> pam configurat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/11/2009 09:22 AM, Sumit Bose wrote:
> Hi,
>
> this patch fixes a bug in the procy provider and makes
> proxy_pam_target a mandatory option, because we do not ship a matching
> pam configuration for the old default.
>
> bye,
> Sumit
>
>
>
> _
On Wed, Nov 11, 2009 at 09:55:25AM -0500, Stephen Gallagher wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 11/11/2009 09:22 AM, Sumit Bose wrote:
> > Hi,
> >
> > this patch fixes a bug in the procy provider and makes
> > proxy_pam_target a mandatory option, because we do not ship
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/11/2009 09:22 AM, Sumit Bose wrote:
> Hi,
>
> this patch fixes a bug in the procy provider and makes
> proxy_pam_target a mandatory option, because we do not ship a matching
> pam configuration for the old default.
>
> bye,
> Sumit
>
>
>
> _
Hi,
this patch fixes a bug in the procy provider and makes
proxy_pam_target a mandatory option, because we do not ship a matching
pam configuration for the old default.
bye,
Sumit
>From d5e97eca44bca580189f9bfd5371937c22d397a3 Mon Sep 17 00:00:00 2001
From: Sumit Bose
Date: Wed, 11 Nov 2009 15:1
