https://bugs.kde.org/show_bug.cgi?id=456543
Bug ID: 456543
Summary: Update plasma-nm to have broader openconnect
functionality
Product: plasma-nm
Version: 5.25.2
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: editor
Assignee: jgrul...@redhat.com
Reporter: emele...@gmail.com
Target Milestone: ---
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
plasma-nm for openconnect vpn lacks some functionality offered by the latter.
openconnect has a number of protocols that are not embedded into the plasma-nm
editor. In addition, due to the particular implementation, editing the
connection generated by hand or by nm-applet results in breaking the
cnfiguration.
STEPS TO REPRODUCE
1. Open the editor to set up a new connection
2. Observe there are missing protocols for openconnect
3.
OBSERVED RESULT
Missing protocols
EXPECTED RESULT
A full set of openconnect protocols to set up the vpn connection
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: Fedora Linux 36
(available in About System)
KDE Plasma Version: 5.25.2
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.3
ADDITIONAL INFORMATION
openconnect currently supports the following protocols,
Set VPN protocol:
--protocol=anyconnect Compatible with Cisco AnyConnect SSL VPN, as
well as ocserv (default)
--protocol=nc Compatible with Juniper Network Connect
--protocol=gp Compatible with Palo Alto Networks (PAN)
GlobalProtect SSL VPN
--protocol=pulse Compatible with Pulse Connect Secure SSL VPN
--protocol=f5 Compatible with F5 BIG-IP SSL VPN
--protocol=fortinet Compatible with FortiGate SSL VPN
--protocol=array Compatible with Array Networks SSL VPN
but plasma-nm openconnect vpn can only handle the first four, which are
hard-coded in the editor and in OpenconnectSettingWidget::loadConfig.
However, openconnect provides the function
int openconnect_get_supported_protocols(struct oc_vpn_proto **protos)
which returns the number of supported protocols and stores them in *protos .
NetworkManager uses this information to populate the drop-down menu in the UI
so that new protocols become available as soon as they are implemented in
openconnect.
I believe it would not be too difficult to implement the same mechanism in
plasma-nm to expand the range of choices the user has for openconnect vpn
connections. At the very least, plasma-nm should be updated to include the
missing protocols.
--
You are receiving this mail because:
You are watching all bug changes.
