Package: openconnect / 9.01-3
Metadata
Package | Version | Patches format |
---|---|---|
openconnect | 9.01-3 | 3.0 (quilt) |
Patch series
view the series filePatch | File delta | Description |
---|---|---|
Do not add single sign on to the capabilities list f.patch | (download) |
auth.c |
4 0 4 - 0 ! |
do not add 'single-sign-on' to the capabilities list for anyconnect auth requests In 024336a8ddeb1754ae5e8fb18770e90c206070b1, we added 'single-sign-on-v2' to the list of auth-methods capabilities in AnyConnect auth requests, and also included 'single-sign-on' (no '-v2') because we had seen it included in a MITM capture from a Cisco client. See discussion at https://gitlab.com/openconnect/openconnect/-/merge_requests/126#note_853084596. . However, OpenConnect does not actually know how to handle the 'single-sign-on' case, and include it appears to confuse Cisco servers and cause them not to return the expected XML structure in their subsequent responses. See https://gitlab.gnome.org/GNOME/NetworkManager-openconnect/-/issues/72 and further discussion on https://gitlab.com/openconnect/openconnect/-/merge_requests/394. . Removing 'single-sign-on' from the list of auth-methods capabilities should resolve this issue. |
Fix pulse 9.1R16 connection.patch | (download) |
pulse.c |
29 18 11 - 0 ! |
fix pulse 9.1r16 connection |
1