Bug 35849 – Rebuild gplpv driver with new signing cert (old certificate has expired)

Bug 35849 - Rebuild gplpv driver with new signing cert (old certificate has expired)


Summary:	Rebuild gplpv driver with new signing cert (old certificate has expired)

Status:	CLOSED FIXED

Product:	UCS
Classification:	Unclassified
Component:	Virtualization - Xen
Version:	UCS 3.2
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 3.2-3-errata
Assigned To:	Felix Botner
QA Contact:	Erik Damrose

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-09-09 14:36 CEST by Felix Botner
Modified:	2014-11-07 12:30 CET (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
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 Felix Botner

2014-09-09 14:36:58 CEST

We need to rebuild the GPLPV driver (version 0.9.372) with the new signing certificate. The old one has expired.

Comment 1 Felix Botner

2014-09-12 12:38:00 CEST

Rebuild version 372 with the new certifiacte (valid until 10.10.2017)

YAML: 2014-09-12-univention-xen-gplpv.yaml

Comment 2 Erik Damrose

2014-09-16 15:10:26 CEST

Reopen:
As discussed, somehow the new certificates seem not to be made for signing driver software. System times are correct, but windows refuses to install the drivers, claiming it can not verify the signature (tested with Win 7).

Everything looks fine and the certificate chain is valid, the same certificate chain is used. A small difference i spotted is the certificate requester is missing "OU=Digital ID Class 3 - Microsoft Software Validation V2" in the new certificate.

Comment 3 Erik Damrose

2014-09-17 12:43:08 CEST

Fresh install of the newly signed drivers works fine. Only the update case is affected by the invalid signature message.

Comment 4 Felix Botner

2014-09-18 09:23:09 CEST

OK, rebuild version 372 with the new certificate and increased the gplpv BUILD_NUMBER to 373 to make that update work (seems that during update with the same version number the driver files are not really updated).

Comment 5 Erik Damrose

2014-09-18 13:16:55 CEST

OK: Install and update on 32 and 64 bit
OK: Certificate warning is gone, new signing is valid until 10.10.2017
I updated the yaml file to point out that the driver version was raised.

Verified

Comment 6 Janek Walkenhorst

2014-11-07 12:30:09 CET

http://errata.univention.de/ucs/3.2/226.html