The attached patches improve the XML configuration handling. The first fixes the behavior of the client not being able to download the configuration if the server doesn't provide any hash (doesn't address the case where openconnect_set_xmlsha1 isn't called). The second documents the fact that the configuration can be downloaded -without connecting- using the --authenticate and -x flags. The last is an RFC to replace the callback APIs with something more reasonable, i.e., a flag to ask the client to download the config and a function for the caller to retrieve it. I am not sure whether the SHA1 hash for xml configs is of any use at all. Most likely the configuration will be downloaded, not every time, but at specific times where the user would like to retrieve that configuration (e.g., first connection, or first connection after a client reset). If we agree on the API for xml config retrieval, I'll continue with a patch to parse these configuration files. regards, Nikos -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-fetch_config-download-config-if-no-SHA1-hash-of-prof.patch Type: text/x-patch Size: 2227 bytes Desc: not available URL: <http://lists.infradead.org/pipermail/openconnect-devel/attachments/20161226/03f56d68/attachment-0003.bin> -------------- next part -------------- A non-text attachment was scrubbed... Name: 0002-man-page-improve-text-on-xmlconfig.patch Type: text/x-patch Size: 851 bytes Desc: not available URL: <http://lists.infradead.org/pipermail/openconnect-devel/attachments/20161226/03f56d68/attachment-0004.bin> -------------- next part -------------- A non-text attachment was scrubbed... Name: 0003-RFC-Introduced-functions-to-request-the-retrieval-of.patch Type: text/x-patch Size: 7088 bytes Desc: not available URL: <http://lists.infradead.org/pipermail/openconnect-devel/attachments/20161226/03f56d68/attachment-0005.bin>
