Re: Option for endpoint.anyconnect.deviceuniqueid of Cisco/ASA DAP

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

 



On Thu, Apr 23, 2020 at 11:21 AM yesi <yesi@xxxxxxxxxx> wrote:
> It advices to use AnyConnect on a Windows client to have support.

I don't understand.

> But i prefer Linux.

It's good for your administrators to know that you're using
OpenConnect on Linux, so that they'll make an effort to support it…
right?

If we pretend that you're using AnyConnect on Windows, and then the
connection fails because of some subtle difference in OpenConnect's
behavior, and this shows up in the logs… then your VPN's
administrators will try to test with AnyConnect on Windows (since that
appears to be what you're using) and they will find no problem… and
give up… and no one will have any useful information to try to fix the
problem.

If they can *see* that you're using OpenConnect, that there's a
failure… ideally they'll realize that they have clients using
OpenConnect and will try to support them.

Spoofing another client should, in my opinion, only be a last resort
for when your VPN absolutely prevents you from connecting unless you
spoof that client, and your VPN's administrators won't do anything to
fix the situation.

-Dan

_______________________________________________
openconnect-devel mailing list
openconnect-devel@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/openconnect-devel




[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