On Wed, 2017-01-11 at 11:50 -0800, Daniel Lenski wrote: > > Add a new public function, openconnect_get_supported_protocols(), > which > returns a list of protocols supported by the client.? Each supported > protocol has a short name (as accepted by the --protocol command-line > option), description, and list of flags; currently, the only flags > are: > > ? * OPENCONNECT_PROTO_TCP (TCP transport supported) > ? * OPENCONNECT_PROTO_UDP (UDP transport supported) Hm, does the caller really care about those? What might make more sense is a set of flags indicating which authentication features are meaningful for each protocol ? can it support certificate auth, can it support OTP, can it support CSD, etc. Tools like the NetworkManager configuration UI would then disable certain options depending on the protocol that's selected. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 4938 bytes Desc: not available URL: <http://lists.infradead.org/pipermail/openconnect-devel/attachments/20170113/e56da6ea/attachment.bin>
