TimurIzhbulatov at oilspace.com
Sun Apr 16 14:24:07 CEST 2006
On Sun, Apr 16, 2006 at 12:46:44PM +0200, Michael Ströder wrote:
> Timur Izhbulatov wrote:
> > On Thu, Apr 13, 2006 at 07:47:05PM +0200, Michael Ströder wrote:
> >>1. As long as returning a server-generated password is not implemented
> >>it does not make sense to make newpw optional and/or accept None as value.
> > Agree. I just blindly followed the RFC.
> If we can't make newpw an optional key-word argument we also can't make
> user and oldpw to optional key-word arguments.
Yes, now I see. At this moment there is no point in making any of the
> >>2. Personally I'd like avoid to turn arguments user,oldpw,newpw of
> >>passwd() into optional key-word arguments (and we can't do that for only
> >>user and oldpw, see 1.). I'd rather prefer the application developer to
> >>really know what he's doing. But I'm open to other opinions.
> > In this case the application developer won't be able to do some important
> > things. For example, changing other users's passwords will be impossible even if
> > tha application is bound with root DN.
> The developer could simply pass value None to passwd() for user and oldpw.
Passing None is OK as long as l_ldap_passwd() allows this. So I suggest applying
my changes only to Modules/LDAPObject.c.
OILspace, 26 Leninskaya sloboda, bld. 2, 2nd floor, 115280 Moscow, Russia
P:+7 495 105 7245 + ext.205 F:+7 495 105 7246 E:TimurIzhbulatov at oilspace.com
Building Successful Supply Chains - One Solution At A Time.
More information about the python-ldap