blessclient
Please note: If you believe you have found a security issue, please responsibly disclose by contacting us at security@chanzuckerberg.com.
Inspiration for this project comes from lyft/python-blessclient.
We decided to write in Go because it is much easier to distribute a statically linked binary to a large team than having to deal with python environments. Some features from lyft/python-blessclient are currently missing but will be added over time while others are purposefully excluded.
Versions
We are currently in the process of releasing a new major version of blessclient that will replace netflix/bless for a version that relies on federated identity.
v0.x.x - deprecation notice
This version will soon be deprecated.
For the time-being brew install blessclient
will still point to v0.x.x
You can use homebrew to install with
brew tap chanzuckerberg/tap
brew install blessclient@1
We will keep a v0 branch around for high priority fixes until migrated fully to v1.x.x
.
v1.x.x - in active development
More to come.
Install
Mac
You can use homebrew -
brew tap chanzuckerberg/tap
brew install blessclient@1
Linux
Binaries are available on the releases page. Download one for your architecture, put it in your path and make it executable.
You might also need to install libusb-dev
. For ubuntu you can install libusb-1.0-0-dev
.
Usage
At a high level:
- Install blessclient
- If you don't have an SSH key, generate one with
ssh-keygen -t rsa -b 4096
- Import or generate a blessclient config. You can find an example config here.
- Run
blessclient run
and make sure there are no errors
- Modify your ssh config to be bless compatible
- ssh, scp, rsync as you normally would
Config
By default, blessclient
looks for configs in ~/.blessclient/config.yml
. You can always override this blessclient run -c /my/new/config.yml
Some more information on the config can be found here.
There is a built-in method to facilitate the generation of blessclient configs:
Import-config
A few options here:
blessclient import-config git@github.com:/..../teamA/blessconfig.yml
blessclient import-config https://www.github.com/..../teamA/blessconfig.yml
blessclient import-config /home/user/.../teamA/blessconfig.yml
blessclient import-config s3::https://s3.amazonaws.com/bucket/teamA/blessconfig.yml
This command uses go-getter to fetch a config and thus supports any source that go-getter supports.
You can see an example config with dummy values here. Download the example, modify the values, and blessclient import-config <path>
it to get started.
.ssh/config
This is the nice part about blessclient - in general, you can write an ssh config to transparently use blessclient. scp, rsync, etc should all be compatible!
Such an ssh config could look like:
Match OriginalHost bastion.foo.com exec "blessclient run"
IdentityFile ~/.ssh/id_rsa
Host 10.0.*
ProxyJump bastion.foo.com
User admin
Host bastion.foo.com
User admin
This ssh config does a couple of interesting things -
- It transparently requests an ssh certificate if needed
- It transparently does a ProxyJump through a bastion host (assuming 10.0.* is an ipblock for machines behind the bastion)
Common Errors
Unsafe RSA public key
Bless lambda is rejecting your key because because it is not cryptographically sound. You can generate a new key ssh-keygen -t rsa -b 4096
and use that instead.
SSH client 7.8 can't connect with certificates
There are a couple of outstanding bugs related to openSSH client 7.8
You can check your version with
ssh -V
Other
Deploying BLESS
There are already several great guides on how to run a BLESS lambda. If you take a moment to skim through these, you'll notice that setting up a successful BLESS deployment requires thorough knowledge of AWS Lambda and IAM. Even then, you'll probably spend hours digging through CloudWatch logs (and who likes doing that).
To further simplify this process, we've put together a terraform provider and module to automate BLESS deployments.
Contributing
Contributions and ideas are welcome! Please don't hesitate to open an issue, join our gitter chat room, or send a pull request.
Go version >= 1.12 required.
This project is governed under the Contributor Covenant code of conduct.