-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oh well... no news is not always good news. I could also mean that PHP
is much more popular and under more surveillance while python is only
good known to professional crackers...
The problem is, that in this usecase we won't be able to use Zope if
--On 27. Januar 2006 09:38:12 +0100 Sven Deichmann [EMAIL PROTECTED]
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oh well... no news is not always good news. I could also mean that PHP
is much more popular and under more surveillance while python is only
good known to professional
Sven Deichmann schrieb:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oh well... no news is not always good news. I could also mean that PHP
is much more popular and under more surveillance while python is only
good known to professional crackers...
The problem is, that in this usecase we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well, acutally secureness in this case has not really something to do
with protection against attackers. It's more secureness in the sense of
consistency and data security.
The system has to be determined in every way and every step must be
reversible
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well. But when will that be? And when will Plone be ported to Z3? And
when will Plone be certified? ;)
And after all: Is Z3 ready to use? :D
Sven
Andreas Jung schrieb:
--On 27. Januar 2006 09:38:12 +0100 Sven Deichmann
[EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello!
I read on the german zope user group homepage, that Zope 2.8.4 is not
supported on python 2.4.x, because of the missing security audit.
That is good to know, but... who did the security audit for python
2.3.x? Where can I read about that? What
--On 26. Januar 2006 10:13:35 +0100 Sven Deichmann [EMAIL PROTECTED]
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello!
I read on the german zope user group homepage, that Zope 2.8.4 is not
supported on python 2.4.x, because of the missing security audit.
That is good to know,
