Bug 1037139 - Installation of spice-gtk-0.33-6.1.x86_64: cannot verify root:root 0755 - not listed in /etc/permissions
Summary: Installation of spice-gtk-0.33-6.1.x86_64: cannot verify root:root 0755 - not...
Status: RESOLVED WONTFIX
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Other (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Dominique Leuenberger
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-02 09:45 UTC by Panagiotis Georgiadis
Modified: 2017-09-20 11:49 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

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 Panagiotis Georgiadis 2017-05-02 09:45:46 UTC 
The installation of `spice-gtk-lang-0.33-6.1.noarch` triggered (as a dependency) the installation of `spice-gtk-0.33-6.1.x86_64`.
Here's is the message that gets displayed:

>  Installing: spice-gtk-0.33-6.1.x86_64 [.......done]
>  Additional rpm output:
>  /usr/bin/spice-client-glib-usb-acl-helper: cannot verify root:root 0755 - not listed in /etc/permissions

Notice that the installation took place in a clean system, which means that the 'spice-gtk-0.33-6.1' cannot verify
the default's machine's security policy. If this is just a false warning that can be ignored, please provide a
message saying so. If this is not possible, then feel free to close this bug-report.
Comment 1 Marcus Meissner 2017-05-03 09:03:40 UTC 
it is a false warning, having it not specified is ok-ish.

a local user can override it locally.
Comment 2 Dominique Leuenberger 2017-09-20 11:49:06 UTC 
(In reply to Marcus Meissner from comment #1)
> it is a false warning, having it not specified is ok-ish.
> 
> a local user can override it locally.

The warning won't disappear until the security of this handler is approved (which in turn probably will take a rewrite/new architecture)

This is still tracked in bug 744251 - marking this one here (about the warning) as WONTFIX