[Bug 268604] security/teleport: Update to 5.2.5

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268604

            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=239072&action=edit
Add security/teleport5, set deprecation and expiry date for security/teleport

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 necessary
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 $reasons
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, access
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 service
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 built
using Synth in test mode. So they probably are in good shape. However I'm only
beginning to learn about ports work; any comments or suggestions are very
welcome.

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