BigBob

Look like here at my company, we are affected by the same exact behavior @eab described in this thread...
Like @eab, as an enterprise customer, I am very surprised that problem stay in « backlog », since to be able to use services listening on « localhost » for all of our developer's, it imply to disable completely the WAP security on all of our Linux clients running the product...
 
I am now following this topic, thanks to @eab for the detailed behavior described here...

Look like here at my company, we are affected by the same exact behavior @eab described in this thread...
Like @eab, as an enterprise customer, I am very surprised that problem stay in « backlog », since to be able to use services listening on « localhost » for all of our developer's, it imply to disable completely the WAP security on all of our Linux clients running the product...
 
I am now following this topic, thanks to @eab for the detailed behavior described here...

Yes, that's the last reply I received from Mr. Schwalb on the 13.12.23. It doesn't say anything other than "we have reproduced the issue and will fix it at some point in time".
As a business using ESET for PC security, I expect a bit more in the way of a timeline of this problem being fixed - a problem which is so severe it makes WAP harmful to productivity (for Linux users), where it really should not. And for that kind of problem I expect something a lot more concrete from the developer of the software.