A message from our CEO about the future of Stack Overflow and Stack Exchange. Read now.

New answers tagged

4

You'd have to move to 9DES rather than 6DES as undoubtedly 6DES would still fall to the meet in the middle attack that can be performed on 2DES, now with the two 3DES block ciphers as parts. That means that (given a large amount of memory), the attack only adds a single bit of security, 113 bits. Even then, just like 3DES has only 112 bits security for 3 ...


1

Whenever TLS is being configured for a new scenario or application, we must identify a balance between security and usability. With that said, I do not believe it's the best approach to only enable strictly only TLS 1.3 yet, since it's still a fairly new protocol, and can cause interoperability issues with older services that you may have to connect the ...


3

You may need a 1.2 and 1.3 scheme, so I'd include at least one of both, giving priority to 1.3 as it is the latest / greatest protocol. Then there is ECDSA and RSA, indicating the certificate based authentication used. ECDSA is more performant for similar security (and you may not even get any certificates above RSA-4096). That may be important if you can ...


3

is it possible with TLS, if the P does not know any of the keys? Sure. SNI is part of the ClientHello message extensions, which is the first TLS message the client sends. At this point you do not yet have key material on the client side to encrypt this in all cases and even for session resumption, SNI is usually included to tell the server which old key ...


Top 50 recent answers are included