(no subject)

Date: 2016-02-24 03:52 pm (UTC)
simont: A picture of me in 2016 (Default)
From: [personal profile] simont
I wonder if it matters that integrity is more subtle because it can be applied retrospectively?

For example, an SSH connection setup initially has no integrity protection – because how could it, when you haven't yet got a shared secret to base it on? – but after the key exchange completes, signatures are generated which cover a hash that includes the whole of the unprotected connection setup phase. So those messages are not integrity-protected at the time of sending in the same sense that the rest of the protocol session is, but they are integrity-protected eventually, in that later on there will come a point where you are convinced that they hadn't been tampered with.

I feel as if that kind of subtlety might be harder to represent in a simple colour code than confidentiality protection, which is much more like a fixed property of the message as originally sent.

(Though, I suppose, even confidentiality protection could be retrospectively removed, either by sending the decrypted version somewhere or by revealing a key.)
(will be screened)
(will be screened if not validated)
If you don't have an account you can create one now.
HTML doesn't work in the subject.
More info about formatting

If you are unable to use this captcha for any reason, please contact us by email at support@dreamwidth.org

February 2025

S M T W T F S
      1
2345678
9101112131415
16171819202122
232425262728 

Most Popular Tags

Expand Cut Tags

No cut tags