Security and Privacy API provides cryptograhic services to HELIOS components.
HELIOS Security and Privacy API is one of the HELIOS Core APIs as highlighted in the picture below:
More detailed examples for using internal structures of the Security module.
See javadocs in zip file javadocs.zip.
This Android Studio 3.5 project contains the following components:
app - Security and Privacy API test application
doc - Additional documentation files
lib - Security and Privacy API implementation
More detailed examples for using internal structures of the Security module are given below.
SIGN IN ------- User's RSA keys are generated at sign in: KeyPair signingKeyPair = generateRSAKeyPair(); KeyPair encryptinKeyPair = generateRSAKeyPair(); Secret keys are stored to the key store with the string masterPassword that the user chose at sign in: void storePrivateKey(signingKeyPair.getPrivate(), "USER SIGNING KEY", masterPassword); void storePrivateKey(encryptingKeyPair.getPrivate(), "USER DECRYPTING KEY", masterPassword); Later the private keys can be retrieved with the masterPassword: PrivateKey signingKey=retrievePrivateKey("USER SIGNING KEY", masterPassword); PrivateKey decryptingKey=retrievePrivateKey("USER DECRYPTING KEY", masterPassword); Public keys are stored in a byte userData that includes * User info: name, userid, address etc. * Public signature verification key: signingKeyPair.getPublic(); * Public encrypting key: encryptingKeyPair.getPublic(); This userData is signed using the private signing key: byte userDataSignature = signBytes(signingKeyPair.getPrivate(), userData); userData together with userDataSignature is stored at the device and sent to all alters at request. For tutorial about converting RSA keys to byte array and back see: http://www.java2s.com/Tutorial/Java/0490__Security/Thebytescanbeconvertedbacktopublicandprivatekeyobjects.htm Our RSA keys are created with definitions KeyPairGenerator keyGen = KeyPairGenerator.getInstance("RSA"); keyGen.initialize(2048); STORING ALTERS' KEYS -------------------- The userData of the receiver is needed when sending encrypted messages to alters. The userData of the sender is needed when verifying the signature of the sender. When the userData and userDataSignature of an alter (alterData and alterDataSignature) is received, the signature is checked before they are stored on the device: boolean verifyBytes(alterSignatureVerificationKey, alterData, alterDataSignature); Here alterSignatureVerificationKey is the public signature verification key from alterData. SENDING A MESSAGE ----------------- When a byte message is sent to an alter with public encryption verification key alterEncryptingKey, first a new AES key is generated: SecretKey messageKey = generateAESKey(); The message is encrypted using this key: byte encryptedMessage = encryptBytes(message, messageKey, iv); Encryption creates an initial value iv of 12 bytes. The encryptedMessage is signed using the sender's private signing key: byte messageSignature = signBytes(signingKey, encryptedMessage); The messageKey is encrypted using the receiver's public encrypting key: byte encryptedMessageKey = encryptAESKey(alterEncryptingKey, messageKey); The following items are sent to the receiver: encryptedMessage, iv, encryptedMessageKey, messageSignature. Here we assume that message includes the metadata: date, time, sender, receiver, message ID, etc. The messageKey can be put into key storage: void storeSecretKey(messageKey, alias, password); Where string alias is a name that describes the use of the messageKey and string password is some chosen phrase that is needed later when retrieving the messageKey: SecretKey messageKey = retrieveSecretKey(alias, password); The messageKey can be used later when sending a new message to the same receiver. Then the encryptedMessageKey need not be sent to the receiver again if the receiver has also stored the messageKey. RECEIVING A MESSAGE ------------------- When encryptedMessage, iv, encryptedMessageKey and messageSignature are received and the sender's public signature verification key alterSignatureVerificationKey is known, first the validity of the signature is checked: boolean verifyBytes(alterSignatureVerificationKey, encryptedMessage, messageSignature); If true, then the messageKey is decrypted: SecretKey messageKey = decryptAESKey(decryptingKey, encryptedMessageKey); Then the encryptedMessage is decrypted using this key and iv: byte message = decryptBytes(encryptedMessage, messageKey, iv); STORING A MESSAGE ----------------- Instead of sending encryptedMessage, iv, encryptedMessageKey and messageSignature to the receiver they could be placed in a storage where the receiver has access to them. If there are several receivers, the messageKey could be separately encrypted with the public encrypting keys of all of them. Then all different encryptions of the messageKey are placed in the storage. ACCESS CONTROL -------------- *void setAccessRules(String fileId, HeliosAccessControlRulesTable rulesTable)* This method sets the access rules for file/resource called fileId. Rules table lists actions that are allowed for users with some userID or attribute. An example of rule table: HeliosAccessControlRulesTable table = new HeliosAccessControlRulesTable(); table.add("read", ALLOWED, "Bob", USERID); table.add("read", ALLOWED, "Frank", USERID); setAccessRules("myfile", table); This gives read access for users Bob and Frank for file myfile. If the table is null then all rules for the fileId are removed. *HeliosAccessControlRulesTable getAccessRules(String fileId)* This method returns the rules that were set for file/resource fileId using the setAccessRules method. An example: HeliosAccessControlRulesTable table = mgr.getAccessRules("myfile"); table.remove("read", ALLOWED,"Bob", USERID); table.add("write", DENIED,"Frank", USERID); setAccessRules("myfile", table); This removes the rule that Bob is allowed to read the file myfile and adds a rule that Frank is not allowed to write to file myfile. *boolean requestAccess(String fileId, String action, String userId)* This method checks if user with userId has access to perform action on file/resource fileId. The method returns false if there is no rule to allow the action for the user or there is a rule that denies the action for the user. The contextual ego network is queried to find all attributes that the user userId has if they are needed to make the decision. At the moment there is only a toy example of hard coded attributes for and all users have attribute "testattribute". The right to read for all users that have testattribute can be added as follows: table.add("read", ALLOWED, "testattribute", EGONETWORKATTRIBUTE); TODO: Adding interaction with ContextualEgoNetwork to find out at lest in what contexts the userID is a friend of the Ego.