| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
This is the extension that is suggested in RFC6030.
|
| |
|
| |
|
| |
|
|
|
|
| |
This also splits the parsing to a parse() function for consistency.
|
|
|
|
|
|
|
|
|
| |
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 documents most of the API of the parsing functions and the PSKC
class.
|
|
|
|
| |
Also contains small consistency improvement.
|
|
|
|
| |
This also hides two properties that are not part of the public API.
|
|
|
|
| |
This documents classes in the pskc.encryption module.
|
|
|
|
| |
This also allows re-organising the imports a bit.
|
| |
|
| |
|
|
|
|
|
| |
This supports deriving the key from a passphrase and information present
in the DerivedKey and PBKDF2-params XML elements.
|
| |
|
|
|
|
|
| |
This implements message message authentication code checking for the
encrypted values if MACMethod and ValueMAC are present.
|
|
|
|
|
| |
This adds an encryption module that provides wrappers for handling
decryption.
|
|
|
|
|
| |
This ensures that DataType values are retrieved dynamically instead of
at the time the PSKC file was parsed in order to make decryption work.
|
| |
|
|
|
|
|
| |
This parses key policy from PSKC files and provides a few utility
methods to help with policy validation.
|
| |
|
|
|
|
|
| |
This gets most simple string values from the KeyPackage as well as some
integer and boolean values.
|
| |
|
|
|
|
|
|
|
|
|
| |
This class is used for handling PSKC files. It will parse the file and
store relevant properties for easy access. The Key class corresponds to
a single key defined in the PSKC file.
This is a very minimal implementation that only provides some meta-data
from the file and keys (work in progress).
|
|
|