Skip to content

Preparation for upgrading to the forthcoming openssl-1.0.1m #1186

@shigeki

Description

@shigeki

OpenSSL-1.0.1m is to be released on March 19 which fixes vulnerabilities of high severity. For quick release of iojs, I've just made a branch of upgrading it to the current HEAD of OpenSSL_1_0_1-stable branch in https://github.com/shigeki/io.js/tree/WIP_OpenSSL_1_0_1m .

After extracting all sources of the current HEAD of OpenSSL_1_0_1-stable in 879c4c3 , the following 5 commits are needed.

14a7f46 deps: replace all headers in openssl
f46274e deps: separate sha256/sha512-x86_64.pl for openssl
3d8b231 deps: fix openssl assembly error on ia32 win32
206b3f0 deps: remove vpaesni-x86_64.asm in x64-win32-masm
1efcfd5 openssl: fix keypress requirement in apps on win32

The forthcoming release would not be so much changed from the current HEAD so these commits can easily be cherry-picked.
I also checked asm files are not changed with asm/Makefile. CI results of https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/322/ are fine with known test failures except the one of test-signal-unregister on Ubuntu10.01 but I think it's not related with this upgrade.

@bnoordhuis @indutny Could you please review the above five commits for preparation?

Metadata

Metadata

Assignees

No one assigned

    Labels

    cryptoIssues and PRs related to the crypto subsystem.tlsIssues and PRs related to the tls subsystem.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions