Description of problem: I have dnssec-triggerd.service up and running and try to set up vpnc on my F20 box, I get an error like: /etc/vpnc/vpnc-script: line 353: /etc/resolv.conf: Permission denied When seeking for what the script is trying to do, I see: 353: echo "$NEW_RESOLVCONF" > /etc/resolv.conf ...which is not surprise, because the file is not read-able intentionally [1] Please, see more in [1]. Version-Release number of selected component (if applicable): vpnc-0.5.3-19.svn457.fc20.x86_64 NetworkManager-0.9.9.0-26.git20131003.fc20.x86_64 dnssec-trigger-0.11-19.fc20.x86_64 How reproducible: every-time Steps to Reproduce: 1. start dnssec-trigger 2. be on wifi connection (not sure if important) 3. start vpnc Actual results: no resolve.conf updated Expected results: resolve.conf is updated [1] https://bugzilla.redhat.com/show_bug.cgi?id=1061370#c6
I just pushed a new vpnc version to updates-testing (for Fedora 20 and 21). I think your issue is still present there but maybe you can confirm that? I assume it'll be much easier for you to reproduce the problem.
This looks like an upstream bug/missing feature to me. The good news is that vpnc-script was split of from the main vpnc project and the new maintainer (David Woodhouse) should be much more easy to work with (http://git.infradead.org/users/dwmw2/vpnc-scripts.git/). If your issue is still present I suggest you report the bug to him as I (and I assume also no other Fedora vpnc maintainer) don't have the time to develop vpnc(-script) fixes on our own. If the vpnc-script contains a fix for your issue, feel free to ping us. Personally I'd be happy to include such a patch once it has been accepted upstream.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.