Versions Compared

Old Version 5

changes.mady.by.user Richard Cheng

Saved on

compared with

New Version 6

changes.mady.by.user Richard Cheng

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Padding “00” + Version(ex. 00 00 00 01) + Long term private key to 256 bytes data
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000100F5368708933920553B7B9FFB16AEED9C77D5BFD9662AF149A6B9F965B73F0CCA


Calculate SHA-256 for data


BD422E43F804506F002B4E93DD0165F488FC18660F21A0DC7D9B3057E36C504B


Use RSA private key encrypt data
A997961F9A8D1C44F89B46A95045DC51D767032EC645E80FA2DDB528690D28C820A828D44C322586FC0CB91B6FCF48513D7F7E579221A5F089E22FF1CB792070D6237D25198B77E3ECB053D519AB1BAB260B27DD8FD5E95C7A21CDA073D8E6AD928B0AD6F698074A5EDC2A5496C02F6B50DD650D9CC61E0385EAE15CF381EE639073A208A5C3A4ADA935369D689A295CE77BC9372A544492034A857F767854EDDFC922D6497B3905B588333447078F7DE55064EF3EA35E0877505E4107FA49126F26CB0114943267FC8BABB5C90A07AEE359A32A71ABFBCE529BF875501F70E4FE022D14FC43D1AE2BD18F4904962BE1C376658D16F298B6E0DEADA829021A85


Append encrypt data and sha-256 data

A997961F9A8D1C44F89B46A95045DC51D767032EC645E80FA2DDB528690D28C820A828D44C322586FC0CB91B6FCF48513D7F7E579221A5F089E22FF1CB792070D6237D25198B77E3ECB053D519AB1BAB260B27DD8FD5E95C7A21CDA073D8E6AD928B0AD6F698074A5EDC2A5496C02F6B50DD650D9CC61E0385EAE15CF381EE639073A208A5C3A4ADA935369D689A295CE77BC9372A544492034A857F767854EDDFC922D6497B3905B588333447078F7DE55064EF3EA35E0877505E4107FA49126F26CB0114943267FC8BABB5C90A07AEE359A32A71ABFBCE529BF875501F70E4FE022D14FC43D1AE2BD18F4904962BE1C376658D16F298B6E0DEADA829021A85BD422E43F804506F002B4E93DD0165F488FC18660F21A0DC7D9B3057E36C504B

IDG Command

5669564F746563683200C7620120A997961F9A8D1C44F89B46A95045DC51D767032EC645E80FA2DDB528690D28C820A828D44C322586FC0CB91B6FCF48513D7F7E579221A5F089E22FF1CB792070D6237D25198B77E3ECB053D519AB1BAB260B27DD8FD5E95C7A21CDA073D8E6AD928B0AD6F698074A5EDC2A5496C02F6B50DD650D9CC61E0385EAE15CF381EE639073A208A5C3A4ADA935369D689A295CE77BC9372A544492034A857F767854EDDFC922D6497B3905B588333447078F7DE55064EF3EA35E0877505E4107FA49126F26CB0114943267FC8BABB5C90A07AEE359A32A71ABFBCE529BF875501F70E4FE022D14FC43D1AE2BD18F4904962BE1C376658D16F298B6E0DEADA829021A85BD422E43F804506F002B4E93DD0165F488FC18660F21A0DC7D9B3057E36C504B6E7C

Test test-cases2074294809.json with Terminal App case 0.3

  1. Download Terminal configuration file terminal_configs.7z to Android phone, which used to as Terminal.

  2. Click Terminal App → Setting → Click "LOAD" → go to direction where store Terminal configuration file → serch for 0.3.json → clikc OK

    → scroll down, change Merchant ID to 50248994(if need) and check Long term private key, which should be same as the priv we use openssl to read PEM file(Google's or Pronto's) → return to Terminal App → tapping new pass
    → SW 9102.

  3. Change LTPK to Pronto's, Terminal APP → Setting → scroll down to LTPK → click LTPK → "LOAD KEY FROM FILE" → select Pronto' s PEM file → SAVE → tapping new pass → SW 9102.

Suggenstion

To validate customer' s pass via Terminal App is a best way. If Terminal App could read data and get SW 9000, that means VP3300 should get same data.

One more thing should be notice is, test case 0.3 need to do negotiate with pass, so we could read log from Terminal App, and knwo SW of Negotiate is 9500(Authorization failed).

I think this issue do not releate to VPP3300, customer and Google may use Terminal App and pass to read something back successfully first, then set the same configuratioin to VP3300 and read pass.

If Terminal App success but VP3300 fail, then we fix it.