Jump to content

Leaderboard

Popular Content

Showing content with the most kudos on 09/26/2021 in all areas

  1. NewbyUser

    Borked HIPS

    It sort of says it "helps" with identifying open ports and vulnerabilities, but doesn't seem to indicate it has any protective role. So how is it a critical security mechanism? And on a side note, now I have to/should post about updates hanging again, this product is a mess.
    1 point
  2. itman

    Borked HIPS

    I need to correct my prior postings in regards to Eset Network Inspector and network inspection processing. Eset's network inspection processing is a critical security mechanism used to inspect IPv4 and IPv6 network traffic via proxy mechanism. It is "baked" into Eset and there is no way to disable it. Nor should you ever want to do so. Its malfunction in regards to monitoring of IPv6 network traffic in ver. 14 is the primary reason I embarked on this long resolution quest. Eset Network Inspector is the newer feature Eset introduced to monitor router tampering activities. It however does deploy Eset network inspection processing to do so. Besides Network Inspector borking my router's IPv6 configuration activities at system startup time, it was also failing to initialize the network inspection IPv6 network connection. BTW - disabling Network Inspector doesn't appear to fully disable its processing. Another Eset feature that uses it is the Network Wizard. The difference being when the Wizard is deployed is after system startup time. Since my router would be fully initialized at this time, it causes no adverse activities to occur against it.
    1 point
  3. itman

    Borked HIPS

    Interesting. My ISP router has an excellent stateful firewall plus IDS protection. Hence, external network attacks like these are dropped on the WAN side of the router. Also, more reason to disable Eset Network Inspector if there are suspicions it might be tampering with any internal router mechanisms.
    1 point
  4. Regarding the forum not saving what you have typed, I was not able to reproduce it. Navigating back and forth or refreshing the page didn't clear what I typed. Anyways, the forum is developed and maintained by a 3rd party provider and we have no permissions or rights to change the code ourselves. If there's an issue we can report it to the provider but we'll need to provide step-by-step instructions how to 100% duplicate it. Last but not least, I would like to ask you not to mix different issues in one topic but rather create a separate topic for an issue. 2021-09-26_10-08-04.mp4
    1 point
  5. I'm going to type this post again. I have the worst luck with this forum! I hit backspace to correct a typo in my post and Firefox went to the previous page I had visited, and I lost my entire post!!!! This has happened so many times on this forum! I have over 5000 post on Wilders and it has never happened on Wilders. The most annoying thing! I think i'm jinxed on this forum. The user should be given the option to opt out of auto-renewal when they purchase a license and it should be easy to see. Also, it is confusing on where to go to opt out of auto-renewal once you have been enrolled. I thought myeset.com would be the place to opt out since that is the site for managing License and Devices. I wasted a lot of time looking for an option to opt out of auto-renewal on myeset.com. I finally found the option to opt out of auto-renewal on store.eset.com. It only gave me the option to opt out for the license I had just purchased. My old license still reported that it was set up for auto-renewal within the Eset Application. I never was able to find any option on either website to disable auto-renewal for my old license. Please read my last response to itman above for more information and one possible solution for this problem. That will save me from having to type everything again.
    1 point
  6. Such shady auto renewal policies are unethical, and possibly illegal in some countries.
    1 point
  7. itman

    Borked HIPS

    Let's talk about Eset's Network Inspection Inspector processing since there is zip technical details on it. To begin, Eset's network inspection processing is not new and has existed on every EIS version I used dating to 2014. Past versions were relatively benign and non-troublesome. Once I configured Eset's network connection to accommodate my router, the settings remained stable. All this changed when Eset decided to get "cute" and expand network Inspection to examine router settings for the purpose of detecting suspected hacking activities. Great idea for off-the-self routers and the like that perform standard network initializing activities. A very bad idea for ISP provided routers with customized firmware settings. The only positive thing in recent Eset versions is that now Network Inspection Inspector can be disabled via GUI setting which was not possible in the past. For those who like technical details, let's get into those. Using a networking connection monitor such as TCPView, open it immediately after system startup time. Look for an ekrn.exe connection monitoring UDP port 138. Eset is examining network connections via proxy using this port. This is also where the problems start. My router is using NetBIOS which also uses that port to initialize it's router connectivity to my device. It then goes downhill network-wise from here.
    1 point
  8. itman

    Borked HIPS

    Correct. It also resolved a more serious issue that manifested on ver. 17. Upon resume from sleep mode, it appears the Eset firewall wasn't initializing itself properly; or not fast enough. Note this didn't happen upon every system startup from sleep mode, but it happened enough to be disconcerting. Network Wizard showed blocked svchost.exe inbound traffic to ports 53, 137, 1900, 3702, 5353, and 5355. The "rub" is the remote IPv4 address shown was my device assigned IPv4 address. In other words, Eset firewall; or more likely Network Inspector, wasn't initializing properly and was interpreting legit outbound traffic from my device as inbound traffic and blocking it!
    1 point
  9. First, verify your credit card data has been deleted from both your Eset eStore account and your myEset.com account. When I likewise did my Eset license renewal via EIS GUI option, it set up a myEset.com account w/o my permission and set it to auto renewal! Also stored in that myEset account is the credit card number used for the purchase. Given all the security issues with myEset.com accounts being hacked, I also deleted the myEset.com account. I for one have had it with Eset's overly aggressive license renewal/management crap. It's just "one more nail added to the Eset coffin" in regards to terminating the future use of this product.
    1 point
  10. itman

    How do i turn off auto renewal?!

    Tip - if you delete your credit card info in your US eStore account, there is no way for Eset to perform an auto-renewal.
    1 point
×
×
  • Create New...