> recognizable patterns can't be good for security. I guess the only way to
> do it then would be to compress that data prior to encryption. This would
This is a client-side issue. You could write a client which automatically
zipped some content (not all, some content shouldn't be zipped, such as
zip files) before inserting it. This could certainly done in a backwards
compatible way since current clients can be used to download zip files
just fine. So it doesn't really require a change to the protocol. You
might say that we should *require* all clients to zip content, but you
can't realistically require anything of clients.
_______________________________________________
Devl mailing list
[EMAIL PROTECTED]
http://lists.freenetproject.org/mailman/listinfo/devl