RELEASE/v1.6

• Updates for new certify paths, OEAdd, PUDUpdate
• Allows outputting statistical test results
• Allows specifying data file sample sizes when the bits per sample doesn't match the sample size in the collected data

RELEASE/v1.5

ESVTS Updates:

• Several changes around the ITAR flag
  • Removed ITAR from specification, WebClient, Python Client, API calls
• Adds stricter file size checks to WebClient and API. Data files should be exactly 1 million samples, padded to complete bytes
• Fixed error around parsing output of Certify step

RELEASE/v1.4

• Test runs that fail the C++ tool will be better captured and not subject to validation
  • Warning for all WebClient users that if the data files uploaded fail the C++ run there will be no error reported back to the user
• Added better error descriptions to C++ tool when things go wrong
• Added better checks around conditioning component values provided to server
• Added DRBGs to the list of vetted conditioning components according to the updated IG D.K
• GET requests to "entropyAssessments/" have been fixed
• Added Data Collection Attestation documents to WebClient and API as optional supporting documents

RELEASE/v1.3.1

Server:
· All conditioning components now require h_out to be specified
· Fixed bounds on min n_in and other values on conditioning components
· Fixed bounds on bitsPerSample for registration properties
· Removes alphabetSize from registration properties
· Require at least one PUD and EAR for a Certify request
· EIDs are now checked for uniqueness

Clients:
· Matching registration fixes for ESVTS
· Adds reuse option on WebClient (previously would default to reuse restricted to vendor)
· Fixes for Python Client around selecting multiple OEs at once
· Adds Python Client CHANGELOG to help users with future updates

RELEASE/v1.2

· [Known Issue] #24
· Fixes C++ tool outputs, and provides all outputs back to the user for datafiles
· Allows multiple OEs to be registered at once on Server, WebClient and Python client
· Supporting Documentation now requires a specific type to be selected to identify the Entropy Assessment Report and the Public Use Document. Submissions without both documents will be rejected. Includes updates to WebClient and Python client