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? To be retested with an expired self-generated certificate. -- You received this bug notification because you are a member of Dcplusplus-team, which is subscribed to DC++. https://bugs.launchpad.net/bugs/1952605 Title: Show a warning when connecting to a hub with expired certificate Status in DC++: Confirmed 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. To manage notifications about this bug go to: https://bugs.launchpad.net/dcplusplus/+bug/1952605/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~linuxdcpp-team Post to : linuxdcpp-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~linuxdcpp-team More help : https://help.launchpad.net/ListHelp
