Rapid Application Development for the masses.
censored distributed easy extendable fast informative intelligent lean maintainable open (source) portable pretty rfc'ed robust secure transparent version numbers virtual
Security is not always an issue, and it is always a trade off with convenience.
If security is easy to use, it is probably easy to abuse. For the things that
need security, we should encrypt at the packet level from end to end. SSL is
good for that. For everyting else, just send in the clear. Segregated servers
and clients will need security to get through their borders, everybody else only
uses it when they need. Security should really be built
into the meta-protocol, and we can then wrap security around unsecure protocols.
If we can modify SSL to use PGP keys, and build PGP into the rest of the system,
then we can bypass the need to know anything about anybody, and even the need to
let others know anything about us. In other words, no one has to deal with a CA,
it's all about who you trust, and who you trust to trust the right people, not
who the authorities trust. Many open source authors are already using PGP to sign
their work, so we can leverage that.
We will probably have to implement some sort of sandbox, like the one used for
browsers when running Java.
[The following concerns matrix-DFS, a sub project of matrix-RAD.]
The total file space can be separated into separate areas, and the different areas can have different security arrangements, that takes care of compartmentalization.
This file was last modified on Tuesday, 26-Oct-2004 18:25:58 EST