This bug was fixed in the package network-manager-openconnect -
1.2.4-2ubuntu1
---
network-manager-openconnect (1.2.4-2ubuntu1) disco; urgency=medium
* Backport some git commit while talking to upstrem about a new tarball
* debian/patches/git_certkey_export.patch:
- Fix import
** Changed in: network-manager-openconnect (Ubuntu)
Importance: Undecided => Critical
** Changed in: network-manager-openconnect (Ubuntu)
Importance: Critical => Low
** Changed in: network-manager-openconnect (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug noti
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager-openconnect (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Looks good to me. Thank you for the fix!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673015
Title:
openconnect config file import cannot handle "(null)" values
To manage notifications about this
https://git.gnome.org/browse/network-manager-
openconnect/commit/?id=f58893e15fc7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673015
Title:
openconnect config file import cannot handle "(null)" v
Arguably the problem here is that you have, literally, "(null)" as the
string in the config file. IF you have a file with that name, you should
be permitted to use that.
This is a bug in the *EXPORT* not the import. We shouldn't (ideally)
special-case that filename on import. Although we might now
