View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005133 | unreal | ircd | public | 2018-08-14 16:42 | 2018-09-05 10:22 |
| Reporter | capitaine | Assigned To | syzop | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 4.0.18 | ||||
| Summary | 0005133: Client certificate fingerprint missing | ||||
| Description | When a client connects with TLS only and provides a certificate, the server doesn't produce any fingerprint. As a consequence, SASL external fails. However, when connecting with STARTTLS, everything works as expected. | ||||
| Steps To Reproduce | Connect to the server with TLS and a client certificate. Server doesn't send "Your SSL fingerprint is ..." | ||||
| 3rd party modules | |||||
|
|
Just checked, I cannot reproduce this. 1) Can you double check that you indeed use a client certificate when connecting directly (non-STARTTLS)? It would be easy to miss something like that, and without client certificate it would connect fine but not print the Your SSL fingerprint is xxxx line. 2) Perhaps it only happens in very specific circumstances? |
|
|
It seems you're right, I'm sorry. Well, it would not make sense to send that certificate in a case but not in the other. But I'm using java and I don't know where the issue is from... I can't say there's a bug now, sorry again. |
|
|
Ok, thanks for getting back, and no problem at all! :) |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2018-08-14 16:42 | capitaine | New Issue | |
| 2018-09-03 09:04 | syzop | Assigned To | => syzop |
| 2018-09-03 09:04 | syzop | Status | new => feedback |
| 2018-09-03 09:04 | syzop | Note Added: 0020259 | |
| 2018-09-05 09:58 | capitaine | Note Added: 0020260 | |
| 2018-09-05 10:22 | syzop | Status | feedback => closed |
| 2018-09-05 10:22 | syzop | Resolution | open => no change required |
| 2018-09-05 10:22 | syzop | Note Added: 0020266 |
