GNU bug report logs - #37369
Getting network-manager-openconnect to work

Previous Next

Full log

Message #23 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: "pelzflorian \(Florian Pelz\)" <pelzflorian <at> pelzflorian.de>
Cc: Help guix <help-guix <at> gnu.org>, Divan Santana <divan <at> santanas.co.za>,
 bug-guix <at> gnu.org
Subject: Re: Getting network-manager-openconnect to work
Date: Mon, 16 Sep 2019 17:57:51 +0200

Hi Florian,

"pelzflorian (Florian Pelz)" <pelzflorian <at> pelzflorian.de> skribis:

> On Wed, Sep 11, 2019 at 10:46:56PM +0200, Ludovic Courtès wrote:
>> Something I don’t get: why does NM itself know about openconnect?
>> 
>> There’s a network-manager-openconnect plugin, so I would expect
>> everything openconnect to happen there.  Do you know why it’s not that
>> way?
>> 
>> Thanks,
>> Ludo’.
>
> I don’t know.  The patch addresses (if it works) a function called
> nm_vpn_openconnect_authenticate_helper within the code for
> NetworkManager clients like nmtui, probably also nm-connection-editor,
> that calls openconnect --authenticate.

So I guess we first need someone to tell us whether the patch “works”,
as you wrote, right?  :-)

Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.