sharpbracket/redshift

Apparmor profile blocks config file if XDG_CONFIG_HOME is set

Open

#708 opened on Feb 19, 2019

View on GitHub
 (5 comments) (3 reactions) (0 assignees)C (429 forks)auto 404
buggood first issue

Repository metrics

Stars
 (6,156 stars)
PR merge metrics
 (PR metrics pending)

Description

Describe the bug With XDG_CONFIG_HOME set to something other than $HOME/.config, the supplied apparmor profile DENIES the file access to the redshift.conf file. Adding the line: owner @{XDG_CONFIG_HOME}/redshift/redshift.conf r, to the usr.bin.redshift file fixes this when running redshift from the command line. It does not fix it when running redshift-gtk however.

To Reproduce Steps to reproduce the behavior:

  1. Set XDG_CONFIG_HOME to something other than ~/.config
  2. Create $XDG_CONFIG_HOME/redshift/redshift.conf
  3. Make sure apparmor is running
  4. Start redshift

Expected behavior Parameters specified in $XDG_CONFIG_HOME/redshift/redshift.conf should be used rather than default values (or those in ~/.config/redshift/redshift.conf).

Error output/logs/screenshots In /var/log/audit/audit.log the error is: type=AVC msg=audit(1550535771.076:213): apparmor="DENIED" operation="open" profile="/usr/bin/redshift" name="/home/username/.config.tumbleweed/redshift/redshift.conf" pid=5793 comm="redshift" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000

Software versions (please complete the following information):

  • OS: Linux
  • Redshift version: 1.12
  • Distribution: openSUSE Tumbleweed
  • Redshift installed from: using zypper and also built from source

Contributor guide