Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 26 Next »


Software Memebers

NameComment
On board: 2013.07
On board: 2018.09

Software Application Map

ItemDateComment

 

<V02>

Software Job List, 2019


Software List

Reader Type = Desktop / PC Environment

Application PeriodName of Software Tool / Lib / SDKPages / DL Info
Hardware EMI / CE / Others Lab Approved Analog Device

TS For Hardware

SW_Hardware_Utilities
Customer Supports

Software for Customer Supports

  • Internal Customers.

EE/ ME/ SQA/ FW.

  • Company Customers
SW_Customer_Supports
EMV Contactless L1 Test / Debug / ApproveContactless Level 1 SDK for LabSW_EMV L1 SDK
EMV Contactless L2 Test / Debug / ApproveContactless Level 2 SDK for Lab

001_CL EMV L2 SDK

/wiki/spaces/KEY/pages/64096480

EMV Contact L1 Test / Debug / ApproveContact Level 1 SDKSW_EMV L1 SDK
EMV Contact L2 Test / Debug / ApproveContact Level 2 SDK002_CT EMV L2 SDK
Test Software, Production / QC purposeTest Software Root , TS### (ex: TS146)Test Software Root
Firmware Download Tool
  • NEO Download App - eat image .txt file
  • NEO Image Gen Txt Tool - Convert .bin to .txt
Software Developer / Programmer PageTaiwan Software Internal Development Forum / GardenSW_Developer / Programmer Page

SQA Software Approval Tool.

ToolVersion / DL LinkComments

MD5 and SHA Checksum Utility


Software Release Approval Flowchart / Steps


Software Code Signing Note

 goofy.liu

ItemComment

JIRA: CS-3120

CS-3120 - Getting issue details... STATUS

 goofy.liu Shawn Li

Here we just asked for Shanghai Software Team's Help...

-----------------------------------

C:\SignatureTools\certs

C:\SignatureTools\NEO1x_App

C:\SignatureTools\SignToolForWin10

這3個 path 就先不去變動..

JIRA: TS22008
TS-22008 - Getting issue details... STATUS

 goofy.liu

Shanghai Software Team Support Digit-Cert Code Sign Tool

+ private key usb dongo stick

+ private key operate software SafeNetAuthenticationClient-x32-x64


  1. zipped folder image , which is to make code-sign environment. i.e. "NEO1x_APP"

NEO1x_App.zip

2. Usage.

2.1 Brief

  A.cert =  3rd public-key embedded valid issuer certificate.

  B.NEO1x_APP = code-sign operation path. contains batch file to make

                         B.1 unsigned folder = put native software here. they might be.exe, .msi, .dll, and .cab file type.

                         B.2 batch files = the batch file to make

  C.SignToolFowWin10 = contains major make tool "signtool.exe" which will be invoked by batch file w/ proper arguments.

3.

  step 01

  step 02

  step 03.


 goofy.liu

Here are some examples.

Type 1 . EV Code Signing, recommended

https://www.websecurity.digicert.com/zh/tw/code-signing

https://www.identrust.com/wizard/form3

Price : $349~ $499 USD /year (reference).

--------------

Type 2. OV Code Signing

https://www.ksoftware.net/code-signing-certificates/?gclid=EAIaIQobChMI-vbgzriD6wIVmLaWCh2tDABaEAAYASAAEgJRSfD_BwE

Price : $84 USD/yr

------------

Comparison OV & EV Code Signing rules.

https://support.ksoftware.net/support/solutions/articles/232500-what-are-the-differences-between-ov-and-ev-level-code-signing-certificates-



Self Code Signing Steps


Bushound(Bh.) Information

ItemComment

Objectives:

   1. Logging RS232/USB send/receive frame data for debugging analysis.

   2. Good PC driver-level instance information to understand helpful features.

   3.Win 10/8/7 compatible, Current Bh. V6.1

License

Config Bh.

Example

Alternative URL

/wiki/spaces/EN/pages/67249962
  • No labels