Description
I posted my problem about this on StackOverflow several months ago, with no reply. After duking it out for awhile, I just stayed on 1.0.1 which generated signed certificates that worked as expected. Here's a snippet that works in 1.0.1, but exhibits the problem described in my SO post on newer versions of Cryptography.
Not a long-term solution as I can't just stay on 1.0.1, and it's time to get to the bottom of the issue. Eventually, I got this script snippet to generate certificates that worked on Windows -- but Linux Mint or OS X still had the old problem of not detecting the Certification path. Also, Firefox on Windows doesn't detect the Certification path.
Being now at my wits end, I decided to use another crypto library, and this snippet using pyopenssl creates and signs certs that work just perfect on all OSs. In a way my problem is solved, except that I'd rather not introduce a new dependency that already depends on Cryptography, which has a nicer API.
So I thought I'd file an issue because it seems like there's a bug. If not a bug, then no clear way in the docs to sign certificates, and if that could save the next guy 25 hours of his life, then it would help recover some of my effort.
Any assistance "Signing certificates For Humans Using Cryptography" would be much appreciated.
Thanks for the excellent work on the Cryptography module!