05-29-2020 01:49 AM - edited 05-29-2020 02:12 AM
Hi,
I'm looking for accurate documentation on how the AnyConnect duid is generated.
If I look at DART cli options, there is two ways to print the uid of a device :
-u, -udid
Display global unique device identifier information.
-ul, -udid_legacy
Display unique device identifier(legacy) information.
But It seems that it is NOT a unique device identifier on Linux systems.
I do retreive the same id on three differents devices under differents local users and differents Linux OS (Fedora 31, Ubuntu 18.04).
Those devices were not cloned. They were installed from scratch at differents dates.
Looking at this documentation, the udid should be unique.
An option to generate a new udid exists only for Windows.
So does anyone know how these ids are generated ?
It seems that it is not safe to use it under an authorize policy on the ASA.
I'm going to open a case about this issue.
Thank you
Solved! Go to Solution.
11-10-2020 06:22 AM
Hi
I reported the issue to the TAC this summer :
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvu65566
It has been fixed in version 4.9.01095 or later.
Deploying this release or later using auto update can set to a connection error once after upgrade :
Regards
11-10-2020 06:22 AM
Hi
I reported the issue to the TAC this summer :
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvu65566
It has been fixed in version 4.9.01095 or later.
Deploying this release or later using auto update can set to a connection error once after upgrade :
Regards
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide