Somehow the environment variable CONFDIR is used to determine the destination of the ipsec.d directory. In case of a tmux session CONFDIR is set to the path containing the tmux configuration (in my case /home/lars/Projekte/sources/tmuxfiles). This results in a sandbox violation: * ACCESS DENIED: mkdir: /home/lars/Projekte/sources/tmuxfiles/ipsec.d mkdir: cannot create directory ‘/home/lars/Projekte/sources/tmuxfiles/ipsec.d’: Permission denied Reproducible: Always Steps to Reproduce: 1. start tmux 2. emerge -av1 net-misc/libreswan Actual Results: * --------------------------- ACCESS VIOLATION SUMMARY --------------------------- * LOG FILE: "/var/log/sandbox/sandbox-30162.log" * VERSION 1.0 FORMAT: F - Function called FORMAT: S - Access Status FORMAT: P - Path as passed to function FORMAT: A - Absolute Path (not canonical) FORMAT: R - Canonical Path FORMAT: C - Command Line F: mkdir S: deny P: ipsec.d A: /home/lars/Projekte/sources/tmuxfiles/ipsec.d R: /home/lars/Projekte/sources/tmuxfiles/ipsec.d C: mkdir -p -m 700 /home/lars/Projekte/sources/tmuxfiles/ipsec.d * -------------------------------------------------------------------------------- The failure only occurs within tmux, not in a normal session.
Created attachment 400990 [details] build.log
Created attachment 400992 [details] environment
My tmux sessions do not have CONFDIR set in the environment. How may I reproduce this behavior?
(In reply to Mike Gilbert from comment #3) > My tmux sessions do not have CONFDIR set in the environment. Yes, you're right. It was my fault. I set the CONFDIR variable myself in my ~/.tmux.conf. I did not expect that this variable is exported. However, it seems like this is the intended behaviour for variables defined in tmux config files.
