Though the right solution is to do some /etc/default/openvpn configuration (see related answer), it might be a good idea to preserve hardy's behavior in that case.
This difference in behavior was introduced when we merged the fix for the following Debian bug : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=454371
In hardy, VPNs needing some password to start would just fail to autostart on boot.
Though the right solution is to do some /etc/default/ openvpn configuration (see related answer), it might be a good idea to preserve hardy's behavior in that case.
This difference in behavior was introduced when we merged the fix for the following Debian bug : bugs.debian. org/cgi- bin/bugreport. cgi?bug= 454371
http://
In hardy, VPNs needing some password to start would just fail to autostart on boot.