add option to force sending empty Domain

Bug #1197313 reported by Andrey Bondarenko
34
This bug affects 6 people
Affects Status Importance Assigned to Milestone
network-manager-vpnc
Confirmed
Wishlist
network-manager-vpnc (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

VPN server in my organization uses empty Domain but requires it on authentication. VPNC plugin currently does not store or send Domain if it is empty (tested versions 0.9.6, 0.9.8.2). This makes impossible to establish vpnc connection with NetworkManager while starting vpnc from command line with empty domain works.

Please add an option to force sending empty Domain.

Changed in network-manager-vpnc:
importance: Unknown → Wishlist
status: Unknown → New
Revision history for this message
Thomas Hood (jdthood) wrote :

Is there any workaround, e.g., editing a script somewhere?

Revision history for this message
Andrey Bondarenko (abone) wrote :

I suppose no.

To send empty domain name during authentication vpnc should be started with --domain "" command line option or Domain option without a value in config file. When starting connection, network-manager-vpnc makes temporary config file using connection parameters from NetworkManager and starts vpnc with it. The problem arises, because NetworkManager does not store domain if it is empty (AFAIK it cannot store empty strings at all).

So you have to either start vpnc manually, or somehow patch network-manager-vpnc to include empty Domain option.

If you need I can publish patched network-manager-vpnc version 0.9.8 that always sends domain. It's not a proper fix for the issue, but works as a temporary solution for me.

Revision history for this message
Andrey Bondarenko (abone) wrote :

A workaround for the bug is to create wrapper script for vpnc proposed by Kasuko http://ubuntuforums.org/showthread.php?t=2104986

#!/bin/sh
exec /usr/sbin/vpnc.real --domain "" $*

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

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager-vpnc (Ubuntu):
status: New → Confirmed
Revision history for this message
Andrey Bondarenko (abone) wrote :

A small improvement for workaround in #3: Use dpkg-divert to move vpnc out of the way. It will help your modifications survive after package reistalls/upgrades (see http://www.debian.org/doc/manuals/debian-faq/ch-customizing.en.html#s-divert)

dpkg-divert --local --divert /usr/sbin/vpnc.real --rename /usr/sbin/vpnc

Changed in network-manager-vpnc:
status: New → Confirmed
Revision history for this message
Ovsyanka (igor-deyawka) wrote :

I am not shure about Ubuntu, but on Arch linux it worked for me if I just set Domain="". I put `""` in the field in the settings GUI. And in the config file then there is:

```
[vpn]
Domain=""
```

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.