How to use OpenConnect and Cisco Secure Desktop with ConnMan (instead of NetworkManager)?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On 12.06.2018 18:33, David Woodhouse wrote:> So there are three pieces
of information which are needed to actually
> make the connection:
>
>  ? VPN server address
>  ? Certificate fingerprint
>  ? Cookie
>
> When you compare with your NetworkManager configuration, you are
> comparing apples and oranges. That contains the information that you
> *start* with ? the first server you start authenticating to, things
> like usernames and passwords. ConnMan doesn't care about any of that,
> or didn't when I last looked. It just needs those three fields listed
> above (which are precisely what the NM auth-dialog actually hands off
> to NetworkManager itself, behind the scenes).

Nothing has changed for ConnMan so far. Wouldn't mind if ConnMan would
learn to do be more user friendly.

> Somewhere there was a script which runs 'openconnect --authenticate' to
> obtain the three relevant fields, and then poke ConnMan to connect
> using them. Isn't that still in the ConnMan repo somewhere?

Just checked the repo and there is no such script :/ And my google-foo
didn't find anything related.

Thanks,
Daniel



[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux