search

GSA / gsa-doc-digital-signature

This tool is deprecated. Please follow these new procedures - https://playbooks.idmanagement.gov/signfedregister/
Other
20 stars 7 forks source link

P7M extension added to output file #32

Open powell-ofr opened 6 years ago

powell-ofr commented 6 years ago

Two different agencies experienced the same previously unseen problem. After signing a DOC file, the signature certificate tests valid but the output filename contains the P7M extension. However, it’s not a double-signed file. If I remove the P7M extension from the output file, it opens normally as a Word file. Unfortunately, it won’t pass our submission portal.

Example are attached; test results below. Note the output file extension:

Word document stored on network folder: Processing file: c:/pki/IN/Test file 1.DOC.P7M Signed by: RANDALL STONE Signer's DN: cn=RANDALL STONE+0.9.2342.19200300.100.1.1=15001000225175,ou=ENRD,ou=Dept of Justice,o=U.S. Government,c=US Verification Status: REV_STATUS_VERIFIED

c:\pki\Out\Test file 1.DOC.P7M was digitally signed Took 11794 milliseconds to process file Test file 1.DOC.P7M

Word document stored on local drive: Processing file: c:/pki/IN/Test 3.doc.p7m Signed by: RANDALL STONE Signer's DN: cn=RANDALL STONE+0.9.2342.19200300.100.1.1=15001000225175,ou=ENRD,ou=Dept of Justice,o=U.S. Government,c=US Verification Status: REV_STATUS_VERIFIED

c:\pki\Out\Test 3.doc was digitally signed Took 12417 milliseconds to process file Test 3.doc.p7m

Two unrelated agencies experienced this problem. The problem started about 3 weeks ago.

Lee Powell OFR

djpackham commented 6 years ago

@powell-ofr - Thanks for submitting. We'd need the logs found in the installation directory in order to troubleshoot this further.

We'll keep this on our radar to see if it becomes a bigger issue.