Timeline for WinHTTP and python requests package, fail to validate certificate containing valid CN but invalid SAN
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 9, 2018 at 6:00 | vote | accept | Muhammad Uzair Khan | ||
| Feb 27, 2018 at 18:40 | answer | added | Steffen Ullrich | timeline score: 2 | |
| Feb 27, 2018 at 14:51 | comment | added | Steffen Ullrich | I see. your "invalid" is actually not invalid but just not matching. | |
| Feb 27, 2018 at 14:34 | comment | added | Muhammad Uzair Khan | @SteffenUllrich, does this help? | |
| Feb 27, 2018 at 14:24 | history | edited | schroeder♦ | CC BY-SA 3.0 |
deleted 7 characters in body
|
| Feb 27, 2018 at 14:18 | history | edited | Muhammad Uzair Khan | CC BY-SA 3.0 |
added 806 characters in body
|
| Feb 27, 2018 at 13:40 | comment | added | Steffen Ullrich | Please link to the relevant part of the document instead of FCS_CKM.1.1(1) as you currently do. Also, please quote the relevant part which you think claims that it should fail with invalid SAN - I cannot see such a requirement. Maybe you should provide a concrete example so one can see what you consider an invalid SAN in the context of this claim. | |
| Feb 27, 2018 at 13:31 | history | edited | Muhammad Uzair Khan | CC BY-SA 3.0 |
added 211 characters in body; edited tags
|
| Feb 27, 2018 at 13:30 | history | edited | schroeder♦ |
edited tags
|
|
| Feb 27, 2018 at 13:26 | history | asked | Muhammad Uzair Khan | CC BY-SA 3.0 |