Bug 716133

Summary: Get following error using Google Chrome
Product: [Fedora] Fedora Reporter: Jeff Kittle <jkittle>
Component: selinux-policyAssignee: Orphan Owner <extras-orphan>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 14CC: chkr, dominick.grift, dwalsh, extras-orphan, mgrepl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-27 06:06:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jeff Kittle 2011-06-23 16:21:44 UTC 
Description of problem:

SELinux is preventing /opt/google/chrome/chrome from read access on the file /jeff/.config/google-chrome/Dictionaries/en-US-2-1.bdic.

*****  Plugin catchall_labels (83.8 confidence) suggests  ********************

If you want to allow chrome to have read access on the en-US-2-1.bdic file
Then you need to change the label on /jeff/.config/google-chrome/Dictionaries/en-US-2-1.bdic
Do
# semanage fcontext -a -t FILE_TYPE '/jeff/.config/google-chrome/Dictionaries/en-US-2-1.bdic'
where FILE_TYPE is one of the following: cgroup_t, chrome_sandbox_exec_t, bin_t, staff_usertype, abrt_var_run_t, usr_t, xguest_usertype, locale_t, user_fonts_t, user_tmpfs_t, sysctl_crypto_t, etc_t, fonts_t, proc_t, sysfs_t, fonts_cache_t, config_home_t, chrome_sandbox_tmpfs_t, user_fonts_cache_t, user_fonts_config_t, abrt_t, lib_t, xserver_tmpfs_t, iceauth_home_t, xauth_home_t, afs_cache_t, abrt_helper_exec_t, ld_so_t, xdm_tmp_t, user_home_type, textrel_shlib_t, user_cron_spool_t, rpm_script_tmp_t, chrome_sandbox_tmp_t, sysadm_usertype, unconfined_usertype, gnome_home_type, xdm_var_run_t, chrome_sandbox_t, staff_execmem_t, user_execmem_t, ld_so_cache_t, sysctl_kernel_t, execmem_exec_t, unconfined_execmem_t, user_usertype.
Then execute:



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

12.0.742.100


How reproducible:

Browse some web pages

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Daniel Walsh 2011-06-23 20:35:32 UTC 
Jeff is your user directory installed in /jeff?
Comment 2 Jeff Kittle 2011-06-24 01:42:28 UTC 
Daniel

/jeff is a Linux filesystem. This problem happened once before and I followed the instructions provided in the security alert on how to fix it and that seemed to work. Now, since I updated the Chrome software through the standard update process, even the recommended fix doesn't work.
Comment 3 Daniel Walsh 2011-06-24 12:28:04 UTC 
The problem is /jeff is a homedir and needs to be labeled as such. If you changed it to be mounted under /home and ran restorecon, you should not have a problem.

Or you could add an equivalency.

# semanage fcontext -a -e /home/jeff /jeff

Which would tell the system to label everthing under /jeff as if it was under /home/jeff

Then run 
# restorecon -R -v /jeff