On Tue, Apr 2, 2013 at 6:04 PM, Glyph wrote:
>
> On Apr 1, 2013, at 2:34 PM, Shell wrote:
>
> I propose that IUsernamePassword should be split into at least two
> interfaces:
>
> * IUsernamePassword, with only username and password, no methods,
> which allows password to be used in any way
> * A
On Apr 1, 2013, at 2:34 PM, Shell wrote:
>>> I propose that IUsernamePassword should be split into at least two
>>> interfaces:
>>>
>>> * IUsernamePassword, with only username and password, no methods,
>>> which allows password to be used in any way
>>> * Another interface, which only defines u
On 08:51 am, _...@lvh.cc wrote:
>Okay, cool. I definitely agree that IUsernamePassword.checkPassword is
>dumb
>and support deprecating it.
Hey lvh,
Please stop top-posting. :)
Jean-Paul
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
Okay, cool. I definitely agree that IUsernamePassword.checkPassword is dumb
and support deprecating it.
On Monday, April 1, 2013, Shell wrote:
> It actually might be the appropriate thing already. There's a couple
> of possible reasons for renaming; one is that the password might not
> be hashed
It actually might be the appropriate thing already. There's a couple
of possible reasons for renaming; one is that the password might not
be hashed but the credentials object wants to insert additional logic
(exarkun's statement in IRC) anyway, but technically that's just
hashing using the identity
Why does IUsernameHashedPassword have to be renamed? It sounds like it's
the appropriate thing already.
On Mon, Apr 1, 2013 at 10:55 PM, Shell wrote:
> The twisted.cred.IUsernamePassword interface declares:
>
> * IUsernamePassword.username - "The username associated with these
> credentials."
>
