AESGCM256 mode uses incorrect algorithm identifier (A128GCM)

[David Illsley]

Incorrect algorithm identifier.

[Brian Campbell]

Good catch, thanks @davidillsley

[Brian Campbell]

fixed with df3e6c1 that just changes the A128GCM literal to A256GCM

though note that the GCM content encryption algorithms aren't currently supported and even with this Aes256GcmContentEncryptionAlgorithm doesn't actually work

[Brian Campbell]

FWIW, I just checked in 2fea31d which adds initial support for the GCM content encryption algorithms. More work to be done there but GCM should be supported in the next release (hopefully in the next few weeks) as long as the underlying JCE provider supports it (which Bouncy Castle does as of v1.50).

[Brian Campbell]

The security provider in Java 8 also supports AES GCM.