New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test failures depending on openssl compilation flags #175
Comments
Here's a log, and i'll PR a workaround:
|
in this repo is the issue just that ecdsa with sha1 isn't supported or the specific curve ? |
Gimme a minute :) |
List of failures:
|
ok so it looks like it's just sha1 which is the issue here so if we just change this line to be |
Do you mean replace |
It works now. |
Note that it's more something about default security setup than about debian in itself. |
#176 works or this repo always worked ? |
#176 works. It was failing before. |
ok great
…On Wed, Jan 3, 2018 at 4:17 PM Jérémy Lal ***@***.***> wrote:
#176 <https://github.com/crypto-browserify/crypto-browserify/pull/176>
works. It was failing before.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/crypto-browserify/crypto-browserify/issues/175#issuecomment-355129812>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABE4n7X_9kp8LEFMlqtf-Uf1fUZmABEyks5tG-6EgaJpZM4RPkAw>
.
|
Algorithms available at runtime depend on how openssl (which could be a shared lib) has been configured.
Test such as https://github.com/crypto-browserify/crypto-browserify/blob/9730d317e2141099b8e56d2afbaf806eb616e0a3/test/sign.js#L34
should not assume all algorithms are available.
The test could either catch the exception (createSign throws with "Unknown message digest") or check
crypto.getCiphers()
.See also browserify/browserify-sign#37
The text was updated successfully, but these errors were encountered: