Project

General

Profile

Feature #5035

open

Auto accept SSL certificates

Added by Gecko 666 7 months ago. Updated 7 months ago.

Status:
Assigned
Priority:
Normal
Assignee:
Category:
Interface
Target version:
Start date:
04/08/2020
Due date:
% Done:

0%

Estimated time:
Operative System:
All

Description

In a channel with numerous bots that come and go, and sometimes change IP address, the current flow where it is necessary to accept the certificate for incoming SSL DCC transfers is tedious, and requires being present when a first time transfer starts, but transfers may be queued or triggered by some outside factor, and sent from an unpredictable nickname, although perhaps with a known certificate SHA fingerprint. A couple ideas to resolve this:

1) include an option to simply accept all offered certificates
2) a list of cert fingerprints to always accept (nx=*,XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX)
3) a list of nicks (supporting wildcards) to always accept (nx="SomeBot*",*)
4) a list of nicks (supporting wildcards), each with an associated fingerprint (nx="SomeBot*",XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX)

I realize that auto accepting certs means you are not verifying the source, but in these cases the use of SSL is only intended to encrypt the traffic, the identification of the sender is not necessarily important.

#1

Updated by Per Amundsen 7 months ago

  • Category set to Interface
  • Status changed from New to Assigned
  • Assignee set to Per Amundsen

I agree, auto accept transfers should probably auto accept certificates as well, I'll figure something out for next beta.

Also available in: Atom PDF