Your message dated Thu, 26 Oct 2023 13:39:43 +0200 with message-id <ZTpP/[email protected]> and subject line Re: Bug#1054541: privoxy: Using custom configuration fails with EACCES at openat syscall has caused the Debian Bug report #1054541, regarding privoxy: Using custom configuration fails with EACCES at openat syscall to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1054541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054541 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: privoxy Version: 3.0.34-3 Severity: important Dear Maintainer, What led up to the situation? The final arg for `privoxy` is the path (relative or absolute) of the configuration file. Specifying anything other than files under /etc/privoxy fails with "Fatal error: can't open configuration file" * What exactly did you do (or not do) that was effective (or ineffective)? `privoxy --no-daemon config` fails `cp config /tmp; privoxy --no-daemon /tmp/config` fails The above with `sudo` likewise fails. `cat config | privoxy --no-daemon /proc/self/fd/0` works `privoxy --no-daemon /etc/ld.so.conf` gives (obviously) a "Ignoring unrecognized directive" warning and fails at binding to the default port, because the system copy is running, but no EACCES error. `sudo cp config /etc/privoxy/jc.conf; privoxy --no-daemon /etc/privoxy/jc.conf` works * What was the outcome of this action? As above. My best workaround so far is using /proc/self/fd/0 * What outcome did you expect instead? I'd expect it to work with a file protected 644 in the current working directory. -- System Information: Debian Release: 12.1 APT prefers stable APT policy: (700, 'stable'), (650, 'oldstable'), (600, 'testing'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'oldstable-updates'), (500, 'oldstable-security') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.19.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages privoxy depends on: ii adduser 3.134 ii debconf [debconf-2.0] 1.5.82 ii init-system-helpers 1.65.2 ii libbrotli1 1.0.9-2+b6 ii libc6 2.36-9+deb12u3 ii libmbedcrypto7 2.28.3-1 ii libmbedtls14 2.28.3-1 ii libmbedx509-1 2.28.3-1 ii libpcre2-8-0 10.42-1 ii logrotate 3.21.0-1 ii ucf 3.0043+nmu1 ii zlib1g 1:1.2.13.dfsg-1 Versions of packages privoxy recommends: ii doc-base 0.11.1 Versions of packages privoxy suggests: ii apparmor 3.0.8-3 -- debconf information: privoxy/listen-address: 127.0.0.1:8118 [::1]:8118
--- End Message ---
--- Begin Message ---Hi John! On Di, 24 Okt 2023, John Comeau wrote: > Package: privoxy > Version: 3.0.34-3 > Severity: important > The final arg for `privoxy` is the path (relative or absolute) of the > configuration file. Specifying anything other than files under > /etc/privoxy fails with "Fatal error: can't open configuration file" On Mi, 25 Okt 2023, John Comeau wrote: > Fixed by: > > # ln -s /etc/apparmor.d/usr.sbin.privoxy /etc/apparmor.d/disable/ > # apparmor_parser -R /etc/apparmor.d/disable/usr.sbin.privoxy > > Sorry for the spurious report. I didn't remember about apparmor, only > noticed it when bugreport pointed it out. I know this problem very good, trapped into this myself. apparmor-notify makes it easier to notice such issues. But since it's the intended behavior of apparmor, I close your bug report here. As a workaround you can - disable apparmor (for privoxy) - place the config file in /etc/privoxy - copy /usr/sbin/privoxy So I close this bug report now. Greetings Roland
--- End Message ---
