Jump to content
Sign in to follow this  
graubart

bytes field clarification

Recommended Posts

I have heard a couple of comments regarding the bytes field in the decryption envelope, that it is not completely clear in the published standard. Here is an unofficial clarification from one implementation team that completed successful interoperability testing:

 

The “bytes” field in the decryption record is the number of bytes before base64 encoding—it’s the length of the initialization vector plus the length of the encrypted text. It’s not an essential field—it conveys no information that the base64 encoding doesn’t, and could be a candidate to deprecate. It’s also impossible to compute if you’re doing on-the-fly encryption and don’t know the length of your encrypted text until you’re done.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×