On Monday 07 November 2005 07:16, Dmitry Vasiliev wrote:
BTW, another one idea: We can set a password manager for a principal
folder, not for a individual principal, so all principals in the folder
will be use the only one password manager.
+1
Regards,
Stephan
--
Stephan Richter
CBU Physics
Benji York wrote:
Dmitry Vasiliev wrote:
BTW, another one idea: We can set a password manager for a principal
folder, not for a individual principal, so all principals in the
folder will be use the only one password manager.
I like that even better. +1
Ok, so I'll redo the implementation
Dmitry Vasiliev wrote:
Dmitry Vasiliev wrote:
Oops, we can't get rid of the generation since we need to encode the
password anyway... :-/
Even if we default to plain text?
--
Benji York
Senior Software Engineer
Zope Corporation
___
Zope3-dev mailing
Benji York wrote:
Dmitry Vasiliev wrote:
Dmitry Vasiliev wrote:
Oops, we can't get rid of the generation since we need to encode the
password anyway... :-/
Even if we default to plain text?
Yes. For example if you change the password of a principal it needs to be
properly encoded before
On Saturday 05 November 2005 08:17, Dmitry Vasiliev wrote:
I think a generation is too heavy a fix where a simple class attribute
will suffice. I like Roger's fix and propose we remove the generation.
No, there is also self.password attribute changed to a property which is
not so easy to
Stephan Richter wrote:
On Saturday 05 November 2005 08:17, Dmitry Vasiliev wrote:
I think a generation is too heavy a fix where a simple class attribute
will suffice. I like Roger's fix and propose we remove the generation.
No, there is also self.password attribute changed to a property
Hi Dimitry , Benji and Stephan
[...]
Stephan Richter wrote:
On Saturday 05 November 2005 08:17, Dmitry Vasiliev wrote:
I think a generation is too heavy a fix where a simple
class attribute
will suffice. I like Roger's fix and propose we remove
the generation.
No, there is also
