BSD Portssecurity/opkssh 0.17.0_1 DragonFly
Tool which enables SSH to be used with OpenID Connect
- System
- DragonFly
- Repository
- DPorts
- Maintainer
- [email protected] (as in FreeBSD)
- License
- APACHE20
- Categories
- security
- Package size
- 4240.9 KiB, 14266.8 KiB installed
Description
opkssh is a tool which enables ssh to be used with OpenID Connect allowing SSH access to be managed via identities like [email protected] instead of long-lived SSH keys. It does not replace SSH, but instead generates SSH public keys containing PK Tokens and configures sshd to verify them. These PK Tokens contain standard OpenID Connect ID Tokens. This protocol builds on the OpenPubkey which adds user public keys to OpenID Connect without breaking compatibility with existing OpenID Provider.
In the other systems
The newest version among them is 0.17.0, as upstream numbers it.
| System | Port | Version | Vulnerabilities | Status | Maintainer | Last update |
|---|---|---|---|---|---|---|
| DragonFly | security/opkssh | 0.17.0_1 newest | none known | - | [email protected] | - |
| FreeBSD | security/opkssh | 0.17.0_2 newest | none known | - | [email protected] | 2026-11-11 |
| HardenedBSD | security/opkssh | 0.17.0_1 newest | no data | - | [email protected] | - |
| GhostBSD | security/opkssh | 0.17.0_1 newest | no data | - | [email protected] | - |
Version history 1
- 0.17.0
Upstream's version as each commit to the port's Makefile set it, or as this site first saw it in the system's packages; the tree's own revisions are not versions here.
Install
Binary package:
pkg install opksshFrom DPorts:
cd /usr/dports/security/opkssh && make install cleanDependencies
No port depends on this one.
Configuration
No options to configure.
- Service scripts
- none
Message after installing
Configure your sshd_config(5) with the following to use opkssh for authorization: AuthorizedKeysCommand /usr/local/bin/opkssh verify %u %k %t AuthorizedKeysCommandUser opksshuser opkssh uses the '/usr/local/etc/opk' directory, where providers and identities are stored. Neither the directory nor the files are created automatically, so you must create them yourself. After creating the 'auth_id' and 'providers' files, they must have the following permissions: chown root:opksshuser /usr/local/etc/opk/auth_id chmod 640 /usr/local/etc/opk/auth_id chown root:opksshuser /usr/local/etc/opk/providers chmod 640 /usr/local/etc/opk/providers Users attempting to use opkssh from jails, please add "allow.mlock" or it will not run.