| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
This also fixes code style fixes in the Sphinx configuration file.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This option can be used to skip a number of rows in the CSV file before
the key data is read. If the number of rows to skip is 0, the column
interpretation should be provided using the --columns option.
|
|
|
|
|
| |
This option can be used to set key properties for all keys in the PSKC
file.
|
|
|
|
|
|
| |
This option can be used to override the list of columns as found in the
first line of the CSV file or provide a mapping for values found in the
first line to PSKC properties.
|
|
|
|
|
|
| |
This script reads a CSV file and writes out a PSKC file with the key
information from the CSV file. The CSV file is expected to have one row
for each key and key property values in columns.
|
|
|
|
|
|
| |
This script reads a PSKC file in any supported format and writes out a
RFC 6030 compliant version of the file, optionally with the encryption
removed or (re-)encrypting the file with a new key.
|
|
|
|
|
| |
This adds a function to decrypt all values and remove the encryption of
an encrypted PSKC file.
|
|
|
|
| |
This also slightly tunes the way Sphinx documentation is built.
|
|
|
|
|
|
| |
This property can be use to see whether the PSKC file needs an
additional pre-shared key or passphrase to decrypt any stored
information.
|
| |
|
|
|
|
|
| |
This makes the old name (pin_max_failed_attemtps) available as a
deprecated property.
|
| |
|
|
|
|
|
| |
This provides a read-only userid property on Key objects that uses the
key_userid or device_userid value, whichever one is defined.
|
|
|
|
| |
This also includes a few other small documentation improvements.
|
| |
|
| |
|
|
|
| |
This accidentally slipped in as part of beafc6b.
|
|
|
|
|
|
|
|
| |
This allows having multiple keys per device while also maintaining the
previous API.
Note that having multiple keys per device is not allowed by the RFC 6030
schema but is allowed by some older internet drafts.
|
|
|
|
|
|
| |
This tries to make it clearer that the setup_preshared_key() and
setup_pbkdf2() functions are meant to be used when writing out PSKC
files.
|
| |
|
| |
|
|
|
|
|
|
| |
Either determine the encryption algorithm from the PSKC file or from the
explicitly set value. This also adds support for setting the encryption
key name.
|
|
|
|
|
| |
This adds a development notes section to the README and changes the
wording on the encryption page.
|
| |
|
|
|
|
|
|
|
| |
This updates the documentation with the new features (writing PSKC
files) as well as many editorial improvements, some rewording and a few
typo fixes. Some things were moved around a little in order to be more
easily readable and easier to find.
|
| |
|
|
|
|
|
|
|
|
|
| |
This updates the documentation with the current API, adding information
on exceptions raised, HMAC algorithms supported and changes to the MAC
checking.
This also includes some editorial changes to some of the text and making
references shorter by not including the full package path.
|
| |
|
| |
|
|
|