Prompted for VPN (openvpn) user info at boot-up

Bug #280428 reported by Piraja
0
Affects Status Importance Assigned to Milestone
openvpn (Ubuntu)
Fix Released
Medium
Thierry Carrez

Bug Description

After upgrading to Intrepid Ibex I have been prompted at bootup for VPN username and password. This is confusing, since it did not happen with Hardy and I do not want this to happen — it serves no purpose for me and is an inconvenience also for other users of the laptop. All I want to do is launch OpenVPN whenever I need to, during the GUI session and not before logging in. I am reporting this as a bug in Intrepid because this did not happen with Hardy.

Some more info:

http://ubuntuforums.org/showthread.php?t=919715
http://ubuntuforums.org/showthread.php?p=5931147

Related branches

Revision history for this message
Piraja (piraja-deactivatedaccount) wrote :

Indeed, this might be the case: "the reporter is confused, and an explanation is needed." Thanks in advance!

Changed in openvpn:
status: New → Invalid
Revision history for this message
Thierry Carrez (ttx) wrote :

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.

Revision history for this message
Thierry Carrez (ttx) wrote :

This should probably be considered as a bug.

Changed in openvpn:
assignee: nobody → tcarrez
importance: Undecided → Medium
status: Invalid → Confirmed
Revision history for this message
Piraja (piraja-deactivatedaccount) wrote :

I agree, and I realized that the problem persists for users upgrading to Intrepid and using OpenVPN (I mean, the behaviour has not been changed yet): I upgraded from Hardy to Intrepid on another machine and had to remove OpenVPN from the autostarted-at-boot apps list. I also realized, while still using Hardy, that VPN autostart authentication at boot-up just silently fails (and this might be a better policy, from an average user's perspective, I believe).

Revision history for this message
Thierry Carrez (ttx) wrote :

Proposed fix
Also includes a fix for VPNs always reported as starting [ OK ] (log_end_msg sent too early)

openvpn (2.1~rc11-1ubuntu2) intrepid; urgency=low

  * debian/openvpn.init.d:
    - Revert fix from #454371 that was merged at 2.1~rc7-4 to prevent
      openvpn prompts from blocking the boot (LP: #280428)
    - Fix VPNs always reported started [ OK ]

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package openvpn - 2.1~rc11-1ubuntu2

---------------
openvpn (2.1~rc11-1ubuntu2) intrepid; urgency=low

  * debian/openvpn.init.d:
    - Revert fix from #454371 that was merged at 2.1~rc7-4 to prevent
      openvpn prompts from blocking the boot (LP: #280428)
    - Fix VPNs always reported started [ OK ]

 -- Thierry Carrez <email address hidden> Wed, 15 Oct 2008 17:12:54 +0200

Changed in openvpn:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.