Cyrille Bonnet wrote:
The main problem is that Zope stores the username and password in a
cookie in clear text (base64 encoded).
Even though it only happens in their internal network, my client
wasn't too happy, because it makes them vulnerable to a
man-in-the-middle attack.
I know, the od
I've been for some time using a "hacked" version of virtual host monster
that was maintained by my hosting company, and I've just moved to a new
hosting service
with just the "stock" version. My impression was that the hack was
mostly cosmetic (just sweetened the interface a little by giving yo
interfaces for Zope 3 are still very rough (at least
this is what the reports say -- I still haven't really
tested it out).
What I have done is to browse the Zope 3 source tree, and I
have made use of the "interface" and "schema" modules. Very
nice stuff! If the rest of Zope
while, so I haven't really
caught up with 'Five' or Zope 3 based products.
--
Terry Hancock ([EMAIL PROTECTED])
Anansi Spaceworks http://www.AnansiSpaceworks.com
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listin
; there anyway to override that?
1) Provide a script that makes this change.
2) Give it the necessary permissions
3) Use the "proxy" feature to allow the script to run with
its own permissions when called (look at the tabs available
on the script editing view)
4) Call this script from t
y is in
squares, but they partially overlap).
I wrote a table layout generator that makes "clock" patterns
with 12 table cels arranged in a circle.
And of course, you can always intersperse "hand crafted"
pages" with data-driven content pages, or combine both on
the sa
