Skip to content
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

fix wrong hash results on Windows with some CPUs that support Intel SHA Extension #12913

Closed
wants to merge 2 commits into from

Commits on May 9, 2017

  1. deps: cherry-pick 4ae5993 from upstream OpenSSL

    This fixes wrong hash results on Windows with some CPUs that support
    Intel SHA Extension and resolves the issue of TLS connection errors.
    
    After upgrading forthcoming openssl-1.0.2l, this is no nolonger needed.
    
      Original commit message:
    
        perlasm/x86_64-xlate.pl: work around problem with hex constants in masm.
    
        Perl, multiple versions, for some reason occasionally takes issue with
        letter b[?] in ox([0-9a-f]+) regex. As result some constants, such as
        0xb1 came out wrong when generating code for MASM. Fixes GH#3241.
    
        Reviewed-by: Rich Salz <rsalz@openssl.org>
        (Merged from openssl/openssl#3385)
    
        (cherry picked from commit c47aea8af1e28e46e1ad5e2e7468b49fec3f4f29)
    
    Refs: openssl/openssl#3241
    Refs: openssl/openssl#3385
    Fixes: nodejs#12691
    shigeki committed May 9, 2017
    Configuration menu
    Copy the full SHA
    5ff8672 View commit details
    Browse the repository at this point in the history
  2. deps: update openssl asm and asm_obsolete files

    Regenerate asm files according to the fix of
    openssl/crypto/perlasm/x86_64-xlate.pl.
    
    Fixes: nodejs#12691
    shigeki committed May 9, 2017
    Configuration menu
    Copy the full SHA
    9dfd409 View commit details
    Browse the repository at this point in the history