Twisted Spread: How to authenticate each RPC with digital signature
- by kronat
I have remote objects which talk each others with RPCs, using Twisted Spread.
I want that objects authenticate messages, before using them, with digital signatures, but I don't know where to start to implement this.
In my head, the Root object must have a public/private key pair, and the Client too. When a message is sent, a digital signature of the hash is added, and when it is received, the signature is checked. Is the Protocol part where I need to add these adds and checks?
Thank you