This bug was fixed in the package openvpn - 2.1~rc15-1ubuntu1
---
openvpn (2.1~rc15-1ubuntu1) karmic; urgency=low
* Merge from debian unstable (LP: #372358), remaining changes:
- debian/openvpn.init.d:
- Do not use start-stop-daemon and use /dev/null to avoid blocking
Looks good. I'll upload the merge once alpha2 has been released.
** Changed in: openvpn (Ubuntu)
Status: Confirmed = Fix Committed
** Changed in: openvpn (Ubuntu)
Assignee: (unassigned) = Mathias Gug (mathiaz)
--
Please merge openvpn 2.1~rc15-1 (main) from Debian unstable (main)
@Andres:
You're right, it's technically more correct to have that lsb-base
dependency (with the version), even if in most cases lsb-base is always
around. This delta could be forwarded to Debian.
The idea is to keep the Debian diff as small as possible, which will
allow simpler merges in the
Ok. Following your recommendations. Attaching final diff.
** Attachment added: openvpn_2.1~rc15-1ubuntu1.debdiff
http://launchpadlibrarian.net/27413778/openvpn_2.1%7Erc15-1ubuntu1.debdiff
** Attachment removed: openvpn_2.1~rc15-1ubuntu1.debdiff
** Attachment removed: openvpn.jpg
http://launchpadlibrarian.net/27077204/openvpn.jpg
** Attachment removed: openvpn_2.1~rc15-1ubuntu1.debdiff
http://launchpadlibrarian.net/27121866/openvpn_2.1%7Erc15-1ubuntu1.debdiff
--
Please merge openvpn 2.1~rc15-1 (main) from Debian unstable (main)
Hey Andres, thank you for your work on this !
About testing:
Did you doublecheck that you can still start the password-protected VPNs
manually (after boot) using sudo service openvpn start vpnname and entering
the right password ?
About the changelog entries:
* Do not use start-stop-daemon
Thierry:
- About the testing: Yes I've tested everything you are mentioning and
it works the same way comparing Jaunty openvpn package and the Karmic
openvpn package I have on my ppa.
- Changed those changelog entries.
- Regarding the diff, it shows that difference because in Debian, they
@Thierry
I've tested the configuration according to this howto:
https://help.ubuntu.com/community/OpenVPN. I have just made a change in:
./pkitool --initca to ./pkitool --initca --pass since ./pkitool --server
didn't support the --pass option. Well, after configuring, I updated
openvpn to this
Attaching screenshot.
** Attachment added: openvpn.jpg
http://launchpadlibrarian.net/27077204/openvpn.jpg
--
Please merge openvpn 2.1~rc15-1 (main) from Debian unstable (main)
https://bugs.launchpad.net/bugs/372358
You received this bug notification because you are a member of Ubuntu
Server
@Andres: Yes, I seem to remember it was the chosen behavior. Fail to
start VPN needing user interaction rather than blocking the boot with a
console prompt. Ideally, you would replicate the exact same
configuration in a Jaunty environment and check the behavior there, and
just doublecheck there is
@Thierry
What you mean by password-protected VPN?? Do you mean that I have to
setup a VPN that asks clients for username/password?? Can you point me
out a sample config?
Thanks.
--
Please merge openvpn 2.1~rc15-1 (main) from Debian unstable (main)
https://bugs.launchpad.net/bugs/372358
You
iirc you should be able to test it by setting up a password on your
server key. OpenVPN will ask you for the key password before being able
to use it to set up the VPN. If you use easy-rsa, use pkitool --server
--pass option.
--
Please merge openvpn 2.1~rc15-1 (main) from Debian unstable (main)
@Andres:
About $script_security, yes, we also need it to be passed as an option.
And yes, something similar to what you propose just might take the best
of both worlds : use start-stop-daemon to avoid failure on start when a
PID file is not deleted, and still have our $script_security and boot-
Thanks for the diff. It seems that there is one part of the merge in the
init script that should properly handled:
Debian changed the way openvpn daemons are started:
-# Check to see if it's already started...
-if test -e /var/run/openvpn.$NAME.pid ; then
- log_failure_msg Already
Unsubscribing main sponsors for now.
--
Please merge openvpn 2.1~rc15-1 (main) from Debian unstable (main)
https://bugs.launchpad.net/bugs/372358
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvpn in ubuntu.
--
Ubuntu-server-bugs
Attaching new patch.
** Attachment added: openvpn_2.1~rc15-1ubuntu1.debdiff
http://launchpadlibrarian.net/26729159/openvpn_2.1%7Erc15-1ubuntu1.debdiff
--
Please merge openvpn 2.1~rc15-1 (main) from Debian unstable (main)
https://bugs.launchpad.net/bugs/372358
You received this bug
@Andres:
It's trickier than that. Doing it purely the Debian way will probably restore
bug 280428, where we chose to differ from Debian. Maybe it's possible to use
start-stop-daemon and still pass /dev/null... This would need to be checked
with a password-protected autostarted VPN for example.
Ohh I now understand. What about $script_security???
So, will doing something similar to the following solve this issue?
+start-stop-daemon --start --quiet --oknodo \
+--pidfile /var/run/openvpn.$NAME.pid \
+--exec $DAEMON -- $OPTARGS --writepid /var/run/openvpn.$NAME.pid \
+
** Changed in: openvpn (Ubuntu)
Status: In Progress = Confirmed
** Changed in: openvpn (Ubuntu)
Assignee: Andres E. Rodriguez Lazo (andreserl) = (unassigned)
--
Please merge openvpn 2.1~rc15-1 (main) from Debian unstable (main)
https://bugs.launchpad.net/bugs/372358
You received
Comments:
- Fix unexpected operator on startup is not a remaining change to Debian, as
it was a fix in the add --script-security 2 by default for backwards
compatibility part which was an Ubuntu delta
- Do not use start-stop-daemon and use /dev/null to avoid blocking boot is
a remaining change
Thanks for the suggestions.
How does it looks like now?
** Attachment added: openvpn_2.1~rc15-1ubuntu1.debdiff
http://launchpadlibrarian.net/26397486/openvpn_2.1%7Erc15-1ubuntu1.debdiff
--
Please merge openvpn 2.1~rc15-1 (main) from Debian unstable (main)
** Changed in: openvpn (Ubuntu)
Status: Confirmed = In Progress
--
Please merge openvpn 2.1~rc15-1 (main) from Debian unstable (main)
https://bugs.launchpad.net/bugs/372358
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvpn in
Thanks for taking the time to prepare a merge. Here are a few comments:
- the changelog entry for the merge needs to be expanded to cover the
remaining changes. It will help for the next round of merges.
- have the changes been forwarded to Debian?
--
Please merge openvpn 2.1~rc15-1 (main)
Heya.
1. Attaching new debdiff with fixed changelog. How does it looks now?
2. I've not forward those changes to Debian. I'm not sure how to do that.
Thanks for the suggestions
Cheers,
RoAkSoAx
** Attachment added: openvpn_2.1~rc15-1ubuntu1.debdiff
24 matches
Mail list logo
