-
-
Notifications
You must be signed in to change notification settings - Fork 129
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
Windows support: Windows openssl binaries use ' = ' instead of '=', breaking scraping #97
Comments
Will not support that because its not a current version.(2004) as i can see.
Von meinem iPhone gesendet
… Am 05.12.2016 um 17:06 schrieb Mike MacCana ***@***.***>:
The Shining Light Productions Win32 openssl binaries use a slightly different formatting for separating fields in the Subject
Windows
~\Documents\foocorp\node_modules\pem $ openssl req -text -noout -verify -in ..\..\deleteme.csr
verify OK
Certificate Request:
Data:
Version: 1 (0x0)
Subject: C = GB, L = London, O = foocorp Limited, CN = ssltest.foocorp.com
Unix
***@***.*** foocorp]$ openssl req -text -noout -verify -in deleteme.csr
verify OK
Certificate Request:
Data:
Version: 0 (0x0)
Subject: C=GB, L=London, O=foocorp Limited, CN=ssltest.foocorp.com
Meaning npm test fails on Windows. I'm not sure why but it's an easy fix. Sending a PR.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Issue is occurring on
|
Oh wait: the copyright notice. Yeah the Shining Light website has an out of date copyright notice, I told the maintainer about it (and the mixed content issue) and he got really angry at me in response. Despite that, the site does actually maintain up-to-date openssl binaries. |
Thanks, i was only check it short by smartphone. Have merged it. |
The Shining Light Productions Win32 openssl binaries use a slightly different formatting for separating fields in the
Subject
Windows
Unix
Meaning
npm test
fails on Windows. I'm not sure why but it's an easy fix. Sending a PR.The text was updated successfully, but these errors were encountered: