Hello,
The issue https://github.com/openssl/openssl/pull/7129 has introduced a possibility to limit the amount of TLS records processed without key changing as required by FIPS.
We in Russia have limitations with the same semantics applicable to Russian GOST TLS ciphersuites (https://datatracker.ietf.org/doc/draft-smyshlyaev-tls12-gost-suites/) so I think that this mechanism is very useful.
The current implementation is done at EVP level, and it seems suboptimal because of the following reasons:
- If the AES implementation is provided via engine, not by OpenSSL itself, the limitation can be avoided
- the limitation has been made too generic
- the implementation seems to be AEAD-specific.
So does not it make sense to provide this limitation at least at the ciphersuite level? It can provide more straightforward way to manage such limitations.
Thank you!
SY, Dmitry Belyavsky
-- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
