[Zope3-dev] buildbot failure in Zope3 trunk 2.4 Linux zc-buildbot
The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 619 Blamelist: ctheune,icemac,jim,mj,schwendinger,tseaver,zagy BUILD FAILED: failed test sincerely, -The Buildbot ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] zope.app.publication uses hard coded global registry
Hi, I'm trying to set up a PAU for a ZODB less application. I stumbled over the fact that zope.app.publication.zopepublication.ZopePublication uses an imported singleton of the global registry. This registry is also registered as a utility, so IMHO this should be done by calling getGlobalSiteManager().getUtility(IAuthentication) instead of using this hard coded thing. :/ Christian -- gocept gmbh & co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] zc.catalog-1.1.1 egg has gone missing
On Apr 24, 2007, at 11:42 PM, David Pratt wrote: Ok I see what has happened, a 1.2dev egg was released to pipy and 1.1.1 is now no longer current release and is now inaccessible. Could someone put 1.1.1 on downloads site. Many thanks. I am glad you found the download cache. I'm sorry I didn't make 1.1.1 also available: I thought it would still be around, even though it was not on the main PyPI page, and I couldn't figure out how to make PyPI show both. :-( I'll ask Jim for help today to make them both available from PyPI: that was my intent. Gary ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] SHA1Password manager, add a pinch of salt
Giovannetti, Mark wrote:
From: Dmitry Vasiliev [mailto:[EMAIL PROTECTED]
Slices doesn't wrap around.
Right, this was what I was seeing/thinking about:
for i in range(41): print i, "'" + "password"[:i-40] + "'"
[skip]
Can't really call it wrap around, I guess.
Anyway:
def checkPassword(self, storedPassword, password):
salt = storedPassword[:max(0, len(storedPassword)-40)]
return storedPassword == self.encodePassword(password, salt)
With Python you can do things as simply as possible. :-) The
expression
storedPassword[:-40] (which is equivalent to
storedPassword[:len(storedPassword)-40]) does exactly what you want:
>>> "password"[:-40]
''
Keeping it simple is often the best way. Given the above, in order
to ensure a blank salt with a password less than 40 characters,
keeping it simple may not suffice.
I think in the example above you're testing for wrong use case since we
use constant slice index, the following example explains what I mean:
>>> hash = "123456789"
>>> while hash:
... print (hash[:-4], hash[-4:])
... hash = hash[1:]
...
('12345', '6789')
('2345', '6789')
('345', '6789')
('45', '6789')
('5', '6789')
('', '6789')
('', '789')
('', '89')
('', '9')
--
Dmitry Vasiliev
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] SHA1Password manager, add a pinch of salt
Giovannetti, Mark wrote: From: Dmitry Vasiliev [mailto:[EMAIL PROTECTED] Giovannetti, Mark wrote: Surely, welcoming obvious improvements that will save some other zope developer from re-implementing a secure /etc/passwd equivalent is desirable. I agreed. I'll apply slightly modified version of the patch with fixed-length salt if you don't object. By all means, I have no objections. Thanks! The changes committed at revision 74700. Python 2.5 has hashlib which supports sha224, sha256 and so forth. I may look into adding support for those hashes to password when zope has been updated for 2.5. I think in this case it will make sense to move the module into self contained package for example zope.app.password or even zope.password. Ok, I might be able to help if you want. It would be cool! By the way you may consider to join Zope Foundation as Committer Member (http://foundation.zope.org/members/classes.html) if you want to contribute. -- Dmitry Vasiliev 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] zc.catalog-1.1.1 egg has gone missing
On Apr 24, 2007, at 11:42 PM, David Pratt wrote: Could someone put 1.1.1 on downloads site. 1.1.1 is available again from PyPI. Sorry for the mix-up. Gary ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] zc.catalog-1.1.1 egg has gone missing
Hi Gary. Many thanks for your effort to bring this back. Regards, David Gary Poster wrote: On Apr 24, 2007, at 11:42 PM, David Pratt wrote: Ok I see what has happened, a 1.2dev egg was released to pipy and 1.1.1 is now no longer current release and is now inaccessible. Could someone put 1.1.1 on downloads site. Many thanks. I am glad you found the download cache. I'm sorry I didn't make 1.1.1 also available: I thought it would still be around, even though it was not on the main PyPI page, and I couldn't figure out how to make PyPI show both. :-( I'll ask Jim for help today to make them both available from PyPI: that was my intent. Gary ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: zope.app.publication uses hard coded global registry
Christian Theune wrote: Hi, I'm trying to set up a PAU for a ZODB less application. I stumbled over the fact that zope.app.publication.zopepublication.ZopePublication uses an imported singleton of the global registry. This registry is also registered as a utility, so IMHO this should be done by calling getGlobalSiteManager().getUtility(IAuthentication) instead of using this hard coded thing. :/ +1 -- http://worldcookery.com -- Professional Zope documentation 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] Re: WebDAV Future
Hi Michael > Subject: Re: [Zope3-dev] Re: WebDAV Future [...] > > zwebdavext.zopelocking, zwebdavext.zopefile - extensions > This I like, but renaming zwebdavext -> zwebdavapp :-) This > allows a clearer seperatation between the protocol components > and the application components, which is what want now that I > think about it. > > For example zwebdavext.zopefile isn't really an extension but > more integration code for zwebdav and any application which > uses zope.file. Then in the future I can hopefully get to > work on zwebdav.dasl, zwebdav.acl etc. which are extensions > to the protocol and hence should belong in zwebdav with more > coresponding integration modules in zwebdavapp. Why this complex naming? I really like to see a namespace package called z3c.webdav and use sub packages like: z3c.webdav.file z3c.webdav.acl If this doesn't fit for distribution, buildout or eggs, or other things I missed, why not: z3c.webdav z3c.webdavfile z3c.webdavacl But anyway that's up to you, I'm sure you will do it right and I like your work anyway ;-) Sorry if I missed something, I didn't read all the full thread. Regards Roger Ineichen [...] > Thanks, > Michael > ___ > 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
[Zope3-dev] Zope egg dependencies and tests
Hi there, now there those wonderful eggs for Zope 3. Apart from the permission problem we ran into lately there is another one with those eggs: The dependencies aren't set right. Apparently nobody every ran the tests of those eggs. This is no wonder. When developing you need to checkout Zope 3 instead of the egg source. The Zope 3 tests would pass of course since everything is in place there. I think we should move the actual code to the eggs as soon as possible and put the externals into the Zope 3 source. Otherwise nobody ever will run the egg tests. Also we need to take care of depending on certain versions. For instance zope.location required a recent version of zope.proxy (>3.3). And it's definitely better to say "I need >3.3 but can't find it" during buildout than "zope.proxy has no module named decorator" somewhere when starting the application. So, how do we get out of this? :) -- Christian Zagrodnick gocept gmbh & co. kg · forsterstrasse 29 · 06112 halle/saale www.gocept.com · fon. +49 345 12298894 · fax. +49 345 12298891 ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Zope egg dependencies and tests
Christian Zagrodnick wrote: now there those wonderful eggs for Zope 3. Apart from the permission problem we ran into lately there is another one with those eggs: The dependencies aren't set right. Apparently nobody every ran the tests of those eggs. This is no wonder. When developing you need to checkout Zope 3 instead of the egg source. The Zope 3 tests would pass of course since everything is in place there. I think we should move the actual code to the eggs as soon as possible and put the externals into the Zope 3 source. Otherwise nobody ever will run the egg tests. Also we need to take care of depending on certain versions. For instance zope.location required a recent version of zope.proxy (>3.3). I personally don't like these "exclusive dependencies" that say what you don't want. I'd rather spell it out as what I want. I think this dependency should ready >=3.4. And it's definitely better to say "I need >3.3 but can't find it" during buildout than "zope.proxy has no module named decorator" somewhere when starting the application. Agreed. So, how do we get out of this? :) +1 on requiring running tests of individual projects Perhaps we could also automate this using a buildbot... -- http://worldcookery.com -- Professional Zope documentation and training ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
