This repository was archived by the owner on Jan 22, 2025. It is now read-only.
File tree Expand file tree Collapse file tree
Expand file tree Collapse file tree Original file line number Diff line number Diff line change 11# SSH CA Bot
22
3+ [ ![ License] ( https://img.shields.io/badge/license-BSD-success.svg )] ( https://opensource.org/licenses/BSD-3-Clause )
4+ [ ![ CircleCI] ( https://circleci.com/gh/keybase/bot-sshca.svg?style=shield )] ( https://circleci.com/gh/keybase/bot-sshca )
5+ [ ![ Go ReportCard] ( https://goreportcard.com/badge/github.com/keybase/bot-sshca )] ( https://goreportcard.com/report/github.com/keybase/bot-sshca )
6+
37See [ keybase.io/blog/keybase-ssh-ca] ( https://keybase.io/blog/keybase-ssh-ca ) for a full announcement and description
48of the code in this repository.
59
6- The idea here is to control SSH access to servers (without needing to install anything on them) based simply on
7- cryptographically provable membership in Keybase teams.
10+ This repository provides the tooling to control SSH access to servers (without needing to install anything
11+ on them) based simply on cryptographically provable membership in Keybase teams.
812
913SSH supports a concept of certificate authorities (CAs) where you can place a single public key on the server,
1014and the SSH server will allow any connections with keys signed by the CA cert. This is how a lot of large companies
You can’t perform that action at this time.
0 commit comments