Closed Bug 1246922 Opened 9 years ago Closed 8 years ago

blapitest: Make AES-GCM an aeadCipher like ChaCha20/Poly1305

Categories

(NSS :: Libraries, defect)

defect
Not set
normal

Tracking

(firefox47 affected)

RESOLVED WONTFIX
Tracking Status
firefox47 --- affected

People

(Reporter: ttaubert, Unassigned)

References

Details

(Keywords: good-first-bug)

We're currently setting up AES-GCM as a symmetric cipher, instead of as an AEAD cipher. This makes some sense because the AESContext created at the beginning of the test run holds the GCM params, unlike for ChaCha where the API explicitly takes IV, tag, and AAD. We should think about how to clean this up best.
Sorry, this is nonsense. We should just leave it as is.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.