For a bare raspbian system, first:
Note: Your Zymkey will require a number of packages to be installed from the Raspberry Pi and Zymbit apt repositories. The following setup script will be installing a number of files and software packages on your system:
- Docker and docker-compose
- Zymbit .service files located in the
Download and install the necessary Zymbit Cloud services
curl -G https://s3.amazonaws.com/zymbit-apt/setup.sh | sudo bash
(grab a cup of coffee because this will take some time )
###Install Zymkey USB Hardware
Zymkey will work in any of the four USB slots on your Pi
##Bind Zymkey to Host
Insure your Zymkey is plugged into the host Pi.
Sign up and create a new project
Copy the bootstrap key as shown:
Return to the shell and paste in your bootstrap key in the following configuration file:
sudo nano /etc/systemd/system/zymbit-connect.service.d/10-env.conf
The configuration file should look similar to this when you are finished with step 4.
Reload the daemon:
sudo systemctl daemon-reload
Reload https://console.zymbit.com and you should see your device with a Zymkey status of unbound and the option to Bind now! Note: this could be delayed about a minute. Right now your pi is starting up the Zymbit connect service for the first time.
Click the Bind Now! Button and the Zymkey LED should turn a solid green. Your Zymkey is now bound!
Please read the Zymkey community pages for documentation on:
- LUKS filesystem encryption
The quickest way to get started is to see the various methods at work by running these scripts:
Is it possible to get this working on a non-raspberry pi hardware?
It appears most of the packages are available or the source package is available except for:
Hey @razron, welcome!
It may be possible, especially the USB version, which does not depend on a GPIO pin layout.
While we are currently focused on nailing the Raspberry Pi experience internally, I’m personally interested and excited to see this working on other hardware as well! Let me know if you’re going to give this a shot and I’ll help you out where I can. I would suggest sticking with an ARM-based Debian-like distro to start, as it will be easier. From there, first step would be to get the pre-requisites installed; the biggest one being Docker.
setup.sh a look and see if it “just works” on your device. Please report back with any issues you may have and we’ll go from there.
curl -s https://s3.amazonaws.com/zymbit-apt/setup.sh > zymbit-setup.sh
Being a backer of your initial Kickstarter campaign, I’ve got a Zymkey. I’m finally getting around to setting it up for a project. I’ve attempted to run your
setup.sh script mentioned above. However, it seems the GPG
apt key it attempts to load appears to be invalid, leading to errors in
apt-get. Has the script and/or key been updated? How to proceed?
W: GPG error: https://zymbit-apt.s3.amazonaws.com stable Release: The following signatures were invalid: BADSIG CABC9FCA2954FDFE Zymbit Inc. <email@example.com>
Oh, now I see this post: https://community.zymbit.com/t/zymkey-apt-repo-url-has-changed/191/6
I’ve updated the URL in
/etc/apt/sources.list.d/zymbit.list. But that
apt GPG key is still invalid:
W: GPG error: https://zymkey-sw-repo.s3.amazonaws.com jessie InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1E8314B357AE01DB
setup.sh script should be updated on S3…
Solution discovered? … disregard the (legacy?) script mentioned on this page. And install download & run the setup script mentioned on https://community.zymbit.com/t/getting-started-with-zymkey-4i/202 (and other more recent “Getting Started” pages here).
Thanks for backing us on Kickstarter ! That product is somewhat vintage and their may be some incompatibilties with our current products.
To help us help you, can you please send us the serial number (white label on early USB units). If you prefer to do this in a private channel, then do so here. Contact Zymbit.
where can i purchase a usb zymkey?