Versions Compared

Key

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

...

If Guardant API functions are present in the loadable code (for instance, an algorithm which was previously protected by Guardant dongles is transferred into a dongle), then for most of these functions there is an analog in Guardant Code API and porting will be confined to the change of prefix from GrdXXX to GcaXXX or GccaXXX.

FunctionDescription
GcaCrash()
 

GcaExit()Exiting the loadable code
GcaLedOn()Turning LED on
GcaLedOff()Turning LED off
GcaRead()Read EEPROM data, GrdRead() analog
GcaWrite()Write EEPROM data, GrdWrite() analog
GcaPI_Read()Read protected item data, GrdPI_Read() analog
GcaPI_Update()Read protected item data, GrdPI_Update() analog
GcaPI_GetTimeLimit()Receiving the remaining algorithm operating time
GcaPI_GetCounter()Get algorithm counter value, GrdPI_GetCounter() analog
GcaGetTime()Get dongle’s timer state, GrdGetTime() analog. For Guardant Code Time only
GcaGetRTCQuality()Real time clock testing
GcaGetLastError()Receiving the last error code
GccaCryptEx()Data encryption, GrdCryptEx() analog
GccaSign()Generate the digital signature, GrdSign() analog
GccaVerifySign()Verify the digital signature, GrdVerifySign() analog
GccaGenerateKeyPair()Creating key pairs
GccaHash()Calculate hash, GrdHash() analog
GccaGetRandom()Random number generation
GcaSetTimeoutSetting the maximum allowed loadable code operating time
GcaCodeGetInfoRequest information from the loadable code descriptor
GcaCodeRunReal time clock (RTC) testing
See Guardant API help for more detailed description of Guardant Code API internal functions (GrdAPI.chm file).
Info
titleImportant information

Since GSII64 algorithm and its derivatives (HASH64, RAND64, etc.) are not implemented in Guardant Code, you will probably have to rework the existing protection scheme for the use of AES128 algorithms for encryption and SHA256 for hashing. All other capabilities of the previous dongle models are present in Guardant Code.