[WIP] Add unencrypted PEM PKCS8 dumping support

Adds unencrypted PEM dumping for private keys. Public keys and encrypted (PBE) support will be in separate PRs (and PBE requires some discussion. I tried to dig up the issue we've used for this in the past but couldn't find it)
Is there a compelling reason to let people have opinions about this stuff?
I guess if there's "some new hotness" and we default to that we could be
creating PEMs that are unreadable by other programs...

On Wed, Oct 1, 2014 at 2:53 PM, Paul Kehrer <notifications@github.com>
wrote:

> In cryptography/hazmat/backends/interfaces.py:
>
> > @@ -240,6 +240,12 @@ def load_pem_public_key(self, data):
> >          Loads a public key from PEM encoded data.
> >          """
> >
> > +    @abc.abstractmethod
> > +    def dump_unencrypted_pem_pkcs8_private_key(self, key):
>
> Are we going to build an enum of algorithm specifiers we want to
> recognize? It also looks like PEM_write_bio_PKCS8PrivateKey uses PBKDF2
> with 2048 iterations. It's unclear to me if there's a way to configure
> that. I believe @public <https://github.com/public> knows more about this
> as we've talked about it a bit in the past.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/pyca/cryptography/pull/1380/files#r18310832>.
>



-- 
"I disapprove of what you say, but I will defend to the death your right to
say it." -- Evelyn Beatrice Hall (summarizing Voltaire)
"The people's good is the highest law." -- Cicero
GPG Key fingerprint: 125F 5C67 DFE9 4084