Mini CA (button New Key) can be used for the certificate creation according to PKCS#10 requests. The key for PKCS#10 request can be generated in the HW module like HSM or smart cards. 

Mini CA (New Key Button) can be used for cross-certificate creation.

Trust in CMS validaton is according to TrustedList.p7m from Trust tab. Certification path is build according to certificates from the signature and certificates form the Trust tab of Lock It.

 Utility tab can be used for the hash computation and comparison. 

New OIDs with description can be added to the configuration LockIt.ini file. The LockIt.ini file also contains the certificates form Trust and the trustlist.p7m 

CMS: LockIt is now able to add the archive time-stamp V2, Update Validation data to the latest archive time-stamp. CMS, XML and PDF AdES: The signing time can be changed in the LockIt application. Signer can include the signing location and define: Proof Of Origin ... Approval. CMS: The signed...

Lock It Signature Creation is according to NSA Qualified Electronic Signature profile for interoperability No.: 917/2011/IBEP/OEP-001 For the signature creation and validation there are used the following CAdES attributes where the following conditions must be met: The RFC 5652 Cryptographic...

The interface language from the translation.zip file can be changed directly from the application menu. 

Certification path is created according to information from Authority Information Access. Issuer certificate: id-ad-caIssuers OBJECT IDENTIFIER ::= { id-ad 2 } OCSP:  id-ad-ocsp OBJECT IDENTIFIER ::= { id-ad 1 }.  CRL: HTTP CRL Distribution Points.  

The application Lock It can be used in the command line.  Usage: LockIt.exe [operation] outputSignFile [-i input1 input2 ... inputX] Where possible operations are:     -s : sign input1..X files or outputSignFile (wildcards * ? and directory allowed) and save the signture to ...