On Thu, 2009-10-15 at 18:05 +0200, Sumit Bose wrote:
> >
> > ok, I've created a new patch (0002) with the changes, 0001 is
> rebased
> > but unchanged. I've also added a 'deny' option for access_provider
> and a
> > man page entry.
> >
> > bye,
> > Sumit
>
> Please find attached rebased versions
On Thu, Oct 15, 2009 at 12:12:57PM +0200, Sumit Bose wrote:
> On Wed, Oct 14, 2009 at 01:33:18PM -0400, Stephen Gallagher wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > On 10/14/2009 07:24 AM, Sumit Bose wrote:
> > > Hi,
> > >
> > > if auth_provider is set to a provider whic
On Wed, Oct 14, 2009 at 01:33:18PM -0400, Stephen Gallagher wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 10/14/2009 07:24 AM, Sumit Bose wrote:
> > Hi,
> >
> > if auth_provider is set to a provider which can handle change password
> > request, e.g. LDAP, but chpass_provider is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/14/2009 07:24 AM, Sumit Bose wrote:
> Hi,
>
> if auth_provider is set to a provider which can handle change password
> request, e.g. LDAP, but chpass_provider is not set at all the user might
> be surprised that the password connet be changed. T
Hi,
if auth_provider is set to a provider which can handle change password
request, e.g. LDAP, but chpass_provider is not set at all the user might
be surprised that the password connet be changed. This patch sets
chpass_provider implicit if an auth_provider is available and can handle
change pass