Like all good softwares Wasabi is going to be secure ! :-D

Well... somehow.

This should be broken down in two parts :

• ACL The user can manage access to his objects, to his core pipes, and to his filesystem to other users, from the network, or locally.

• Crypto The user has to be able to encrypt and decrypt data flowing through the network, but also files, dirs, and filesystem on his own hd. I think it will do a perfect DSP for wasabi :)

                        |< Key
                        |< Cypher
  FileManager] ---- [crypto DSP] ----  [FileManager
  
  

  svc_crypto.wac? or do we have a svc_crypto, and have many wac's? ie. svc_crypto_aes.wac, svc_crypto_blowfish.wac?
  WaI> define svc_crypto, and then wac's with services, but they can all be in one. Eg, cryptolib.wac could have crypto_aes, crypto_blowfish, etc in it, and crypto_mycoolcipher could have others. no need to have 10 files when one will do. The idea is right though.
  JmB> The simple fact that the user can add easily his own cyphers is sufficient. the Crypto DSP can provide the basic cyphers. What I drawed on the schematics (upper input) were in fact parameters (such as Cypher= "my_cool_cypher", key="122ab323cf323")