ducky-tools | Tools for working with Ducky One keyboard firmware updates

First, install go - https://golang.org/. At least version 1.11 for go mod support. This also uses [gousb (https://github.com/google/gousb)](https://github.com/google/gousb), which itself depends on libusb-1.0. This should be an easy dependency to satisfy on Linux and Mac. Consult the gousb page for more information. This extracts the information from an update file (.exe or .toml) and writes it out to a .toml-based description and set of binary files. This will extract the firmware blob and some other data from the .exe updater into files in the current working directory, with a description stored in One_TKL_EU_L_1.03r.exe.toml. This .toml file can be used as an input to ducky iap update (see below). The firmware blob itself will be written to One_TKL_EU_L_1.03r.exe.internal.enc.bin. Note that this data is likely to be scrambled with a 52-byte XOR key, and so won’t look like Arm/Thumb code. The keyboard expects to receive the scrambled data during the programming process, and descrambles it with a key which is only stored in the keyboard and not the updater.