Bug 696244 - Missing digital signature
Summary: Missing digital signature
Status: RESOLVED FIXED
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: Printer Driver (show other bugs)
Version: master
Hardware: PC Windows 7
: P4 minor
Assignee: Default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-05 23:07 UTC by Tommy Gjerding
Modified: 2015-10-23 02:43 UTC (History)
1 user (show)

See Also:
Customer:
Word Size: ---

Attachments
ErrorMessage when installing printer (7.97 KB, image/png)
2015-10-05 23:07 UTC, Tommy Gjerding 		Details
Valide .inf file (1.36 KB, text/plain)
2015-10-23 02:43 UTC, caqikuffimm-4637 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tommy Gjerding 2015-10-05 23:07:32 UTC 
Created attachment 11952 [details]
ErrorMessage when installing printer

I previously filed a bug for version 9.15 (Bug 696177), that I was not able to install the printer on Windows Server 2012, due to missing signature.

I was advised to wait for release of GS9.18...

GS9.18 has been downloaded, but I'm still missing the signature, when installing from "E:\Program Files\gs\gs9.18\lib" ;-(

What can I do to install printer properly
Comment 1 Ken Sharp 2015-10-06 00:17:19 UTC 
(In reply to Tommy Gjerding from comment #0)

> I was advised to wait for release of GS9.18...
> 
> GS9.18 has been downloaded, but I'm still missing the signature, when
> installing from "E:\Program Files\gs\gs9.18\lib" ;-(

Check the installation directory, do you have a ghostpdf.cat file ? If so then that is your signature.

 
> What can I do to install printer properly

You have to install from the control panel, you cannot right-click and install or double-click the .inf file.
Comment 2 caqikuffimm-4637 2015-10-22 01:21:45 UTC 
The ghostpdf.cat exist but it's sound like the sha1 for ghostpdf.inf is bad.

In cat file, it's B2AC12AD6CA976C9A6D84E8365D8D5E8A3CA8D59, but the real sha1 for ghostpdf.inf is not the same : 380140C3C235E02C74D31AB095C64389A9109D95.
Comment 3 Tommy Gjerding 2015-10-22 01:28:02 UTC 
OK. Do I have any option to modify/update the sha value in cat-file?
Or will a new be provided from download-site?
Comment 4 Ken Sharp 2015-10-22 01:31:12 UTC 
(In reply to Tommy Gjerding from comment #3)
> OK. Do I have any option to modify/update the sha value in cat-file?

No

> Or will a new be provided from download-site?

No. Any changes will be reflected in the next release, or in our Git repository.
Comment 5 Tommy Gjerding 2015-10-22 01:39:52 UTC 
And time frame for next release??
Will that be like three to sex months ;-(
Comment 6 Ken Sharp 2015-10-22 01:51:57 UTC 
(In reply to Tommy Gjerding from comment #5)
> And time frame for next release??
> Will that be like three to sex months ;-(

We do releases at 6 monthly intervals, yes.

The problem turns out to be that our release process involves copying files to a Unix server, which means that the line endings in text files are altered.

This has been fixed in commit c46f8651e6bea69b76f84dd58568c18fc73ade7d and should mean the next release has this problem resolved.

You can try running the .inf file through unix2dos which might work for you.
Comment 7 caqikuffimm-4637 2015-10-23 02:43:47 UTC 
Created attachment 12013 [details]
Valide .inf file

SHA1 : B2AC12AD6CA976C9A6D84E8365D8D5E8A3CA8D59