3. User’s guide to using the inoQulate solution

The inoQulate solution supports PDF Timestamping (RFC 3161) and code signing.

3.1. Batch PDF inoQulation

1. Log in to the SFTP server in the VM with an SFTP client program of your choice to drop PDF files for inoQulation.

   Use the following parameters:

   Parameter	Value
   Server	The FQDN as configured in Set up a domain name for your VM
   Port	2222
   Username	sftp
   Authentication Method	SSH keypair, with the private key from Prepare an SSH keypair for users.

   For example, using the sftp command line program,

   sftp -P 2222 sftp@inoqulate.example.com
   

2. Upload your PDF files in the toInoQulate directory.

3. Observe that your inoQulated files appear in the inoQulated directory after one hour.

4. Observe that new proof files are generated in the proofs directory. These are the zero-knowledge proofs generated by pQCee’s SPP technology.

5. Observe that:

   1. A new summary report of the latest run has been created in the report directory.

   2. The original documents have been moved to the done directory.

   3. Any documents that failed inoQulation are moved to the error directory.

6. Copy out the files in the inoQulated, proofs and report directories and store them securely.

7. Check if the error directory contains any files. If there are, contact the administrator to check the service logs.

8. Remove the files from inoQulated, error and done directories to avoid the service failing because a file with the same name already exists.

9. Logout of the SFTP server.

3.2. Code signing

1. Access the code signing web portal with the domain configured in Set up a domain name for your VM.

   

2. Fill in the Worker Name (click copy to clipboard on the right):

   SPP-ECDSA-CodeSigner
   

3. Click Choose File and select the code binary you wish to sign.

4. Leave the process type at Sign Document.

5. Click Submit. A p7s file is downloaded.

6. Store the p7s file securely.