On 4/20/07, Giovannetti, Mark <[EMAIL PROTECTED]> wrote:
+def checkPassword(self, storedPassword, password):
+if len(storedPassword) == 48:
+salt = storedPassword[0:8]
+else:
+salt = ''
+return storedPassword == self.encodePassword(password, sal
On Apr 13, 2007, at 10:44 AM, Baiju M wrote:
Hi,
I would like to introduce Nikhil N a student from Kerala
(India) who will be
porting Zope 3 to work on Python 2.5. I am looking for your help
and feedback
to complete this project. He had already joined in this list, and
I will ask him
Hi,
I'm doing a bit of bug mangling for Zope 3.4 everybody who wants to just
go ahead and fix a bug for Zope 3.4 can go to
https://bugs.launchpad.net/zope3/3.4/ and see what bugs need to be
handled.
Christian
--
gocept gmbh & co. kg - forsterstraße 29 - 06112 halle/saale - germany
www.gocept.co
Adam Groszer wrote:
Using the current trunk I experienced that using the PAU with a user
folder and users passwords stored with MD5, entering accented
characters as passwords causes an exception. That happens either at
adding the principal or at Z3's stock login form.
I think this is not my faul
Hi,
I think we lost tests at some point.
When moving code around some doc tests have not been added to the test
suites again. I noticed because we received some bug reports about
zope.app.component.vocabulary. This module contains doctests but those
are never run (and obviously they are broken).
Hello Dmitry,
Saturday, April 21, 2007, 10:57:07 AM, you wrote:
> Ugh, my bad I didn't notice that passwords may be Unicode strings. I
> think password should be encoded to UTF-8 before processing but I don't
> know that to do with backward compatibility. As an option we can
> introduce new Unic
Giovannetti, Mark wrote:
I've been researching authentication and whatnot in Zope 3
and was looking at the password management implementations.
I don't like the fact that the SHA1 password manager
doesn't use a random salt value when encoding and storing
a password. Salts are commonly used in /e
The Buildbot has detected a failed build of Zope3 branches 3.3 2.4 Linux remy.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 187
Blamelist:
alecm,alga,andreasjung,baijum,ctheune,darrylcousins,dobe,faassen,gary,jacobholm,jim,jukart,jvloothuis,ksmith_mcweekly,mj
Adam Groszer wrote:
Ugh, my bad I didn't notice that passwords may be Unicode strings. I
think password should be encoded to UTF-8 before processing but I don't
know that to do with backward compatibility. As an option we can
introduce new Unicode-aware password managers. Opinions?
Thinking it
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: 189
Blamelist: ctheune
BUILD FAILED: failed test
sincerely,
-The Buildbot
___
Zope3-dev
Hi,
Am Freitag, den 20.04.2007, 16:25 +0200 schrieb Martijn Faassen:
> Hey,
>
> > Compatibility with Zope 2
> > --
> >
> > We continue to work on the transition from Zope 2 to Zope 3 by making
> > Zope 2 use more and more of the Zope 3 packages. But we're not there
> > ye
That was a spurious ZEO error.
Am Samstag, den 21.04.2007, 06:08 -0400 schrieb [EMAIL PROTECTED]:
> The Buildbot has detected a failed build of Zope3 branches 3.3 2.4 Linux remy.
>
> Buildbot URL: http://buildbot.zope.org/
>
> Build Reason: changes
> Build Source Stamp: 187
> Blamelist:
> alecm
Hmm. Up until now those failures where spurious on my machine. I'm
somewhat happy those turned up.
Jim mentioned to me those would be problems with exit handlers in the
test runner, however one testrunner that was breaking on my machine
didn't get fixed by switching to `os._exit()` :/
Am Samstag,
On the basis that eggs spell out dependencies, I am thinking the
inclusion of packages and their dependencies should be enough to dictate
the sequence of inclusion for package configuration (and creation of the
site.zcml) for the app buidout recipe. This could be a option to the
current manual
Hi,
(moving it to zope3-dev for discussion)
Am Samstag, den 21.04.2007, 13:50 + schrieb Jim Fulton:
> On Apr 21, 2007, at 9:24 AM, Christian Theune wrote:
>
> > *sigh*
> >
> > This is a can of worms. It looks like email.FeedParser.FeedParser is
> > probably what we want to use.
>
> Why?
Ah
On Apr 21, 2007, at 11:47 AM, Christian Theune wrote:
Hi,
(moving it to zope3-dev for discussion)
Am Samstag, den 21.04.2007, 13:50 + schrieb Jim Fulton:
On Apr 21, 2007, at 9:24 AM, Christian Theune wrote:
*sigh*
This is a can of worms. It looks like email.FeedParser.FeedParser is
pr
Hey,
Anyone, can I conclude that z3c.widget is not available anywhere? Who
would like to upload a version? Can I help? Where shall we upload it?
Regards,
Martijn
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/opti
Hi All,
I want to move the webdav implementation on by releasing it to cheeseshop,
supporting more content types and then working on some more interesting
aspects of the protocol itself, and maybe even supporting other applications
like Plone if there is interest.
First I need to rename it
Am Samstag, den 21.04.2007, 19:12 +0200 schrieb Martijn Faassen:
> Hey,
>
> Anyone, can I conclude that z3c.widget is not available anywhere? Who
> would like to upload a version? Can I help? Where shall we upload it?
You should be able to make an sdist and scp it to
download.zope.org:/distribut
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Pratt wrote:
> On the basis that eggs spell out dependencies, I am thinking the
> inclusion of packages and their dependencies should be enough to dictate
> the sequence of inclusion for package configuration (and creation of the
> site.zcml)
Christian Theune wrote:
Am Samstag, den 21.04.2007, 19:12 +0200 schrieb Martijn Faassen:
Hey,
Anyone, can I conclude that z3c.widget is not available anywhere? Who
would like to upload a version? Can I help? Where shall we upload it?
You should be able to make an sdist and scp it to
download
Hello,
Tres Seaver wrote:
David Pratt wrote:
On the basis that eggs spell out dependencies, I am thinking the
inclusion of packages and their dependencies should be enough to dictate
the sequence of inclusion for package configuration (and creation of the
site.zcml) for the app buidout recipe
Hi there,
I have some questions about the Zope 3.4 release. My apologies if this
information is already available somewhere else.
I've just uploaded z3c.widget to download.zope.org/distribution, but ran
into a new snag: it properly lists a whole bunch of dependencies in its
setup.py that are
On 4/21/07, Martijn Faassen <[EMAIL PROTECTED]> wrote:
It is therefore important that binary Windows
eggs are indeed available for the appropriate Zope 3 and ZODB packages.
Is there a plan for providing these? I'm hoping Sidnei will pop up and
say, oh, yeah, all taken care of. :)
Jim has been b
24 matches
Mail list logo