Skip to content

v0.8.0

Latest
Compare
Choose a tag to compare
@Foxboron Foxboron released this 26 Mar 21:47
· 4 commits to master since this release
v0.8.0
1a96091

The release is signed with C100 3466 7663 4E80 C940 FB9E 9C02 FF41 9FEC BE16.

⚠️ Breaking Changes ⚠️

ssh-tpm-agent won't use SSH_AUTH_SOCK as the default socket environment
variable anymore. As ssh-tpm-agent support proxy features and intended to be
run along side an existing ssh-agent this does not make much sense anymore.

Instead SSH_TPM_AUTH_SOCK is the new standard environment variable.

agent: Don't overwrite SSH_AUTH_SOCK socket

Changes

Support for rsa-sha2-512

Previously ssh-tpm-agent did not support sha512. This is annoying as in many
cases ssh is going to try and opt for sha512 when dealing with RSA keys. As
most TPMs do not support SHA512, a hack was implemented using the raw
TPM2_Decrypt call to implement support for other hash algorithms.

See upstream go-tpm-keyfiles project commit:
tpm: support RSA signing with SHA512

As a bonus:
ssh-keygen -Y sign did not support setting the hashalg with -O. I sent a
patch to fix that, so you can use RSA keys with SHA256 for signatures if
needed.
upstream: when using RSA keys to sign messages, select the signature algorithm based on the requested hash algorithm ("-Ohashalg=xxx").

New Features

MANPAGES!

We now have manpages!

  • ssh-tpm-agent(1)
  • ssh-tpm-keygen(1)
  • ssh-tpm-add(1)
  • ssh-tpm-hostkeys(1)

Typos may follow.

Implement man pages

Hierarchy keys

Important

This feature is experimental. Change in the future could cause the keys to change
between versions.

ssh-tpm-agent is now capable of preloading hierarchy keys into the agent.
These keys are not the usual keys and persist across installs and system
reboots.

The TPMs have several hierarchies you can create keys under. The owner
hierarchy should be unique for each owner of a given device. The endorsement
hierarchy should be unique for the lifetime of the device, and null should be
unique for the current device power cycle.

ssh-tpm-agent --hierarchy endorsement will now start the agent with two keys,
one ecdsa key and one rsa keys which is bound to the endorsement hierarchy
of the device.This is useful for host keys as they can persist between
installations of the operating system and ephemeral root disks.

To create the public portions of the host keys you can used
ssh-tpm-keygen -A --hierarchy endorsement

Implement hierarchy keys #87

keyctl support for PIN caching

In previous releases passwords/pins for keys where stored along side the key in
the memory. Now these values are passed to the kernel keyring for storage and
only stored in memory while it is used. After use there is an attemt at using
mmap to clear the memory.

This ensures that only the ssh-tpm-agent process can access these secrets.

Note the huge caveat that this is Go, and any handling of the secrets before
we pass them to keyctl might be leakable in a crash drump etc. I have a goal
of trying to improve this in the future.

Implement kernel keyctl support

Initial support for landlock

ssh-tpm-agent now has some baseline support for landlock
sandboxing of the processes. This is disabled by default but can be enabled by
setting the SSH_TPM_LANDLOCK environment variable.

If you run a distro with different requirements, please help test this feature
as I would like to turn it on by default in the future.

Note that ssh-tpm-keygen does not support landlock yet.

Initial support for landlock

Support signing with SSH certificates

ssh-tpm-agent supports signing with SSH certificates now.

Implement signing using SSH certificates

Better support for ssh-add in ssh-tpm-agent

ssh-add will now attempt to also include the certificate if found alongside
the ssh key.

agent: ensure we load certificates if found

#Generated list of changes

What's Changed

New Contributors

Full Changelog: v0.7.0...v0.8.0