Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 31 Jan 2019 15:42:22 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 235354] ftp/pure-ftpd issue on FreeBSD 12 with TLS enabled
Message-ID:  <bug-235354-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235354

            Bug ID: 235354
           Summary: ftp/pure-ftpd issue on FreeBSD 12 with TLS enabled
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: sunpoet@FreeBSD.org
          Reporter: churchers@gmail.com
          Assignee: sunpoet@FreeBSD.org
             Flags: maintainer-feedback?(sunpoet@FreeBSD.org)

Created attachment 201561
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D201561&action=
=3Dedit
tls.c patch to fix 1.3 support

I've recently had an issue where users are unable to connect via pure-ftpd =
when
TLS is required and the client attempts to use TLS 1.3.

This is mentioned on the pure-ftpd GitHub page in the following issue -
https://github.com/jedisct1/pure-ftpd/issues/94

Unfortunately I can't seem to find an obvious way to just disable 1.3 (it's=
 not
mentioned in the GitHub issue at least, just that it needs patching - which=
 has
to be done manually by the look of it as there hasn't been a new release for
over a year.

Without the patch I'm seeing the following error, which I also get when I t=
ry
myself with Filezilla=20

pure-ftpd[8789]: (?@a.b.c.d) [ERROR] TLS renegociation

I have attached the patch I created for my own ports tree, based on the fix
committed to GitHub (Sorry if line ending are Windows).

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-235354-7788>