Decrypt an IBE ciphertext, returning the message
There is no fixed upper bound on the size of the message that can be encrypted using this scheme. However, internally during the encryption process several heap allocations are performed which are approximately the same length as the message itself, so encrypting or decrypting very large messages may result in memory allocation errors.
Serialize the IBE ciphertext to a bytestring
Static
deserializeStatic
encryptEncrypt a message using IBE, returning the ciphertext
Any user who is able to retrieve the VetKey for the specified derived public key and identity will be able to decrypt this message.
There is no fixed upper bound on the size of the message that can be encrypted using this scheme. However, internally during the encryption process several heap allocations are performed which are approximately the same length as the message itself, so encrypting or decrypting very large messages may result in memory allocation errors.
If you anticipate using IBE to encrypt very large messages, consider using IBE just to encrypt a symmetric key, and then using a standard cipher such as AES-GCM to encrypt the data.
The seed parameter must be a randomly generated value that was generated just for this one message. Using it for a second message, or for any other purpose, compromises the security of the IBE scheme.
IBE (Identity Based Encryption)