| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
The only files that were lacking a license were the 0-sized __init__.py
files — since those are not copyrighteable, make them Unlicense relesed.
|
| |
|
|
|
|
|
|
|
| |
See https://reuse.software/ for details.
For simplicity, the support files, that are vastly copy-pasta, are licensed
under MIT license, rather than LGPL-2.1-or-later.
Note that `reuse lint` currently fails due to fsfe/reuse-tool#208.
|
| |
|
|
| |
This is following the advice provided in https://matija.suklje.name/how-and-why-to-properly-write-copyright-statements-in-your-code
|
| | |
|
| |
|
|
| |
This requires the released version of usbmon-tools.
|
| |
|
|
|
|
| |
This in turn allows wrapping the FreeStyle access in its own session class,
which the freestyle_hid_console can use without dirty tricks, and without
triggering the now-abstract class.
|
| |
|
|
|
|
|
|
|
|
|
| |
The f-strings formatted strings are generally simpler to write, read and
debug, with a few exceptions.
Keep the logging strings lazy, keep the CSV-building with %-formatting, as
it makes it more readable.
In fsoptium, keep `'$%s\r\n'` as a %-format, to avoid making it
`f'${command}\r\n'` that would make it easy to mistake for a Shell variable.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
This includes changes to the flags, so that instead of an address prefix
you need to provide a full device address, and instead of `--libre2`,
there's a `--encrypted_protocol` flag.
If the capture includes the descriptors, neither flags are needed because
the script identifies them itself.
|
| |
|
|
| |
These messages are not encrypted, but they can also be safely ignored.
|
| |
|
|
|
| |
This encodes some more details of which commands are encrypted and not, but
makes decoding easier.
|
| |
|
|
|
|
|
|
|
|
|
| |
The tool needs https://github.com/Flameeyes/usbmon-tools to work, and is
derived off the extract-hid-chatter tool in that repository, so it's
Apache-2 licensed (unlike the rest of the repository) and shares copyright
with the usbmon-tools authors.
While this does not work correctly for Libre2 traces, it does appear to
work fine with Libre1 systems with text protocol exchanges, and it provides
a starting point.
|
| | |
|
| |
|
|
| |
This can be used to help testing new FreeStyle devices, like the Libre2.
|
| |
|
|
| |
This makes it easier to identify the expected command range of a FreeStyle device.
|
|
|
This makes it possible to send and receive text-command protocols to a FreeStyle HID device without actually writing any code, to identify possible valid commands.
|
