This repository has been archived by the owner on Jun 15, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 8
Add ed25519 and secp256k1 #30
Comments
Hello @AlbertoElias Thanks for creating the issue. It would be great if you could create a PR for that 😀 |
@vasco-santos Hey, I have an implementation pending tests, and even though that existing tests do pass, I get this error:
Seems like it can't run the browser tests. Any ideas? I wanted to push my implementation to double check it with you but it doesn't let me until tests run. Thanks! |
I managed to get the browser tests running, but I had to modify the browser configuration in browsers: ['ChromeHeadlessNoSandbox'],
customLaunchers: {
ChromeHeadlessNoSandbox: {
base: 'ChromeHeadless',
flags: ['--no-sandbox']
}
} I created a PR here: ipfs/aegir#333 |
Also, my work on this issue is blocked by libp2p/js-libp2p-crypto-secp256k1#13 |
This was referenced Feb 14, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I saw that it only supports rsa keys here: https://github.com/libp2p/js-libp2p-keychain/blob/master/src/keychain.js#L201
But the underlying library (https://github.com/libp2p/js-libp2p-crypto) also supports ed25519, and also secp256k1 if you add https://github.com/libp2p/js-libp2p-crypto-secp256k1.
Is there anything holding this feature back or is it something simple that I could create a PR for it so it will be supported downstream in js-ipfs?
The text was updated successfully, but these errors were encountered: