List view

• Full support for JC3.0.5 algorithms

  Create cap supporting all algorithms up to 3.0.5 (has to be separate cap to allow also for older cards)

  No due date
  0% complete0 open0 closed

• Improvement of performance results presentation

  Due by July 30, 2015

  •7/8 issues closed
  87% complete1 open7 closed

• Interactive database of all results

  - user can easily upload measured results (instead of sending via email) - user can obtain similarity ratio for measured card and cards already in database

  Due by October 30, 2015

  •2/3 issues closed
  66% complete1 open2 closed

• Basic performance tests

  - Measurement of time required to perform operation for most of relevant classes, algorithms and methods. Database of time measurements and presentation in graphs. E.g., User shuld be able to measure (or find in database) answer to: How long will it take to encrypt 256B of data by ALG_AES_BLOCK_128_CBC_NOPAD algorithm?

  Due by June 29, 2015

  •26/27 issues closed
  96% complete1 open26 closed

• New release - one apdu per single test

  - one apdu per tested algorithm and configuration - JC 2.1.2, 2.2.1, 2.2.2 cap files - actualize table with results

  Due by November 20, 2014
  0% complete0 open0 closed