Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 28 Dec 2022 00:01:51 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 268604] security/teleport: Update to 5.2.5
Message-ID:  <bug-268604-7788@https.bugs.freebsd.org/bugzilla/>

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

            Bug ID: 268604
           Summary: security/teleport: Update to 5.2.5
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: kraileth@elderlinux.org
                CC: diizzy@FreeBSD.org
 Attachment #239072 maintainer-approval+
             Flags:

Created attachment 239072
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D239072&action=
=3Dedit
Add security/teleport5, set deprecation and expiry date for security/telepo=
rt

This patch updates the security/teleport port from 4.4.12 to 5.2.5 (last
version compatible for upgrades) as security/teleport5. This is necessary
because in 2022q4 the original port is still at version 4.3.9, which cannot=
 be
updated to 5.x. Therefore this update is a second intermediary step necessa=
ry
to eventually upgrade to version 6.x which I intend to work on next. I had
hoped to proceed more quickly after claiming maintainership, but for $reaso=
ns
it took some more time. Maybe this work can still go in before 2023q1 is
branched.

What was tested: I set up a 4.4 cluster and tested invitations & joins, acc=
ess
to nodes via both the WebUI and CLI (tsh), 2FA (via OTP) as well as access =
to
sshd-only nodes. Then I updated both the server and the regular test node to
5.2 and made sure that everything still worked. In addition I successfully
tested the major new feature of 5.x: Web application access (caveat: I could
not get it to work regularly via configuration file and using the rc.d serv=
ice
for some reason; it works when done manually though which is good enough to
prove that it's working in general).

What was not tested: 2FA via U2F, direct OpenSSH access to teleport nodes (=
this
should work, though), database access (feature preview in this version,
production ready in 6.x).

Both the new port and the modified one passed "portlint -AC" and could be b=
uilt
using Synth in test mode. So they probably are in good shape. However I'm o=
nly
beginning to learn about ports work; any comments or suggestions are very
welcome.

--=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-268604-7788>