Trubanc Encryption
I haven't thought much about encryption for the Trubanc client/server link. I figured I'd just set up SSL on the server, and go with that. Today, I realized that I don't need SSL. Trubanc already has a public key infrastructure all set up. It can do it's own encryption, using the OpenSSL library just as the SSL protocol does. Here's an outline of the encryption protocol, using the same language I use in my server design, from the perspective of the client:
sent: (<id>,getsessionkey,<bankid>,<reqid>) rcvd: (<bankid>,sessionkey,<id>,<pubkey encrypted: [<sessionid>,<sessionkey>]>) sent: [<sessionid>,<sessionkey encrypted: message>] rcvd: [<sessionid>,<sessionkey encrypted: response>] or [<sessionid>,unknown] if the <sessionid> isn't registered sent: [<sessionid>, <sessionkey encrypted: (<id>,closesession,<bankid>,<sessionid>)>] rcvd: [<sessionid>, <sessionkey encrypted: (<bankid>,@closesession,(<id>,closesession,<bankid>,<sessionid>))>]
This should be relatively easy to implement, and won't likely slow things down by much. Yay!
Previous Posts:
The Ultimate Conspiracy - The Biomedical Paradigm
Pinchas Zukerman
Trubanc Server Working
The penalty is always death
'Good Morning, Mr. President.'
'Major discovery' from MIT primed to unleash solar revolution
A Handgun Against An Army -- Ten Years After
Honda CH80 Elite Moped
More Cowbell
Trubanc