This repository contains some development tools for the Tillitis TKey USB security stick.
-
tkey-runapp
: A simple development tool to load and start any TKey device app. -
run-tkey-qemu
: Script around our TKey emulator OCI imageghcr.io/tillitis/tkey-qemu-tk1-23.03.1
.
See the TKey Developer Handbook for how to develop your own apps, how to run and debug them in the emulator or on real hardware.
Current list of known projects.
You have two options, either our OCI image
ghcr.io/tillitis/tkey-builder
for use with a rootless podman setup,
or native tools. See the Devoloper
Handbook for setup.
With native tools you should be able to use make
$ make
If you want to use podman and you have make
you can run:
$ podman pull ghcr.io/tillitis/tkey-builder:2
$ make podman
or run podman directly with
$ podman run --rm --mount type=bind,source=.,target=/src -w /src -it ghcr.io/tillitis/tkey-builder:2 make -j
To install:
sudo make install
If you want to reload the udev rules to access the TKey use:
sudo make reload-rules
Undo the installation with the uninstall
target.
The client app tkey-runapp
only loads and starts a device app. It's
mostly a development tool. You'll then have to switch to a different
client app that speaks your app's specific protocol. Run with -h
to
get help.
$ ./run-tkey-qemu
This gives you tkey-qemu-pty
in the current working directory you
can attach your client programs to, typically with --port ./tkey-qemu-pty
.
Unless otherwise noted, the project sources are licensed under the terms and conditions of the "GNU General Public License v2.0 only":
Copyright Tillitis AB.
These programs are free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, version 2 only.
These programs are distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program. If not, see:
See LICENSE for the full GPLv2-only license text.
External source code we have imported are isolated in their own
directories. They may be released under other licenses. This is noted
with a similar LICENSE
file in every directory containing imported
sources.
The project uses single-line references to Unique License Identifiers as defined by the Linux Foundation's SPDX project on its own source files, but not necessarily imported files. The line in each individual source file identifies the license applicable to that file.
The current set of valid, predefined SPDX identifiers can be found on the SPDX License List at:
All contributors must adhere to the Developer Certificate of Origin.