Debian Patches
Status for openconnect/9.01-3
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| Do-not-add-single-sign-on-to-the-capabilities-list-f.patch | 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. |
Rahul Rameshbabu <sergeantsagara@protonmail.com> | no | debian | upstream,https://gitlab.com/openconnect/openconnect/-/commit/0e82c9371420db42376f7952f0d756222aba1001 | |
| Fix-pulse-9.1R16-connection.patch | Fix pulse 9.1R16 connection | Timothee 'TTimo' Besset <ttimo@ttimo.net> | no | debian | upstream,https://gitlab.com/openconnect/openconnect/-/commit/c9831b382c7839682b3f1ea0a7f950e6cb55d5e8 |