Page MenuHomePhabricator

triggers interest-noawait /etc/resolv.conf will probably not work
Closed, ResolvedPublic


I've never used triggers, but it's most interesting. I see a potential issue here.

# Reset back to Whonix defaults
interest-noawait /etc/resolv.conf
interest-noawait /etc/hosts
interest-noawait /etc/hostname

I think you might want to use /etc/resolv.conf.anondist instead. Because the file known to dpkg is
Moving /etc/resolv.conf out of the way and the symlink magic is done by config-package-dev. And I suppose that dpkg uses triggers on files it knows to manage. Probably not on dpkg-diverted files. But I might be wrong about this. I advice to actually test this if you want to make sure this really works.

(Related: T171)


Needs Triage

Event Timeline

Patrick raised the priority of this task from to Normal.
Patrick updated the task description. (Show Details)
Patrick added projects: Whonix, Qubes.

It has been tested and does work.

Those 3 files are managed by qubes.whonix and also have a chattr+i attribute set upon them to prevent Qubes from over-writing them.

I advice to fix this in a later version of Qubes upstream and in the qubes-whonix version.

nrgaway lowered the priority of this task from Normal to Low.Jun 6 2015, 6:19 PM

fixed 'triggers interest-noawait /etc/resolv.conf will probably not work' -