Arthur de Jong

Open Source / Free Software developer

summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Get files ready for 0.4 release0.4Arthur de Jong2016-03-284-2/+378
|
* Document may_use() policy functionArthur de Jong2016-03-281-4/+4
|
* Implement writing encrypted filesArthur de Jong2016-03-2712-88/+816
|\ | | | | | | | | | | This adds support for setting up encryption keys and password-based key derivation when writing PSKC files. Also MAC keys are set up when needed.
| * Document writing encrypted filesArthur de Jong2016-03-276-25/+105
| |
| * Add encryption error testsArthur de Jong2016-03-261-0/+74
| |
| * Add tests for writing encrypted PSKC filesArthur de Jong2016-03-261-0/+175
| |
| * Allow configuring a pre-shared keyArthur de Jong2016-03-261-13/+38
| | | | | | | | | | | | | | This method allows configuring a pre-shared encryption key and will chose reasonable defaults for needed encryption values (e.g. it will choose an algorithm, generate a new key of the appropriate length if needed, etc.).
| * Allow configuring PBKDF2 key derivationArthur de Jong2016-03-262-12/+127
| | | | | | | | | | This factors out the PBKDF2 key derivation to a separate function and introduces a function to configure KeyDerivation instances with PBKDF2.
| * Allow configuring a MAC keyArthur de Jong2016-03-262-0/+60
| | | | | | | | | | This method will set up a MAC key and algorithm as specified or use reasonable defauts.
| * Generate MAC valuesArthur de Jong2016-03-262-13/+30
| |
| * Write MACMethodArthur de Jong2016-03-263-3/+52
| | | | | | | | | | | | This also makes the MAC.algorithm a property similarly as what is done for Encryption (normalise algorithm names) and adds a setter for the MAC.key property.
| * Write out encrypted valuesArthur de Jong2016-03-262-11/+88
| | | | | | | | | | | | | | | | | | The Encryption class now has a fields property that lists the fields that should be encrypted when writing the PSKC file. This adds an encrypt_value() function that performs the encryption and various functions to convert the plain value to binary before writing the encrypted XML elements.
| * Make Encryption and MAC constructors consistentArthur de Jong2016-03-263-6/+4
| | | | | | | | | | | | This removes calling parse() from the Encryption and MAC constructors and stores a reference to the PSKC object in both objects so it can be used later on.
| * Write encryption key informationArthur de Jong2016-03-263-3/+40
| | | | | | | | | | | | This writes information about a pre-shared key or PBKDF2 key derivation in the PSKC file. This also means that writing a decrypted version of a previously encrypted file requires actively removing the encryption.
| * Add algorithm_key_lengths propertyArthur de Jong2016-03-262-16/+37
|/ | | | | This property on the Encryption object provides a list of key sizes (in bytes) that the configured encryption algorithm supports.
* Also check key expiry in may_use()Arthur de Jong2016-03-234-12/+50
|
* Support reading password or key in pskc2csvArthur de Jong2016-03-201-14/+35
| | | | | This supports reading the encryption password or key from the command line or from a file.
* Copy namespaces to toplevel elementArthur de Jong2016-03-201-0/+11
| | | | | | Ensure that when writing an XML file all namespace definitions are on the toplevel KeyContainer element instead of scattered throughout the XML document.
* Support writing to text streams in Python 3Arthur de Jong2016-03-192-4/+7
| | | | | This supports writing the XML output to binary streams as well as text streams in Python 3.
* Improve tests and test coverageArthur de Jong2016-03-1914-60/+166
| | | | | | | | | | 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.
* Support both CheckDigit and CheckDigitsArthur de Jong2016-03-194-4/+90
| | | | | | RFC 6030 is not clear about whether the attribute of ChallengeFormat and ResponseFormat should be the singular CheckDigit or the plural CheckDigits. This ensures that both forms are accepted.
* Implement policy checkingArthur de Jong2016-03-193-7/+139
| | | | | This checks for unknown policy elements in the PSKC file and will cause the key usage policy check to fail.
* Add a few tests for vendor filesArthur de Jong2016-03-194-0/+434
| | | | | Some vendor-specific files were lifted from the LinOTP test suite and another Feitian file was found in the oath-toolkit repository.
* Support various integer representationsArthur de Jong2016-03-193-4/+70
| | | | | | | | | | | | | | | | | | | This extends support for handling various encoding methods for integer values in PSKC files. For encrypted files the decrypted value is first tried to be evaluated as an ASCII representation of the number and after that big-endian decoded. For plaintext values first ASCII decoding is tried after which base64 decoding is tried which tries the same encodings as for decrypted values. There should be no possibility for any base64 encoded value (either of an ASCII value or a big-endian value) to be interpreted as an ASCII value for any 32-bit integer. There is a possibility that a big-endian encoded integer could be incorrectly interpreted as an ASCII value but this is only the case for 110 numbers when only considering 6-digit numbers.
* Re-organise test filesArthur de Jong2016-01-3036-34/+34
| | | | | This puts the test PSKC files in subdirectories so they can be organised more cleanly.
* Add test for incorrect key derivationArthur de Jong2016-01-301-0/+10
| | | | | If no key derivation algorithm has been specified in the PSKC file an exception should be raised when attempting to perform key derivation.
* Refactor out EncryptedValue and ValueMACArthur de Jong2016-01-243-155/+135
| | | | | | | | | This removes the EncryptedValue and ValueMAC classes and instead moves the XML parsing of these values to the DataType class. This will make it easier to support different parsing schemes. This also includes a small consistency improvement in the subclasses of DataType.
* Normalise algorithm namesArthur de Jong2016-01-242-3/+46
| | | | | This transforms the algorithm URIs that are set to known values when parsing or setting the algorithm.
* Add encryption algorithm propertyArthur de Jong2016-01-244-3/+45
| | | | | | 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.
* Fix a problem when writing previously encrypted fileArthur de Jong2016-01-242-1/+22
| | | | | This fixes a problem with writing a PSKC file that is based on a read file that was encrypted.
* Strip XML namespaces before parsingArthur de Jong2016-01-246-85/+79
| | | | | | | | | This simplifies calls to the find() family of functions and allows parsing PSKC files that have slightly different namespace URLs. This is especially common when parsing old draft versions of the specification. This also removes passing multiple patterns to the find() functions that was introduced in 68b20e2.
* Update some documentationArthur de Jong2015-12-282-4/+13
| | | | | This adds a development notes section to the README and changes the wording on the encryption page.
* Fix typo in the documentationMathias Laurin2015-12-011-1/+1
|
* Support Python 3Mathias Laurin2015-12-011-1/+2
|
* Make value conversion methods static privateMathias Laurin2015-11-301-11/+20
| | | | | - the conversions do not call self: they are static - the conversions are not to be used out of the class: make private
* Provide abstract methods to clarify APIMathias Laurin2015-11-301-4/+12
|
* Fix typo in variable nameMathias Laurin2015-11-301-6/+6
|
* Fix doctest: IGNORE_EXCEPTION_DETALMathias Laurin2015-11-301-5/+5
|
* Get files ready for 0.3 release0.3Arthur de Jong2015-10-075-3/+141
|
* Update documentationArthur de Jong2015-10-078-87/+150
| | | | | | | 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.
* Support Python 3Arthur de Jong2015-10-0616-125/+166
| | | | | | | | 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.
* Fix issue with namespaced PBKDF2 parametersArthur de Jong2015-10-064-25/+141
| | | | | | | | | | | | The find() utility functions now allow specifying multiple paths to be searched where the first match is returned. This allows handling PSKC files where the PBKDF2 salt, iteration count, key length and PRF elements are prefixed with the xenc11 namespace. A test including such a PSKC file has been included. Thanks to Eric Plet for reporting this.
* Provide a sample pskc2csv scriptArthur de Jong2014-10-121-0/+127
| | | | | This is a simple command-line utility that reads a PSKC file and outputs information on keys as CSV.
* Move encryption functions in pskc.crypto packageArthur de Jong2014-10-096-4/+4
| | | | | | This moves the encryption functions under the pskc.crypto package to more clearly separate it from the other code. Ideally this should be replaced by third-party library code.
* Rename pskc.parse to pskc.xmlArthur de Jong2014-10-096-19/+26
| | | | | | | This renames the parse module to xml to better reflect the purpose of the module and it's functions. This also introduces a parse() function that wraps etree.parse().
* Support writing unencrypted PSKC filesArthur de Jong2014-06-285-0/+317
|\
| * Add test for writing PSKC filesArthur de Jong2014-06-281-0/+143
| | | | | | | | | | This makes a simple doctest that checks the writing of the XML representation of the PSKC data.
| * Add function for writing XMLArthur de Jong2014-06-282-0/+17
| | | | | | | | This provides a function for pretty-printing the generated XML document.
| * Construct XML document with basic PKSC informationArthur de Jong2014-06-283-0/+109
| | | | | | | | | | | | This introduces make_xml() functions to build an XML document that contains the basic PSKC information and keys. This currently only supports writing unencrypted PSKC files.
| * Introduce mk_elem() to create elementsArthur de Jong2014-06-281-0/+48
|/ | | | | | This introduces the mk_elem() function that can be used to create ElementTree elements for building XML documents. This function transparetly handles namespaces, translation of values into XML etc.