23:59 Muhammad Moinur Rahman (bofh) 

security/teleport: Update version 4.4.12=>5.2.5

This port was marked to expire on 2023-03-31 but there was another port
security/teleport5 with more recent version from upstream. So move
security/teleport5 to security/teleport.

Pet portlint/portclippy while I am here.

Approved by:	portmgr (blanket)

    301d2b5

10:46 Daniel Engberg (diizzy)  Author: Michael Reim

security/teleport: Update to 4.4.12

Pass maintainership to submitter due to multiple timeouts from current.

Changelog:
https://github.com/gravitational/teleport/releases/tag/v4.4.12

PR:		267052
Approved by:	portmgr (maintainer timeout, 3+ weeks)

    19cac11

00:19 swills 

security/teleport: update to 4.3.9

 

20:55 swills 

security/teleport: update to 4.3.7

 

17:47 swills 

security/teleport: update to 4.3.6

 

16:22 swills 

security/teleport: update to 4.3.5

 

12:39 swills 

security/teleport: update to 4.3.4

 

00:49 swills 

security/teleport: update to 4.3.2

While here, take maintainership since I use this, and also clean up a
bit, remove REINPLACE_CMD

 

15:31 fernape 

security/teleport: update to 4.2.11

From ChangeLog: https://github.com/gravitational/teleport/releases/tag/v4.2.11

 * Fixed an issue that prevented upload of session archives to NFS volumes.
 * Fixed an issue with port forwarding that prevented TCP connections from being
   closed correctly.
 * Fixed an issue in tsh that would cause connections to the Auth Server to fail
   on large clusters. #3872
 * Fixed an issue that prevented the use of Write-Only roles with S3 and GCS.

While here:

 * Reorder some variables
 * Remove GH_TAG_COMMIT

Reported by:	portscout

 

06:02 fernape 

security/teleport: update to 4.2.10

From ChangeLog: https://github.com/gravitational/teleport/releases/tag/v4.2.10

 * Fixed an issue that caused Teleport environment variables not to be
   available in PAM modules. #3725
 * Fixed an issue with tsh login <clusterName> not working correctly
   with Kubernetes clusters. #3693

Reported by:	portscout

 

06:04 fernape 

security/teleport: update to 4.2.9

ChangeLog: https://github.com/gravitational/teleport/releases/tag/v4.2.9

 * Fixed an issue where double tsh login would be required to login to a leaf
   cluster. #3639
 * Fixed an issue that was preventing connection reuse. #3613
 * Fixed an issue that could cause tsh ls to return stale results. #3536

Reported by:	portscout

 

16:25 mikael 

security/teleport: update to 4.2.8

 - update to 4.2.8
 - fix build on aarch64

PR:		245670 245940

 

18:02 seanc 

Update security/teleport to 3.2.2

Approved by:	swills (mentor)
Differential Revision:	https://reviews.freebsd.org/D20042

 

14:34 swills 

security/teleport: update to 3.1.5

PR:		235295
Approved by:	maintainer timeout (seanc, >2 months)

 

07:56 seanc 

Upgrade security/teleport to 2.7.4.

See the release notes for details.

Approved by:	mat (mentor)
Sponsored by:	Joyent, Inc.
Differential Revision:	https://reviews.freebsd.org/D16939

 

07:02 seanc 

Update security/teleport to 2.6.7

Approved by:	mat (mentor)
Differential Revision:    https://reviews.freebsd.org/D16311

 

05:26 seanc 

Upgrade gravitational teleport to 2.6.6.

* See upstream's changelog for details
  https://github.com/gravitational/teleport/blob/master/CHANGELOG.md
* Explicitly specify the git sha when building teleport.
* Restrict builds to amd64.
* Work around daemon(8)'s lack of syslog functionality in 10-STABLE.

Submitted by:	swills
Approved by:	swills (mentor)
Differential Revision:	https://reviews.freebsd.org/D15311

 

20:35 seanc 

Upgrade gravitational teleport to 2.5.7.

Explicitly specify the git sha when building teleport. Restrict builds to amd64.

Reviewed by:	swills, mat
Approved by:	swills (mentor)
Differential Revision:	https://reviews.freebsd.org/D15311

 

17:32 seanc 

Add new port: security/teleport

Gravitational Teleport ("Teleport") is a modern SSH server for remotely
accessing clusters of FreeBSD or Linux servers via SSH or HTTPS. It is
intended to be used instead of sshd. Teleport enables teams to easily
adopt the best SSH practices like:

- Integrated SSH credentials with your organization Google Apps identities or
  other OAuth identitiy providers.
- Teleport uses certificate-based access with automatic expiration time
- Enforcement of 2nd factor authentication
- Cluster introspection: every Teleport node becomes a part of a cluster
  and is visible on the Web UI
- Record and replay SSH sessions for knowledge sharing and auditing purposes
- Collaboratively troubleshoot issues through session sharing

(Only the first 15 lines of the commit message are shown above )