Electronic digital signature of documents.

Electronic digital signature of documents. Electronic digital signature of documents based on JAR archives. We use ported JDK programs: KeyTool and JarSigner. Since JarSigner does not check absence of files, we necessarily enter CFL file with full list of files into JAR archive, which is an information file of electronic document. This file describes all the details of the document: designation; name; type of document; number of changes; name of signatories and what the signature is for; single date of signature; number of notification, etc. (which was missing for non-paper documents: PCB; firmware; programs, etc.) I ported KeyTool and JarSigner into windows applications to work correctly with UNICODE. You don't have to pay for certificates anymore - create your own ATTENTION CENTER and sign your certificates. There is no time limit for certificates - create them for as long as you want, even for 100 years. Generate certificates and enter signing data into KeyToolW. Because keytool creates certificates with 866 encoding. JarSignerW has introduced a procedure for signing JAR archives. JarSignerW doesn't reset options. Example: start JarSignerW; enter -verify and press RUN+; press LOAD - enter file for checking; press RUN+ - check; enter -verbose and press RUN+; enter -certs and press RUN+; LOAD - enter file and check RUN+.