Re: [Zope3-dev] New database generation for Zope 3.2 (Was: [Zope3-checkins] Added BBB for older instances)

2005-11-07 Thread Stephan Richter
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  Chemistry (B.S.) / Tufts Physics (Ph.D. student)
Web2k - Web Software Design, Development and Training
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



Re: [Zope3-dev] New database generation for Zope 3.2 (Was: [Zope3-checkins] Added BBB for older instances)

2005-11-07 Thread Dmitry Vasiliev

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 and get rid of the generation.

--
Dmitry Vasiliev (dima at hlabs.spb.ru)
http://hlabs.spb.ru
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



Re: [Zope3-dev] New database generation for Zope 3.2 (Was: [Zope3-checkins] Added BBB for older instances)

2005-11-07 Thread Benji York

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 list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



Re: [Zope3-dev] New database generation for Zope 3.2 (Was: [Zope3-checkins] Added BBB for older instances)

2005-11-07 Thread Dmitry Vasiliev

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 storing so the password needs to go through 
aPasswordManager.encodePassword method. I think the only way to get rid of the 
generation is to use InternalPrincipal.setPassword method inside the views and 
store the encoded password as InternalPrincipal.password attribute (like before).


--
Dmitry Vasiliev (dima at hlabs.spb.ru)
http://hlabs.spb.ru
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



Re: [Zope3-dev] New database generation for Zope 3.2 (Was: [Zope3-checkins] Added BBB for older instances)

2005-11-05 Thread Stephan Richter
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 fix without a generation. I see two alternative
 possibilities:

In this case a generation is appropriate.

Regards,
Stephan
-- 
Stephan Richter
CBU Physics  Chemistry (B.S.) / Tufts Physics (Ph.D. student)
Web2k - Web Software Design, Development and Training
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



Re: [Zope3-dev] New database generation for Zope 3.2 (Was: [Zope3-checkins] Added BBB for older instances)

2005-11-05 Thread Benji York

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 which is
not so easy to fix without a generation. I see two alternative
possibilities:


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.

--
Benji York
Senior Software Engineer
Zope Corporation
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



RE: [Zope3-dev] New database generation for Zope 3.2 (Was:[Zope3-checkins] Added BBB for older instances)

2005-11-05 Thread Roger Ineichen
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 self.password attribute changed to a 
 property which is
 not so easy to fix without a generation. I see two alternative
 possibilities:
  
  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 idea in this case.

I think a MIGRATION.txt file in the trunk/doc folder would be a good 
idea for such migration notes.

btw, we have to take care on such changes, what's happen if somebody
uses allready a password property in a custom class where is inherited
form InternalPrincipal?

Regards
Roger Ineichen

 Benji York
 Senior Software Engineer
 Zope Corporation
 ___
 Zope3-dev mailing list
 Zope3-dev@zope.org
 Unsub: 
 http://mail.zope.org/mailman/options/zope3-dev/dev%40projekt01.ch
 
 

___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com