[Zope] - Encryption

[Paul Everitt]

Magnus wrote:
> It still would be nice to have a standard tool that worked 
> with Zope (at
> least IMO.) I guess it would be possible to follow the route 
> of pgp and
> have two versions etc... No?

I personally feel that if we have FTP covered, we can then focus on
WebDAV.  The WebDAV spec requires Digest Authentication.  That answers
much of the problem, unless people really feel that encrypting the
payload is as important as encrypting the authentication.

Digest authentication has no export restriction.  It is a standard with
free implementations.  SSH2, with its non-free license, is a big
problem.  WebDAV represents an extension of the Web object model in a
way that Zope is uniquely positioned to exploit.

Still, there is no one approach that suits everyone, just as there is no
one Python GUI.  Since Zope is free and open source, I'm eagerly
awaiting contributions that reflect people's unique requirements.

> And personally -- I usually sit at the machine where the webserver is
> located, so it would be very nice to be able to edit the 
> document methods
> directly in emacs... (I guess it would be possible to make an 
> emacs-lisp
> program that interacted with Zope, but it seems a bit unneccesary...)

Personally I think this is the *right* way to do it.  I believe
*strongly* in objects and I feel that editing the data directly is a
violation of encapsulation.  *But*, Zope is a free, open system and
others can do what they want, including discarding the object database
(as both Andreas and Skip have done).

--Paul

Paul Everitt       Digital Creations
paul@digicool.com  540.371.6909