Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 03/09/2020 in all areas

  1. 1 point
    Did you make sure you got the correct file path for the executable as a custom Exclusion rule with Immunet? If the installer created it, did you try an Exclusion rule for the "entire Program Files folder" for the software? If you are sure you created an Exclusion with the correct file path(s) and it's still being blocked then I would suggest you submit a False Positive report at this URL for the devs to take a look at. https://www.immunet.com/false_positive You will need the correct SHA256 checksum to complete the FP report. If you're not sure what the correct hash is you can contact the software developers for this info. Another option to obtain the correct SHA256 checksum would be to use a third-party software program like HashCalc. I've personally used this software myself on occasion. https://download.cnet.com/HashCalc/3000-2250_4-10130770.html Best wishes & stay healthy, Ritchie...
  2. 1 point
    Please see attached samples for detection, ZIP is not password protected.
  3. 1 point
    Has anyone else been getting a certificate error/warning when attempting to visit these forums? I've checked my computer's clock and tried visiting with GNU Icecat (Firefox ESR), regular Firefox, and Vivaldi (based on Chromium). Warning message every time. I haven't tried regular Google Chrome but suspect users of that browser won't have any issue connecting, because last time I paid any attention to anything G, Chrome still wasn't checking the validity of HTTPS certificates (this might seem convenient because all websites "just work", but in reality is a very bad thing for your security). This situation might have changed, but as I have not used anything G for a very long time, I cannot check. If it helps webmasters with any diagnostics, I use "HTTPS everywhere" from EFF.
  4. 1 point
    Thanks for calling it out Zom, our forum cert is defiantly expired. A new one is on the way but I don't have an ETA fr it yet. Cheers, RobT
  5. 1 point
    If the UI ever supposedly comes to a change where the old theme will be replaced with a newer one then before that happens you should know why it's not a good idea. Modern UI is almost everywhere, some people have brought up the idea to replace the "dated" older UI. My question is, do you REALLY want to do what everybody else's doing with THEIR website? I mean, you can do whatever you want to YOUR website but consider this: why am I doing this? Are you doing it because of the new modern UI trend popularized by Microsoft? (Microsoft really popularized modern UI, look it up if you don't believe what I'm saying). What I think is; you should do what YOU want to do, not what everybody else's doing. And if that IS what you want to do then go ahead. I must say though, a flat UI makes a 2D screen boring. A 3D UI (like the one Immunet is using for their program rn.) establishes what's boring to new, futuristic, and special. My idea is this: You can change whatever you want, but don't make it modern UI. This's just a constructive opinion, you don't have to do what I tell you to do, but when you have almost every single website you look at SHARE ONE ENTIRE UI, I start to lose sanity. What I will like is if you change the UI to something less "dated" but keep the 3D effect. You can even make a whole new UI yourself.
  6. 1 point
    That's kinda what I want. And I agree 100%
  7. 1 point
    I wholeheartedly agree. The standard Immunet UI actually looks pretty good and has aged rather well. It's also very easy to understand and use, right from the moment you first ever use the program. The only real area where it starts to show its age is on high resolution screens, where it either appears very small or scales poorly. It was better suited to the days of 800x600 or 1024x768. Maybe all it needs is a very slight cosmetic revamp, and the addition of scaling/HiDPI capability, with the general layout left largely untouched. Like others here, I really don't like the trend for "modern" UI. It's flat, boring, looks dated to begin with, and has no visual appeal whatsoever. It's like the whole metaphor of a "button" that you "press" has gone out of the window, and designers got lazy and just drew harsh-edged rectangles in Paintbrush. I remember DosShell and the MS Windows 1.x-2.x series being more ornate than W10. Even the standard X11 TWM is, and that's older than me! I still think the prettiest and nicest looking user interface for desktop PCs was KDE3 with the Keramik widgets and window-decorations, and Crystal icon theme. That was extremely 3D! The nearest Windows equivalent would probably be Windows XP Luna. Both still look good today even in a VM on modern hardware - although I think the best looking Windows interface by far (and easiest to use) is the 9x/ME/NT/2000 interface. Again, those buttons etc. still look good for some programs, even at high res.
  8. 1 point
    Ritchie I went and loaded Firefox on another drive so the warning would come up. I'll just uninstall it. I couldn't find it once I went past it on other drive with Firefox. If I'm getting it so are others. My clock is correct.
  9. 1 point
    Here's an update on another method scammers are using right now. Some people are reporting receiving scam phone calls saying they're a medical professional and that a family member is sick with covid-19 and needs to be treated but can not do so unless payment is received up front. Don't fall for this one either folks! Best wishes, Ritchie...
  10. 1 point
    Sorry all, I haven't been able to reproduce the 503 error on any version of windows 10 so all I have to offer is some troubleshooting steps for it's most likly causes. By any chance Is anyone on this thread seeing this error from somewhere outside north America? If you are seeing the 503 error please verify you can at least: 1) ping clamav.net should output something similar to: Pinging clamav.net [198.148.79.54] with 32 bytes of data: Reply from 198.148.79.54: bytes=32 time=80ms TTL=128 2) browse to update.immunet.com --> It's just a blank page with nothing to see. The important thing is you don't get any "page not found"/403/503/unreachable error messages. 3) browse to http://database.clamav.net --> this should open a page saying "You reached one of ClamAV virus database mirrors:" 4) if steps 2 or 3 fail, please double check from a different browser. If your getting errors with any of the above, you there are 3 common causes: A) there is a local a firewall preventing you from accessing Immunet's servers. Temporarily disable it and see if your 503 errors stop. Also note that sometimes windows 10 updates will turn the default windows firewall back on. So if you thought you left it disabled it's worth double checking it's still disabled. Immunet's IP addresses change all the time and a common problem we see is users allowing access to Immunet server IP's during the initial install and everything works great, but a few months later our server IP's change but your local machine's firewall rules have to be manually get updated to allow connecting to Immunet's new IP's. C) You might be using a DNS server that can't resolve Immunet's hostnames to the correct IP addresses. Try setting a different DNS server in your network connection settings : Google hosts one at 8.8.8.8 (it's also the only static IP I know). I won't guarantee anything about it's privacy, but I will guarantee its at least providing accurate hostname-to-IP resolution to reach Immunets servers. i) Immunet uses the default system level default DNS server, which is usually found in your local area connections settings, and is usually assigned automatically by your internet provider. ii) Note that a computer can be configured to use an multiple alternate DNS servers than the one provided by your internet provider. Individual web browsers can be set to use different DNS' from each other, which can in turn also be different from the local area connection level dns. iii) Some programs that can lead to the confusion of dealing with multiple DNS servers are: -Comodo Firewall products that install their own local DNS Server. -browser plugins & add-ons that claim to to increase security or privacy by re-routing DNS queries that originate from the browser through their secure/alternate DNS server. -Private vpn's usually provide their own DNS servers while you're connected to them and sometimes offer free private DNS servers for use when disconnected from the vpn. -malware that will maliciously redirect your DNS settings "aka the DNShijack" attack. iv) The user Amydala reported above that Immunet's installer didn't work with the Firefox browser but did work with IE. This is a telltale sign of having multiple different DNS servers across different browsers.
  11. 1 point
    Hey guys, "I too wish something can be done to end these 503 error messages that users are still encountering once & for all!" I can see why someone might get a little frustrated as this issue seemingly continues to go unresolved unfortunately. It makes me wonder if Immunet's update server is being overloaded with requests at times causing this error. Does Immunet need a faster/improved update server that can handle more traffic? CAVU, Rob or myself will send you a PM regarding your old log in credentials if they can be retrieved.
  12. 1 point
    I am a new User and have no idea if this is helpful but just in case... I could not download the installer. It kept telling me there was an internet problem. So I saw this thread and tried the links posted above. Couldn't reach the https://sourcefire-apps.s3.amazonaws.com link. So after some investigating, I found out it was a Mozilla/Firefox problem. I changed my default browser in Windows to IE and boom, it worked. Hope this helps someone.
×
×
  • Create New...