Skip to content

Releases: gliderlabs/ssh

v0.3.8

13 Dec 20:25
Compare
Choose a tag to compare

This bumps x/crypto to 0.31.0 to resolve CVE-2024-45337. The API has not changed, which means there are still a number of ways you could be vulnerable if your code improperly uses the PublicKeyHandler.

Note that this may result in a performance regression, as the PublicKeyHandler may be called multiple times for the same key. The last time it is called will be the key the user is actually using.

Note that if you are using Permissions to pass information about the public key out of the handler, you need to make sure you always overwrite all relevant stored map keys in order to avoid being vulnerable.

Full Changelog: v0.3.7...v0.3.8

v0.3.7

18 Mar 22:19
adec695
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.3.6...v0.3.7

v0.2.2: Merge pull request #110 from gliderlabs/belak/raw-cmd

20 Jun 03:23
5b6cc70
Compare
Choose a tag to compare

v0.2.1

19 Jun 18:02
Compare
Choose a tag to compare
  • Fix ForwardedTCPHandler by switching to a pointer receiver
  • Rename DefaultServerConfigCallback to ServerConfigCallback

v0.2.0

19 Jun 08:39
Compare
Choose a tag to compare
  • Make ChannelHandlers configurable
  • Make RequestHandlers configurable
  • Disable port forwarding by default

v0.1.4: Fix panic with missing request handler

19 Jun 08:39
Compare
Choose a tag to compare
  • Fix panic with missing request handler

v0.1.3

21 Feb 22:46
Compare
Choose a tag to compare

Small release which adds a method of changing the internal SSH config

v0.1.2

20 Feb 18:44
bed87f3
Compare
Choose a tag to compare

This is a cut of master that includes reverse port forwarding.

v0.1.1

01 Jun 19:01
Compare
Choose a tag to compare

There were too many changes to list them in a short changelog, but the main reason for this release is so users working with dep or vgo can use a version which works with the latest x/crypto/ssh version.

v0.1.0

14 Feb 23:00
Compare
Choose a tag to compare

First cut of the library before we start potentially introducing breaking API changes. Releases will use semantic versioning, but right now we're pre-1.0. During this phase breaking API changes will represented in the minor version and is the only reason a release will happen.