|
Bug ID
|
6791982
|
|
Synopsis
|
hal.conf policy flaws exposed by DBus 1.2.8
|
|
State
|
10-Fix Delivered (Fix available in build)
|
|
Category:Subcategory
|
utility:hal
|
|
Keywords
|
|
|
Responsible Engineer
|
Artem Kachitchkin
|
|
Reported Against
|
snv_105
, snv_106
|
|
Duplicate Of
|
|
|
Introduced In
|
solaris_nevada
|
|
Commit to Fix
|
snv_107
|
|
Fixed In
|
snv_107
|
|
Release Fixed
|
solaris_nevada(snv_107)
|
|
Related Bugs
|
6794539
,
6795120
,
6795511
|
|
Submit Date
|
9-January-2009
|
|
Last Update Date
|
28-January-2009
|
|
Description
|
solaris_nevada_105 sparc and x86
osol_0904_b105 x86
Logging into Gnome destop (nevada and osol) or logging into command line session ( nevada).
On typing eject the following error is reported:-
# eject
eject of cdrom /dev/dsk/c0t0d0s2 failed: A security policy in place prevents this sender from sending this message to this recipient, see message bus configu
ration file (rejected message had interface "org.freedesktop.Hal.Device.Storage" member "Eject" error name "(unset)" destination "org.freedesktop.Hal")
The problem occurs for ordinary user and root user.
|
|
Work Around
|
Edit /etc/dbus-1/system.d/hal.conf:
add the following line to the <policy context="default"> section:
<allow send_interface="org.freedesktop.Hal.Device.Storage"/>
plus afterwards:
svcadm restart svc:/system/dbus:default
(interestingly svcadm refresh does not pull the workaround in...)
|
|
Comments
|
N/A
|