RSAES-PKCS1v15 Already broken Recorded traffic 5 places See details
TLS cipher suite named in source
A cipher suite written into the code rather than into a configuration file - `TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256`, the OpenSSL spelling `ECDHE-RSA-AES128-GCM-SHA256`, or a TLS 1.3 suite. Each is reported as a setting of the TLS protocol and listed in its `cipherSuites`; RSA key transport and broken bulk ciphers are reported again, as `config.cipher-suite.weak`.
This code names the exact cryptography its TLS connections may use. Because the list is in the program rather than in a settings file, changing it needs a new release - which is the thing that makes a migration slow.
What to do. A hardcoded suite list ships with the binary and cannot be changed without a release, so move it to configuration first. The key exchange changes when the TLS library offers a hybrid group, not before.
-
src/peergos/server/UserService.java:46
"TLS_RSA_WITH_NULL_SHA256," + -
src/peergos/server/UserService.java:47
"TLS_RSA_WITH_AES_128_GCM_SHA256," + -
src/peergos/server/UserService.java:48
"TLS_RSA_WITH_AES_128_CBC_SHA256, " + -
src/peergos/server/UserService.java:49
"TLS_RSA_WITH_AES_256_GCM_SHA384, " + -
src/peergos/server/UserService.java:50
"TLS_RSA_WITH_AES_256_CBC_SHA256, " +