One main advantage to letting SSLLogger implement System.Logger is a more accurate stack caller trace value per log statement. The "SSLLogger.log" method itself is discarded.

e.g.

current behavior:
Nov 17, 2025 3:37:40 PM sun.security.ssl.SSLLogger log
FINE: Plaintext before ENCRYPTION

after fix:
Nov 17, 2025 3:40:01 PM sun.security.ssl.SSLCipher$T13GcmWriteCipherGenerator$GcmWriteCipher encrypt
FINE: Plaintext before ENCRYPTION:

Such a change would be trivial enough to make (Thanks to [~dfuchs] for the help)

We could also take this opportunity to encapsulate the 'isOn' boolean in SSLLogger. Calling code should access this variable via a new method which can be forced to be inlined.