pgpfan:seip
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
pgpfan:seip [2024/10/10 15:27] – [Protection] Sounded editorial and was confusing. Create narrative arc. b.walzer | pgpfan:seip [2024/10/10 15:37] (current) – [SEIP for TLS] Consistency. b.walzer | ||
---|---|---|---|
Line 173: | Line 173: | ||
Up to this point we assumed a cipher with 128 bit blocks. The OpenPGP standard supports ciphers with 64 bit blocks. Use of a 64 bit cipher in a SEIP formatted message would result in the secret IV only being 64 bits long. So the strength of the modification detection would be reduced. It's not clear to me that SEIP with 64 bit blocks is something that anyone ever implemented and that such messages/ | Up to this point we assumed a cipher with 128 bit blocks. The OpenPGP standard supports ciphers with 64 bit blocks. Use of a 64 bit cipher in a SEIP formatted message would result in the secret IV only being 64 bits long. So the strength of the modification detection would be reduced. It's not clear to me that SEIP with 64 bit blocks is something that anyone ever implemented and that such messages/ | ||
+ | |||
+ | A bit of insight from this discussion... The damage amplification of CFB is helpful here but would not have been as helpful if " | ||
[[pgpfan: | [[pgpfan: |
pgpfan/seip.1728574024.txt.gz · Last modified: 2024/10/10 15:27 by b.walzer