Bug 407971 - Smb4k is blocked by SELinux, by default
Summary: Smb4k is blocked by SELinux, by default
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 8
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-12-02 18:54 UTC by Paul-Marc Bougharios
Modified: 2007-12-12 22:03 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-12-12 22:03:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
SETroubleshoot log file, created upon trying to browse the samba share (2.11 KB, text/plain)
2007-12-02 18:54 UTC, Paul-Marc Bougharios
no flags Details

Description Paul-Marc Bougharios 2007-12-02 18:54:21 UTC
Description of problem:
Smb4K, SMB/CIFS share browser for KDE, is blocked by default by SELinux.
Upon trying to access a network share, I get:
"SELinux is preventing /usr/bin/net (samba_net_t) "getattr" to socket:[405714]
(unconfined_t)."
I'm attaching the SETroubleshoot log file


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Open Smb4K
2. Wait for it to scan the network
3. Try to browse a network share
  
Actual results:
Nothing appears in the browser, or error "mount error 1 = Operation not
permitted" appears.

Expected results:
Open the browsed share.

Comment 1 Paul-Marc Bougharios 2007-12-02 18:54:21 UTC
Created attachment 275091 [details]
SETroubleshoot log file, created upon trying to browse the samba share

Comment 2 Daniel Walsh 2007-12-03 01:41:53 UTC
Not sure what is going on here.

If you put the machine in permissive mode does everything work?

Comment 3 Paul-Marc Bougharios 2007-12-10 21:53:20 UTC
I put the permissive mode.
I'm still unable to open any samba share, but no AVC denials were recorded... 
I got an error stating that "mount.cifs" was returning error code 1.
I don't think it's SELinux no more...
I think I should work it over with mount.cifs...
Deep thanks for the prompt response!


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