Bug 1037644 - mingw-virt-viewer msi should be signed by Red Hat code signing key
Summary: mingw-virt-viewer msi should be signed by Red Hat code signing key
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: mingw-virt-viewer
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ovirt-4.4.0
: 4.4.0
Assignee: Default Assignee for SPICE Bugs
QA Contact: SPICE QE bug list
URL:
Whiteboard:
Depends On: 923837 1524447
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-03 14:29 UTC by David Jaša
Modified: 2019-03-25 17:28 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-25 17:28:06 UTC
oVirt Team: Spice
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description David Jaša 2013-12-03 14:29:34 UTC
Description of problem:
mingw-virt-viewer msi should be signed by Red Hat code signing key. It is currently unsigned.

Version-Release number of selected component (if applicable):
mingw-virt-viewer-0.5.6-15.el6_5

How reproducible:
always

Steps to Reproduce:
1. launch mingw-virt-viewer msi
2.
3.

Actual results:
when prompted by Windows if intallation should be launched, Windows (at least 7, 2008 R2) say that the binary is unsigned and the publisher is unknown

Expected results:
the binary is signed by code signing key so that the publisher is recognized as trusted source by Windows

Additional info:

Comment 1 Marc-Andre Lureau 2013-12-03 14:49:46 UTC
spice-client-msi is currently doing signing of MSI.

doing signing in mingw- would require cross-signing capabilities, adding dep on brew

Comment 2 David Blechter 2013-12-08 21:20:55 UTC
moving to 3.4, the 923837 should be solved first

Comment 3 Marc-Andre Lureau 2014-03-11 23:23:49 UTC
this isn't going to happen in 3.4 either, if bug 923837 isn't fixed.

Comment 4 David Blechter 2014-06-02 17:47:23 UTC
let's hope the depend on bug will be fixed prior to 3.5 development ends

Comment 6 Red Hat Bugzilla Rules Engine 2015-10-20 15:39:37 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a release.

Comment 7 Sandro Bonazzola 2015-10-26 12:35:28 UTC
this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015.
Please review this bug and if not a blocker, please postpone to a later release.
All bugs not postponed on GA release will be automatically re-targeted to

- 3.6.1 if severity >= high
- 4.0 if severity < high

Comment 8 David Blechter 2015-11-23 13:54:27 UTC
This bug depend on the one that is not fixed in brew, moving to rhevm-future

Comment 9 David Blechter 2015-11-23 13:54:44 UTC
This bug depends on the one that is not fixed in brew, moving to rhevm-future

Comment 15 Victor Toso 2018-10-22 11:10:21 UTC
Uri, are this getting fixed with new components in rhel8? I'm not sure how to address this and why it depends on 1524447

Comment 16 Uri Lublin 2018-10-23 09:50:14 UTC
(In reply to Victor Toso from comment #15)
> Uri, are this getting fixed with new components in rhel8? I'm not sure how
> to address this and why it depends on 1524447

First, to make it clear, the MSI binaries that are being shipped are signed (but that's not what this bug is about). We have to do an extra step to sign the MSI binaries.

With regards to this bug - likely we can not fix it yet.
It is not possible to sign the binaries when building with mingw, until bug 1524447 is resolved.

Comment 17 Sandro Bonazzola 2019-01-28 09:40:32 UTC
This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

Comment 19 Sandro Bonazzola 2019-03-12 12:52:29 UTC
4.3.1 has been released, please re-target this bug as soon as possible.


Note You need to log in before you can comment on or make changes to this bug.