none
Signature authentication in MS Developer Center does not work RRS feed

  • Question

  • Good morning
    In the face of the need to register our company's certificate (EV Codesign) in MS Developer Center, I tried to register but it did not work properly and I left a question.

    The web page where the problem occurred is below.

    https://developer.microsoft.com/ko-kr/dashboard/Registration/Hardware?step=SignUpload

    We have registered with the following process.

    1. I have downloaded a signable file. The file name is "SignableFile.bin".
    2. I downloaded the signing tool, completed the installation, and found the signing tool, signtool.exe.
    3. Code signing is in progress.
    - signtool.exe sign / as / fd SHA256 / tr http://sha256timestamp.ws.symantec.com/sha256/timestamp/d "PENTA SECURITY SYSTEMS INC." / V C: \ Users \ Thanatos \ Downloads \ SignableFile.bin
    - The result is 'Success' as shown below.
    The following certificate was selected:
        Issued to: PENTA SECURITY SYSTEMS INC.
        Issued by: Symantec Class 3 Extended Validation Code Signing CA - G2
        Expires: Sat Apr 07 08:59:59 2018
        SHA1 hash: 8DA4B87C94150A44990BD108A8B97EE609D6DD7A

    Done Adding Additional Store
    Successfully signed: C: \ Users \ Thanatos \ Downloads \ SignableFile.bin

    Number of files successfully Signed: 1
    Number of warnings: 0
    Number of errors: 0
    4. When I tried to verify, 'Success' message was also output.
    Signtool.exe verify / pa / v C: \ Users \ Thanatos \ Downloads \ SignableFile.bin

    Verifying: C: \ Users \ Thanatos \ Downloads \ SignableFile.bin
    Signature Index: 0 (Primary Signature)
    Hash of file (sha256): 2C271F63F53F02510A4DB4F7A7E628E141A3060AF8ABB53284F1F43CB96E2220

    Signing Certificate Chain:
        Issued to: VeriSign Class 3 Public Primary Certification Authority - G5
        Issued by: VeriSign Class 3 Public Primary Certification Authority - G5
        Expires: Thu Jul 17 08:59:59 2036
        SHA1 hash: 4EB6D578499B1CCF5F581EAD56BE3D9B6744A5E5

            Issued to: Symantec Class 3 Extended Validation Code Signing CA - G2
            Issued by: VeriSign Class 3 Public Primary Certification Authority - G5
            Expires: Mon Mar 04 08:59:59 2024
            SHA1 hash: 5B8F88C80A73D35F76CD412A9E74E916594DFA67

                Issued to: PENTA SECURITY SYSTEMS INC.
                Issued by: Symantec Class 3 Extended Validation Code Signing CA - G2
                Expires: Sat Apr 07 08:59:59 2018
                SHA1 hash: 8DA4B87C94150A44990BD108A8B97EE609D6DD7A

    The signature is timestamped: Tue Apr 18 20:18:55 2017
    Timestamp Verified by:
        Issued to: VeriSign Universal Root Certification Authority
        Issued by: VeriSign Universal Root Certification Authority
        Expires: Wed Dec 02 08:59:59 2037
        SHA1 hash: 3679CA35668772304D30A5FB873B0FA77BB70D54

            Issued to: Symantec SHA256 TimeStampingce
            Issued by: VeriSign Universal Root Certification Authority
            Expires: Sun Jan 12 08:59:59 2031
            SHA1 hash: 6FC9EDB5E00AB64151C1CDFCAC74AD2C7B7E3BE4

                Issued to: Symantec SHA256 TimeStamping Signer - G2
                Issued by: Symantec SHA256 TimeStampingce
                Expires: Sun Apr 02 08:59:59 2028
                SHA1 hash: 625AEC3AE4EDA1D169C4EE909E85B3BBC61076D3


    Successfully verified: C: \ Users \ Thanatos \ Downloads \ SignableFile.bin

    Number of files successfully Verified: 1
    Number of warnings: 0
    Number of errors: 0

    5. When you finally upload the signed file, a message similar to the one below will be displayed.

    There was a problem processing the uploaded file. Make sure the file you sign and upload is the same as the file you downloaded.
    Correlation ID 5b3c3172-fa61-4f2e-bb77-2e7570d28593, sDqhKfDSY0 + kGADd.1.


    Thank you for your help.

    • Moved by Mattew Wu Wednesday, April 19, 2017 9:59 AM hardware issue
    Wednesday, April 19, 2017 12:52 AM

All replies