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
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
Dmitry Vasiliev wrote:
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'
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
Roger Ineichen wrote:
Hi Dimitry , Benji and Stephan
[SKIP]
In this case a generation is appropriate.
Agreed. I didn't know about the other changes. The only
thing I would
propose would be that the generation be automatically run.
I agree too.
I think automatic generation is a good ide
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
--
Benji York
Senior Software Engineer
Zope Corporation
___
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 Physic
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 wh
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
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 whi
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 e
Benji York wrote:
Roger Ineichen wrote:
> Is there a way to evolve during the bootstrap process? Or is the
> manuel process via the ZMI the right way?
If min generation is set properly shouldn't this happen automatically?
Yes, but is it right way to set min generation == max generation?
>
Roger Ineichen wrote:
Hi Dimitry
Roger Ineichen wrote:
Log message for revision 39855:
[SKIP]
+_passwordManagerName = "Plain Text"
+
def __init__(self, login, password, title, description=u'',
passwordManagerName="Plain Text"):
self._login = login
This is unn
13 matches
Mail list logo