Chapter 9. Security


SSH connections using libica AES-GCM now work correctly

Previously, unmodified data could be tagged as modified when using decryption with the AES-GCM cipher suite. As a consequence, SSH connections could not be established when using AES-GCM, and with some applications, data encrypted using AES-GCM could not be decrypted. With this update, the tag is computed from the ciphertext when decrypting and from the plaintext when encrypting. As a result, SSH connections using AES-GCM are now successfully established, and it is possible to decrypt data encrypted with AES-GCM. (BZ#1490894)
Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.