https://bugs.exim.org/show_bug.cgi?id=2350
Git Commit changed:
What|Removed |Added
CC||g...@exim.org
--- Comment #8 from Git Commit ---
https://bugs.exim.org/show_bug.cgi?id=2350
Castro B changed:
What|Removed |Added
CC||castro8583benn...@gmx.com
--- Comment #7 from Castro
https://bugs.exim.org/show_bug.cgi?id=2350
--- Comment #6 from Torsten Tributh ---
Hi,
happy new year. After investigating I bit deeper, we can close this issue for
now.
There is no support in the client handshake to staple the OCSP status_response
for TLS< 1.3 and actually no codepoints
https://bugs.exim.org/show_bug.cgi?id=2350
--- Comment #5 from Torsten Tributh ---
Hi,
I am on the way to clarify the OCSP case in the IETF TLS working group. Seems
to take some more time. Please hold this until next year.
--
You are receiving this mail because:
You are on the CC list for the
https://bugs.exim.org/show_bug.cgi?id=2350
--- Comment #4 from Jeremy Harris ---
That would be my reading of the situation, yes.
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim
details at
https://bugs.exim.org/show_bug.cgi?id=2350
--- Comment #3 from Torsten Tributh ---
Haven't recognized this difference between TLS 1.2 and TLS 1.3 before.
Seems like stapling was not intended in the beginning to be offered from
clients also. If it will be offered in TLS 1.3 implementations there
https://bugs.exim.org/show_bug.cgi?id=2350
--- Comment #2 from Jeremy Harris ---
I note that the original RFC for stapling, 6066, only talks about it in terms
of the client requesting and the server supplying certificate status.
https://tools.ietf.org/html/rfc6066 Section 8.
Also the OpenSSL
https://bugs.exim.org/show_bug.cgi?id=2350
Jeremy Harris changed:
What|Removed |Added
Priority|medium |high
Severity|bug
