Show a warning when connecting to a hub with expired certificate and no keyprint in the hub address
Bug #1952605 reported by
eMTee
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| DC++ |
Confirmed
|
Low
|
Unassigned | ||
Bug Description
There's no any indication of this. Given that DC++ hasn't done anything so far, nothing more aggressive is reasonable to do than show some warning message. Also if a warning is shown then maybe hub owners also act more likely.
Revision history for this message
| eMTee (realprogger) wrote | #1 |
| summary: |
- Show a warning when connecting to a hub with expired certificate + Show a warning when connecting to a hub with expired certificate and no + keyprint in the hub address |
To post a comment you must log in.
Now as there are human readable TLS errors in DC++, I came across a hub that refuses to connect with TLS error : certificate has expired. No info on what kind of cert the hub has.
I remember the original problem has seen in DCDev public, where the self-generated certificate become expired. There should be differences in handling of different certificates possibly?
Edit: nvm, there was keyprint in the hub address so that behavor is OK. Here we're dealing with hub connections where the keyprint is NOT specified in the hub address.