I don't think McAfee ENS officially supports WSL. At least that was the
case in 2018 when I last tried.

This would probably be evident in its labelling WSL /tmp writes as the
beginnings of an attack - you could always check your scan logs (at
%ProgramData%\McAfee\Endpoint Security\Logs) to see what is actually
happening - if this is a blacklisted directory, a rule firing, or if EDR is
picking up the sketchy behavior.

Feel free to raise a ticket to support on this topic - there's probably an
active community internal to McAfee who would love to get more momentum for
WSL support.

Some potentially dated sources on this topic:
1. ENS log manifest
<https://docs.mcafee.com/bundle/endpoint-security-10.6.0-common-product-guide-windows/page/GUID-2E289950-D6E3-4F7F-93EE-998790E5E028.html>
2. ENS lack of support for WSL
<https://kc.mcafee.com/corporate/index?page=content&id=KB91411>
3. A rather interesting article
<https://www.mcafee.com/blogs/other-blogs/mcafee-labs/knock-knock-whos-there/>
which spells out why WSL might not be well supported, i.e. it has the
tendency to be used for fileless attack behaviors.

Hope this helps!

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/CAC41hdON9_x54Fe6Yso8hd97%3DKCQ3Z6GRkfFjkwH6mB-Y5C2pQ%40mail.gmail.com.

Reply via email to