Need help with ssh-permit-a38?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

ierror
451 Stars 18 Forks MIT License 61 Commits 1 Opened issues

Description

Central management and deployment for SSH keys

Services available

!
?

Need anything else?

Contributors list

No Data

SSH Permit A38

Central management and deployment for SSH keys

Build Status

asciicast

Features

  • Central management of public SSH keys and servers in a simple and readable JSON database
  • Sync authorized users to the servers authorized_keys
  • SSH config support for the sync command connection paramaters (Hostname, User, Port)
  • User Groups
  • Host aliases
  • Diff of authorized_keys to sync and the existing one

Latest release v0.2.0 - 2018-08-18

Download prebuilt binaries

Previous Releases

Changelog

v0.2.0 - 2018-08-18

  • Support for SSH config files #5

    If a ssh-permit-a38 hostname or alias matches the ssh configs Host (or Hostname), User, Port and Host information are used for authorized_keys sync connection

  • sync command switch -y, --yes-authorized-keys-prompt: Automatic yes to authorized_keys location prompts

Previous Changes

Build from source

Prerequisites

Build

make build

Quickstart

ssh-permit-a38 host urlsmash.403.io add
ssh-permit-a38 user obelix add
ssh-permit-a38 user obelix grant urlsmash.403.io 
ssh-permit-a38 sync

Documentation

Run

ssh-permit-a38 howto

or online

Running the tests

make test

Coding style

We use rustfmt to format the source.

make fmt

Contributing

Pull requests welcome! ;)

Versioning

We use SemVer for versioning. For the versions available, see the tags on this repository.

Authors

See also the list of contributors who participated in this project.

License

This project is licensed under the MIT License - see the LICENSE file for details

FAQ

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.