feat: adds support for ed25199 and secp256k1

[AlbertoElias]

Fixes #30

This is blocked by: libp2p/js-libp2p-crypto-secp256k1#13

@vasco-santos Could you review?

[vasco-santos]

Thanks for the PR @AlbertoElias

Can you rebase this PR with master? We are not using Jenkins CI anymore (travis now), and we need to have it here.

[AlbertoElias]

@vasco-santos done!

[vasco-santos]

Thanks for rebasing the PR @AlbertoElias

LGTM so far.

I would recommend installing the libp2p-crypto-secp256k1: AlbertoElias/js-libp2p-crypto-secp256k1#patch-1, so that you have the id, as well and you are able to add the remaining tests: exportKey and importKey.

[AlbertoElias]

@vasco-santos That should be done now. I also updated exporting and importing to fix marshaling.

[vasco-santos]

Great @AlbertoElias ! Thanks

Except for a minor request that I added now, this is good to go, once libp2p-crypto-secp256k1 is released.

[AlbertoElias]

@vasco-santos Everything is fixed, but it seems that what needs updating is libp2p/js-libp2p-crypto#137 I've tampered my package-lock.json to get everything running, but if js-libp2p-crypto decides to do a minor release instead of patch, js-libp2p-keychain's package.json would need to be updated as well

[raullaprida]

I'm creating a project using js libp2p and I created a Keystore where I store secp25k1 keys using PEM encrypted PKCS #8. (so now password wouldn't be just for RSA keys). Tests include being able to use OpenSSL to verify the encrypted keys.
Would that be a desired feature for the keychain? (I don't want to make a PR and be automatically rejected)