| | 2 | |
| | 3 | The test made it clear that JJK's patch will not set `common_name` at all after the client renegotiates and then times out. If the client disconnects using `--explicit-exit-notify` then jjk's patch works, as expected. |
| | 4 | |
| | 5 | The reason to record these findings it because I have thoroughly tested the results and these are the steps required to reproduce the issues. |
| | 6 | |
| | 7 | Summary: |
| | 8 | |
| | 9 | 1. Without JJK's patch, all that is required to trigger the original problem is for the client to renegotiate and then disconnect. The disconnect can be a time out or explicit, the problem always occurs, regardless. |
| | 10 | |
| | 11 | 2. With JJK's patch, the client must renegotiate and then time out to trigger the second problem. |
