Commit graph

6 commits

Author SHA1 Message Date
adam
8c4cf510d6 py-trustme: updated to 0.6.0
0.6.0:
Features
Allow specifying organization and organization unit in CA and issued certs.
2020-01-22 19:20:32 +00:00
adam
849a3cbedb py-trustme: updated to 0.5.3
Trustme 0.5.3:
Features
Added :attr:`CA.from_pem` to import an existing certificate authority; this allows migrating to trustme step-by-step.
2019-11-13 20:29:12 +00:00
adam
7504e0acae py-trustme: updated to 0.5.2
0.5.2:
Unknown changes
2019-06-06 21:24:22 +00:00
adam
5491b37016 py-trustme: updated to 0.5.1
0.5.1:
Unknown changes
2019-05-02 09:41:04 +00:00
adam
843cfe403b py-trustme: updated to 0.5.0
Trustme 0.5.0:

Features
Added CA.create_child_ca() to allow for certificate chains
Added CA.private_key_pem to export CA private keys; this allows signing other certs with the same CA outside of trustme.
CAs now include the KeyUsage and ExtendedKeyUsage extensions configured for SSL certificates.
CA.issue_cert now accepts email addresses as a valid form of identity.
It’s now possible to set the “common name” of generated certs; see CA.issue_cert for details
CA.issue_server_cert has been renamed to CA.issue_cert, since it supports both server and client certs. To preserve backwards compatibility, the old name is retained as an undocumented alias.

Bugfixes
Make sure cert expiration dates don’t exceed 2038-01-01, to avoid issues on some 32-bit platforms that suffer from the Y2038 problem.
2019-01-25 13:33:15 +00:00
adam
210800f5a9 py-trustme: added version 0.4.0
trustme is a tiny Python package that does one thing: it gives you a fake
certificate authority (CA) that you can use to generate fake TLS certs to use
in your tests. Well, technically they're real certs, they're just signed by
your CA, which nobody trusts. But you can trust it. Trust me.
2018-09-06 13:36:16 +00:00