Allow Passing Custom `openconnect` CLI Arguments
Some time ago, openconnect
added a new --allow-insecure-crypto
option to the master branch (which hasn't been released yet).
Said option enables the use of outdated mechanisms such as Unsafe Legacy Renegotioation
and a variety of outdated ciphers.
As I'm using the master branch version of openconnect
, I'd love to be able to add the --allow-insecure-crypto
argument to the openconnect
call.
I'd love to have the option to add custom openconnect
command line arguments somewhere in the NetworkManager settings.