You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The gcm encryption is a one shot function, it is always only called only once. The tag is often generated at this point by the underling crypto engine (see aes_gcm_nss.c), it would be clear to append the tag to the out immediately instead of caching it. This would match the decrypt function.
The text was updated successfully, but these errors were encountered:
This is a safety check to ensure we do not wrap dst len when removing tag size.
All of this code would get much cleaner if the tag could just be returned instead of cached. see cisco#714
The gcm encryption is a one shot function, it is always only called only once. The tag is often generated at this point by the underling crypto engine (see aes_gcm_nss.c), it would be clear to append the tag to the out immediately instead of caching it. This would match the decrypt function.
The text was updated successfully, but these errors were encountered: