epoptes team mailing list archive

Thread
Date

Bug#981612: epoptes-client: socat[1483] E Failed to set SNI host ""

To: Debian Bug Tracking System <submit@xxxxxxxxxxxxxxx>
From: Vagrant Cascadian <vagrant@xxxxxxxxxx>
Date: Mon, 01 Feb 2021 19:18:53 -0800
Delivered-to: submit@xxxxxxxxxxxxxxx
Reply-to: Vagrant Cascadian <vagrant@xxxxxxxxxx>, 981612@xxxxxxxxxxxxxxx
Resent-cc: vagrant@xxxxxxxxxx, Epoptes Developers <epoptes@xxxxxxxxxxxxxxxxxxx>
Resent-date: Tue, 02 Feb 2021 03:21:01 +0000
Resent-from: Vagrant Cascadian <vagrant@xxxxxxxxxx>
Resent-message-id: <handler.981612.B.161223594429171@xxxxxxxxxxxxxxx>
Resent-to: debian-bugs-dist@xxxxxxxxxxxxxxxx

Package: epoptes-client
Severity: serious
Control: forwarded -1 https://github.com/epoptes/epoptes/issues/127
X-Debbugs-Cc: Vagrant Cascadian <vagrant@xxxxxxxxxx>

Reported upstream, but the short of it is socat 1.7.4.0 (recently
updated in bullseye) defaults to using Server Name Indication (SNI) and
epoptes-client needs to disable it:

  $ /usr/sbin/epoptes-client
  Epoptes-client connecting to server:789...2021/02/01 18:39:47 socat[1483] E Failed to set SNI host ""

Reported upstream and submitted pull request that should fix the issue,
but curious what upstream has to say before rushing to apply the patch
in Debian.


live well,
  vagrant

Attachment: signature.asc
Description: PGP signature