On Tue, Apr 10, 2018 at 5:37 AM, Daniel Lenski <dlen...@gmail.com> wrote:
> On Apr 6, 2018 2:23 PM, "David Woodhouse" <dw...@infradead.org> wrote:
>>On Fri, 2018-04-06 at 11:54 -0500, Daniel Lenski wrote:
>>> On Fri, Apr 6, 2018 at 11:27 AM, Luis l <chel...@hotmail.com> wrote:
>>> > Hi Guys, I am using the latests version of OC w/ Palo Alto VPN …
>>> As explained on the page for the fork with PAN GlobalProtect support
>>> (https://github.com/dlenski/openconnect#feedback-and-troubleshooting),
>>> you should report problems which are specific to PAN-GP as a new issue
>>> on Github, rather than on this mailing list. GlobalProtect support is
>>> not yet part of the official OpenConnect.
>> FWIW I have no objection to using the mailing list for it even when it
>> isn't merged yet.
> Great, okay! I think I added that admonition on the Github project
> README when it was at a much less functional state.
>> Where *are* we with merging it?
> I gave you another round of cleaned-up-and-rebased patches on March 4,
> and one more patch on top on March 27 (for tolerance of oversize ESP
> packets, in the same vein as previous patches for tolerating oversize
> ONCP and GPST packets).
>> I did some heckling
>> at the last round of patches as there was some string allocation
>> confusion, and it looked like it hadn't been run in valgrind. Did you
>> give me another set after that?
> valgrind credibly accuses me of a lengthy of memory-allocation crimes.
> I haven't fixed them all yet. :-(
> Do you have a preferred invocation for valgrind'ing openconnect, by
> the way? To test the GP protocol, I've been using variants of this:

Not sure about valgrind, but if you want to run the testsuite of the
openconnect, you can fork the project from gitlab, and check the
existing tests + your tests outputs on the pipelines:


openconnect-devel mailing list

Reply via email to