| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
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 adds support for creating and verifying embedded XML signatures in
PSKC files. This uses the third-party signxml library for actual signing
and verification.
The signxml library has a dependency on lxml and defusedxml (and a few
others) but all parts of python-pskc still work correctly with our
without lxml and/or defusedxml and signxml is only required when working
with embedded signatures.
This modifies the tox configuration to skip the signature checks if
singxml is not installed and to only require 100% code coverage if the
signature tests are done.
|
| |
|
|
|
|
| |
Note that asymmetric encryption and digital signature checking has not
yet been implemented so the tests are pretty minimal.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This adds tests to ensure that incorrect attribute and value types in
the PSKC file raise a ValueError exception and extends the tests for
invalid encryption options.
This removes some code or adds no cover directives to a few places that
have unreachable code or are Python version specific and places doctest
directives inside the doctests where needed.
|
|
|
|
|
| |
This puts the test PSKC files in subdirectories so they can be organised
more cleanly.
|
|
|
|
|
|
|
|
| |
This enables support for Python 3 together with Python 2 support with a
single codebase.
On Python 3 key data is passed around as bytestrings which makes the
doctests a little harder to maintain across Python versions.
|
| |
|
| |
|
|
|
|
| |
This is the extension that is suggested in RFC6030.
|
|
|
|
|
| |
This tests that, before the PSKC ecnryption is key available, the secret
from the key cannot be extracted.
|
|
|
|
|
|
|
|
|
| |
This documents most of the information that is available per key and
adds a few other minor cosmetic changes.
This also re-organises the key properties to be in a slightly more
logical order and renames the userid key property to key_userid to more
clearly distinguish it from device_userid.
|
| |
|
|
|
|
|
| |
This tests encrypted key derivation using PBKDF2 and a pre-shared
passphrase.
|
|
|
|
| |
This test key encryption with a pre-shared key and MAC checks.
|
|
|
|
| |
This test extraction of key policy information and cross-key references.
|
|
|
|
|
| |
This tests for key profile and key reference properties that can be used
to reference external keys.
|
|
This tests Figure 3 from RFC6030 with a very basic plain text secret key
and some supplementary data.
|