Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 01/27/2020 in all areas

  1. 4 points
    What a "great idea" for Immunet users to voice their likes & dislikes Barbara! I completed the survey although, if chosen, I wouldn't be able to participate in the video conference since my computer has no web cam. "I would 'strongly urge any & all Immunet users' to complete this survey!" It really does only take a few minutes & that will give the devs much more insight into what Immunet users want in a new build. Best wishes, Ritchie...
  2. 3 points
    A couple of times this month I received a recorded phone call allegedly from an Amazon employee stating that they have detected possibly fraudulent activity with my account. I was then prompted to press 1 for more info. "I immediately knew this was a 'scam call' for the simple reason that I don't have an Amazon account!" After that I decided to do some investigation into this. "Amazon is aware of this scam and is advising it's customers if you do receive one of these scam calls don't fall for it, just hang up & 'definitely don't press any numbers' when prompted!" You can always check your Amazon on-line account yourself if you have any concerns and then contact Amazon customer service directly if you have questions. These Amazon scammers have also been using hacked email accounts. If you receive an email with similar content just delete it without clicking on any links or attachments included. You're also encouraged to report these calls or email to the Better Business Bureau, https://www.bbb.org/ and the Federal Trade Commission. https://reportfraud.ftc.gov/ Not a bad idea to also report this activity to your state's Attorneys General office. Regards, Ritchie...
  3. 3 points
    Hi Immunet Users, The development team working on Immunet (by Cisco) is looking for your feedback. Do you have 5 minutes to fill out a survey telling us more about how you use Immunet and how you think it could improve? Here is the link to the survey: https://www.ciscofeedback.vovici.com/se/6A5348A7201B0385 We know there is a lot of misinformation on the internet these days. If you would like to verify that this is real Cisco-sponsored research, email Barbara Shain, Cisco User Researcher, at bshain@cisco.com Thanks, Immunet UX
  4. 3 points
    I think this is an awesome thing!! I have filled out the survey and left my feedback. I really like that the platform is getting more support from cisco! As you said ritchie I would also encourage all users to fill out the survey, this will give us a chance to give feedback to the devs on how to improve the AV. The more of us that fill it out the better it will be. I can't wait to see how the survey helps and how it will help improve Immunet as a whole:) Stay safe everyone
  5. 3 points
    Hello all, We are happy to announce a new release of Immunet: Version 7.3.0! This latest version of Immunet provides the same great protection against malware and viruses as before but also includes some new features, enhancements and bug fixes as below. Changes in 7.3.0 New & Enhancements: New endpoint threat activity detection engine New Immunet UI cloud connect status message replacing cloud stats message Bug Fixes: Connector cloud registration issue fix related to long network interface names Fixed an issue related to support package Mitigating fixes related to no-reboot upgrade and uninstall failures Immunet Installer bug fixes Other bug fixes You can get the new installer from here https://download.immunet.com/binaries/immunet/bin/ImmunetSetup.exe Expected upgrade behaviour for Immunet users: Upgrades from Connector versions < 7.0.0 to 7.0.0+ require a reboot to complete Upgrades from Connector versions 7.0.0+ to any higher version do not require a reboot to complete Looking forward to your participation in using our new detection engine and some help in cases of upgrade reboot failures issues, if encountered any. We would appreciate it if you can reach out to us via support forum with Support logs as soon as you see upgrade failing or upgrade asking for a reboot on upgrade. If you are running an older version of Immunet, you should be able to upgrade via the 'Update Now' button in the UI. If you don't see the update in your UI we recommend uninstalling Immunet and reinstalling the version downloaded from http://www.immunet.com/index
  6. 2 points
    Hmm, restore from quarantine seems fine now. I suspect this might just be related to system load. If the system is under stress when an attempt is made to restore from quarantine, it probably takes slightly too long for the GUI to communicate properly with the Immunet service, so the GUI assumes that the service isn't running, and/or the operation has failed. Intermittent error are the worst to diagnose and fix!
  7. 2 points
    Hello all We are happy to announce a new release of Immunet: Version 7.3.2! This latest version of Immunet provides the same great protection against malware and viruses as before, but also includes some new features, enhancements and bug fixes as below. Changes in 7.3.2 New: Exploit Prevention engine with Script Control support Bugfixes/Enhancements Improvements to endpoint threat activity detection engine Increased the number of process exclusions honoured by the Connector to 500. Improved stability of local UI notifications. Addressed an issue where System Process Protection exclusions would not work for processes that start before the Connector. Changed Connector driver altitudes to officially registered altitudes. Removed Connector-related events and logs from a computer when the Connector is uninstalled Addressed issues with file exclusions. General performance and stability improvements for Exploit Prevention engine Fix for the vulnerability described in CVE-2019-0708. Fixed Exploit Prevention engine compatibility issues with the following applications: APTA Connect MS PowerPoint 2016/2013 FSLogix Internet Explorer and different plugins CIG ACG MS Office Appv applications Visual Studio debugger Vizient and Open Text IRM Black Knight You can get the new installer from here https://download.immunet.com/binaries/immunet/bin/ImmunetSetup.exe Expected upgrade behaviour for Immunet users: * Upgrades from Connector versions < 7.0.0 to 7.0.0+ require a reboot to complete * Upgrades from Connector versions 7.0.0+ to any higher version do not require a reboot to complete If you are running an older version of Immunet, you should be able to upgrade via the 'Update Now' button in the UI. If you don't see the update in your UI we recommend uninstalling Immunet and reinstalling the version downloaded from http://www.immunet.com/index
  8. 2 points
    I thought of yet another Idea that some users might appreciate. Add a dedicated CMD Command-line scanner to Immunet. That would be something useful for power users & IT technicians. Cheers, Ritchie...
  9. 2 points
    I support that 99,999% Jasen Dear Immunet_UX, please read the forum! please support your forum moderator! please tell the support that you are welcome to reply to e-mails! The Form is fillet out with my informations but please ask to ritchie because ritchie knows all important things and is our hero. I don't have high hopes, because Windows 7 ...
  10. 2 points
    Done! It's nice to see this project getting the care it needs. I'm eager to see what it's coming from this!
  11. 2 points
    Oh yes Ritchie, you are doing an excellent job.
  12. 2 points
    You made a great Job here Ritchie, you help a lot this community. Perhaps cisco doesn't have someone managing support of immunet. It seems when they have a free time they visit here to see what is going on.
  13. 2 points
    Hey all, For a more "generic" way to start/stop Immunet, you can do the following (possibly only works in Windows 10, I haven't tried on earlier versions * ) : Stopping Immunet From the command line: wmic service where "name like 'Immunet%'" call stopservice or from a batch file: wmic service where "name like 'Immunet%%'" call stopservice (Re-)Starting Immunet From the command line: wmic service where "name like 'Immunet%'" call startservice or from a batch file: wmic service where "name like 'Immunet%%'" call startservice The advantage of these is you don't need to know what version of Immunet you're using, so you don't need to work out the new service name after upgrades or edit any scripts you have. I have a custom script that downloads some of the Securiteinfo, Sanesecurity and RFXN custom databases, stops Immunet, copies them to Immunet's "ClamAV" dir, and restarts Immunet. By identifying the "newest" ClamAV dir and using the more-generic way of stopping the service, my script doesn't need editing every time Immunet upgrades. For my case, this increases Immunet's static file detection rate from about ~75% to >95%. I originally worked this out a while ago because I did a couple of upgrades where the Immunet service changed name from something like "ImmunetProtect" to "Immunet 6.0.4" --- * I don't know much about Windows as I've been primarily a Unix/Solaris/GNU-Linux user for both work and play since the late 1990s. I only maintain a Windows installation for the tuning software that allows me to flash custom maps to my car's ECU.
  14. 2 points
    Hi 4tygrit i've the same update problem with the main.cvd file in a other post. To update immunet i've download ClamAV Portable (doant forget to get Updates in ClamAV). Stop the Immunet Service Delete in "C:\Program Files\Immunet\clamav\0.1......" the file main.cvd and daily.cvd copy the main.cld and daily.cvd files from "...\PortableApps\ClamWinPortable\Data\db" to "C:\Program Files\Immunet\clamav\0.1......" Start the Immunet Service again
  15. 2 points
    Hello all, We are happy to announce a new release of Immunet: Version 7.2.8! This latest version of Immunet provides the same great protection against malware and viruses as before but also includes some new features, enchantments and bug fixes as below. Changes in 7.2.8 New & Enhancements: Added support for the Windows 10 November 2019 Update (version 1909) Added support for Windows 10 20H1 (Version 2004) (RTM Preview build: 19041) Improved visibility and enhanced protection against script-based attacks System Process Protection Improvements Improved Malicious Activity Protection engine to no longer detect on Google Chrome Stability Improvements in the Exploit Prevention engine Installer improvements to handle NoReboot upgrades and uninstall Stability Improvements in the Immunet SelfProtect driver Bug Fixes: Resolved Windows Connector service freeze issue on startup, under certain circumstances Improved the Windows connector process of gathering BIOS serial number, when needed, to properly detect hardware changes for registration with AMP Cloud Fixed a crash that could be encountered on shutdown Addressed issue where Windows Connector would fail to upgrade when installed alongside BitDefender AV Made stability improvements in the Connector installer Fixed an issue where ClamAV was taking a long time in scanning PDF files resulting into longer high CPU usage Updated ClamAV to 0.102.1, including changes related to the vulnerability described in CVE-2019-15961 Fixed an Exploit Prevention engine issue that could cause Google Chrome v78 and later to crash or display a renderer code integrity error This version also addresses the following vulnerabilities: CVE-2019-1010305 CVE-2019-12625 CVE-2019-12900 You can get the new installer from here https://download.immunet.com/binaries/immunet/bin/ImmunetSetup.exe Expected upgrade behaviour for Immunet users: * Upgrades from Connector versions < 7.0.0 to 7.0.0+ require a reboot to complete * Upgrades from Connector versions 7.0.0+ to any higher version do not require a reboot to complete Looking forward to your participation and help in cases of upgrade reboot failures issues, if encountered any. We would appreciate it if you can reach out to us via support forum with Support logs as soon as you see upgrade failing or upgrade asking for a reboot on upgrade. If you are running an older version of Immunet, you should be able to upgrade via the 'Update Now' button in the UI. If you don't see the update in your UI we recommend uninstalling Immunet and reinstalling the version downloaded from http://www.immunet.com/index
  16. 2 points
    I'd like to report that the 7.2.8 upgrade through the UI took place with no problems. No reboot necessary! Great job on that guys! I did have to create a new allow rule with my firewall for sfc.exe but that's not uncommon behavior when a new build is installed. Some impressive changes have been made! A personal thanks to nirmeshptl for including a detailed change log with this announcement! Something I've been suggesting in the past when a new build is publicly rolled out. Best wishes, Ritchie...
  17. 2 points
    Interesting video you uploaded Valnat! Thanks for sharing. As the video demonstrates Immunet has some suburb efficacy! Much better than Microsoft's Defender AV! As you mentioned Immunet can be used as a stand-alone AV solution but it is recommended you use the ClamAV module if used in that manner. If Immunet is used as a companion AV to another compatible "paid product" it's best if the ClamAV module and updates for it remain disabled. This will reduce the amount of system resources being used. Also, don't forget to create exclusion rules for the Program Files folders for both AV's. This can go a long way in avoiding possible conflicts between the two AV's. Regards, Ritchie... P.S. I moved this topic to the General forum section since that's a better place for it.
  18. 1 point
    Here's something else you could try. Immunet developers have rolled-out a new 7.3.12 build that has some bug fixes & improvements. You should get the update pushed to you through the UI or you can directly download the newest boot-strapper installer here. https://download.immunet.com/binaries/immunet/bin/ImmunetSetup.exe It wouldn't hurt to do an uninstall & reinstall actually considering the circumstances. It's up to you. If you do decide to do a uninstall & reinstall with the new build I would recommend you keep your previous Settings & Exclusions by clicking on the "YES" option when the uninstaller prompt asks if you plan to re-install Immunet. That way you won't have to re-configure your Settings and add your Exclusions over again as Immunet will save your history.dat files.
  19. 1 point
    I watched the whole video. Great idea to add the screen grab video for documentation! There definitely is some sort of 'continuing' serious conflict between the game & Immunet. "Yeah, that process 'normally' does not continue to use up that much system resources for that length of time!" Weird! Have you tried to contact the game's developers to see if Path Of Exile has caused problems with other AV's & if there's a fix/workaround for that? This just a guess on my part but some games do use one or more Windows Temp file directories that might also need excluded. That's something else you could ask the game's developers. One more thing you could try is also disable 'Monitor Program Start' in Settings to see if that makes any difference. You will lose some of Immunet's efficacy by turning off this important setting however. Like I mentioned before, I do wish a support technician would get involved with this issue but I'm not going to hold my breath on that happening! Best wishes, Ritchie...
  20. 1 point
    The Immunet team would like to wish everybody a Merry Christmas & Happy New Year!
  21. 1 point
    I wish a support person would/could add some insight into this issue. Adding the entire games' C:\Program Files (x86)\ folder directory to the exclusion list should have worked. Unless... Immunet does have additional behavioral blocking capabilities too so maybe that's the issue. Immunet thinks that the games' executable is possibly "unknown malicious code" trying to execute on your system would be my extrapolation. Mmm, try adding another exclusion for the file path of the executable file that's being shown with the warning dialog box. That is: C:\Program Files (x86)\Path of Exile\PathOfExile_X64.exe (great idea to add the screen-grab btw!). Also, try turning off "Blocking Mode" in Settings too. Regards, Ritchie...
  22. 1 point
    If you created a C:\Program Files Exclusion for the game that should have worked! No mistakes can be made with spelling, spaces, etc... associated with the file path or the exclusion won't work. If you manually typed in the file path the first time around try using the Exclusion's "Browse" feature this time. Also, try excluding the game's "entire Program Files folder" if you didn't last time. Here's how... Open Settings -> scroll down to Add New Exclusion & click on that -> click on the Browse button -> find the correct Program Files folder and click on the folder itself -> click on Add Exclusion -> click Apply -> click Close. You can delete the old exclusion after you create the new one. I hope this info helps qwerty123 Best wishes, Ritchie...
  23. 1 point
    Well, isn't that strange! Sorry zom but I would recommend that matt use Revo Uninstaller instead since I've never heard of or used BCUninstaller. I've personally used Revo Uninstaller with very good results in the past with uninstalling troublesome programs. Revo can in fact find orphaned registry keys, left over folders and files too if you use the Advanced scan setting. The free version will work great with 32bit systems but I would recommend you choose the "fully functional free trial" of the Pro version if you have a 64bit system as it better supports those platforms. https://www.revouninstaller.com/revo-uninstaller-free-download/ If you've never used Revo Uninstaller before there are some great tutorial videos (even by the developers themselves) on YouTube you can view prior to using the software. Just to be on the safe side it's not a bad idea to create a manual "System Restore Point" first in case you accidentally delete something you shouldn't have (like a OS system file or folder). I would recommend you enter "Safe Mode without Networking" before uninstalling with Revo Uninstaller. Some earlier versions of Win 10, Microsoft (in it's infinite wisdom) made accessing Safe Mode a more dawn out affair so let me know if you run into any difficulty there. Also, please read the thread I added to the other Issues/Defects topic you posted regarding what to do next with the reinstall. Cheers, Ritchie...
  24. 1 point
    Hi qwerty123, Have you tried to add a custom Exclusion rule for the autohotkey app(s) with Immunet? If not, give that a try and see if that fixes the issue. Just make sure you exclude the correct file path(s) for the app(s).
  25. 1 point
    Don't forget to delete the files lastupd and update.log (a lastupd file can make trouble). During tests, I always rename the cvd files to see if fresh cvd's are being downloaded. FrankenImmunet, sounds good. FrankenImmunet with IgorCloud.
  26. 1 point
    Sorry to have been the harbinger of doom! I agree with lavamagma in that it is probably some sort of timeout issue. A while back I started experiencing update timeouts with both Freshclam and the "clamav-unofficial-sigs" scripts on my GNU/Linux boxes. It was basically caused by a time-out value that was too low in freshclam.conf (or wget/curl's default settings, in the case of the unofficial signatures script). Once the database had grown to a certain size, it was impossible to download it quickly-enough for the entire file to be complete before the timeout was reached. This was initially noticeable with the unofficial signatures script, because the SecuriteInfo "old" database is extremely large (~300MB), and SecuriteInfo restricts download-speeds for free users to circa 384KB/s. I believe a change to the default freshclam.conf fixed this in one of the recent versions. I suspect that you won't see this issue if you've already downloaded all the ClamAV databases once, because subsequent updates only require downloading the latest .cld patches. One way to test this would be to manually download the ClamAV databases from the web site, stop Immunet's service, copy them to Immunet's ClamAV dir, and then restart Immunet. Another option, if Immunet honours freshclam.conf settings, is to look to see if freshclam.conf is present in the folder, and set the ConnectTimeout and ReceiveTimeout settings to something like 300 (5 minutes) and 3600 (1 hour) respectively. I may have a quick look at these two options when I am next back in Windows.
  27. 1 point
    i am done with immunet. why bother when simplest update is headache looking like updates from amp to immunet botched guess they using amp over there in cisco this free is free headache i have gone way of virtual box hopefully this gets fixed or pay to use i really havent had a need for antivirus past months my 2 cents stay safe u al
  28. 1 point
    I'm sorry, but I find the survey very disturbing. I cannot get the Immunet 7 service to stay running and development wants to ask how I feel about the importance of "history" and if I like the idea of moving history to the Windows Event Viewer. Are they serious? The location of "history" is the biggest thing they are worried about? How about they fix what they have before they rip away or add new features? How about leaning on your support forum for actual customer feedback? BTW, Windows Event Viewer interface is old and outdated. Why Microsoft has not changed the MMC interface is beyond me. I have to resort to LDAP queries and other scripts to properly search/filter event viewer at work and now Immunet wants to know if I'm ok with that on my home computer? No thank you. I would rather see some Cisco AMP for Endpoint features making their way into Immunet. I would like to know what my family members were doing on a computer when an incident occurs. AMP makes this very nice. This is a step forward. Windows Event Viewer is a step backwards. If Cisco is not willing to resolve the issues with Immunet and properly support the consumer base, then pull the plug and let it die. I really hope Immunet development continues and improves. Jasen
  29. 1 point
    This is so fun! I'll add it as a suggestion in an upcoming report I'm working on.
  30. 1 point
    I could be wrong but I doubt that the Emsisoft tool is causing this. Are all those temp files associated with the Sin Confirmar Spanish to English translation software? If that's the case you just might need to add a custom Exclusion rule or two to Immunet.
  31. 1 point
    I do have something else that comes to mind actually. It has been reported on numerous occasions that users of laptop, netbook, tablet PC"s or monitor that have a 4k screen resolution cannot easily (if at all) use Immunet's UI since it's so small. This must be something that is hard to fix since it's been a known unresolved issue for some time. If it's impossible for Immunet to be coded to automatically recognize the screen resolution a user has then would it be possible to add an extra toggle switch in Settings to go from normal to a up-scaled UI that 4k users can easily access? Another idea for you guys to make the product that much better if possible! After all, the more users in the cloud community the better the efficacy for everyone! Cheers, Ritchie...
  32. 1 point
    And also got this on one of the multiple attempts to submit:
  33. 1 point
    Hi Immunet_UX, I posted a topic to include a VPN service with Immunet a while back. Here is a link to the original topic. https://support.immunet.com/topic/4437-include-a-vpn-service-with-immunet/ The reason why I'm mentioning this again is that with the covid-19 pandemic still occurring many more people are working from home, doing on-line shopping or banking then ever before! My idea was to create a new Plus (paid) version to include this service. I do have another idea. Why not also include the TETRA module to this new Plus version as well. The old Plus version gave users the option to use this engine so I bet it wouldn't be that hard to include this engine once again. Could end up being a money maker for Cisco I think! It is a fact that Immunet's user base was consistently much larger when a Plus & Free version was offered to the public. What ever the outcome is I am glad to hear that Immunet is not being scrapped and l honestly look forward to working with you and your team in the future. Regards, Ritchie...
  34. 1 point
    It seems that immunet is maintained by Cisco Talos Intelligence, they have social media, or you can tweet immunet on their own Twitter account.
  35. 1 point
    Hi Gordon, You're just one of many that have run into this same update/connection bug with the 7.3.0 build unfortunately. I use Immunet as a companion AV to another paid AV product. For that reason I didn't use the ClamAV module so that's never been a problem for me. However I did like the added security that the ETHOS & SPERO cloud engines provided. After I noticed that cloud lookups were not taking place I had no other choice but to uninstall Immunet for now. I mean, why keep an app installed that is essentially useless! So now I'm waiting for the developers to fix this issue before I reinstall Immunet again. What's particularly disconcerting for me is that no admin or dev seems to want to even take the time to look into this or let users know they're working on it. "I hate to sound so pessimistic but your guess is as good as mine when/if this bug will be adequately resolved regrettably!" I know Cisco has made Immunet a "Low Priory" project but this is getting absolutely ridicules how long it's taking in my honest opinion! Has Immunet become complete ABANDONWARE? I'm starting to have my suspicions and this ongoing scenario is really starting to bum me out! I've been involved with this project for over 10 years now and "this is the worst situation I've encountered in all that time!" If things don't improve soon I'm not sure how much longer I will wish to stay involved with this software. What's the point of helping to support abandonware that no longer even works properly? Frustratingly, Ritchie...
  36. 1 point
    I just made a post on how to open the IP Ranges for "updates" and "cloud connectivity" and how to get exact IP addresses if you don't want to open up the whole range. It's posted under "General" and titled "IP Ranges" if your issue is something else, I'm about to make a quick white paper on how to fix update hiccups.
  37. 1 point
    Tried virus samples from https://www.eicar.org/?page_id=3950 and online scaner did not work!
  38. 1 point
    Ritchie - I've added the three products to the firewall allow rules - no change. Rebooted, the device, double checked to make sure the firewall rules were still in place - they were. The application keeps telling me I need to update and there's no update available.
  39. 1 point
    This Problem is a error of Immunet and not a server Problem. The ClamAV 0.102.1 provided by Immunet is outdated and the current version is 0.102.3. This is also reportet by C:\Program Files\Immunet\clamav\0.102.1.76\freshclam.exe and freshclam.exe cancel the update after the download of the first "cvd" it get. ClamAV do that to prevent using a old engine with new Database files. Freshclam.exe have problems to download and also cant update complete downloaded files. Solution 1 Download clamav-0.102.3-win-x64-portable.zip from https://www.clamav.net/downloads#otherversions Stop the Immunet Service --> net stop ImmunetProtect_7.2.8 Delete old Database files bytecode.c*, daily.c*, main.c*, lastupd and update.log Extract the files to C:\Program Files\Immunet\clamav\0.102.1.76 Start the Immunet Service --> net start ImmunetProtect_7.2.8 Start Immunet, Click on Update Now and wait a moment (if Update does not start repead it after a min.) The download location is configuratet in the file freshclam.conf, if you need to use a other mirror change it in this file. Solution 2 Immunet need a Update to new ClamAV version 0.102.3.x What a disgrace from Immunet
  40. 1 point
    Personally, I've never seen the cloud stat issue go unresolved this long after a new build is released. Now users are reporting update issues too. Are these related or what? "Hello, is there anybody out there!!!"
  41. 1 point
    I used Immunet alongside Sophos Home for maybe a year on a Windows 10 rig. It was probably the most stable and quick combination I've ever used - and that was with the ClamAV engine enabled as well! They never clashed once, even on files they could both detect. For ages I never bothered adding each to the other's exclusion list, and they played fine together. I eventually added each one's "program files" folders to the other's exclusion-list, when Sophos eventually got a false positive on one of Immunet's temporary files (I had ClamAV enabled). I think I also had to add another Sophos folder (somewhere inside "c:\programdata") to Immunet's exclusions. The combo was great and never gave me an issue once. Speed was similar to running just Windows Defender. The only way I could get quicker performance was to turn off ClamAV or switch to running just Kaspersky or F-Secure on its own.
  42. 1 point
    Thanks everyone for their input. In my test environment I'm seeing no issues between the two applications as of yet. Sophos Home Pro and Immunet are functioning without any added configuration to quell any false positives. So far so good!
  43. 1 point
    Thanks Richie, as you know Immunet uses the 'Cisco AMP for Endpoints' scanning and detection engine, which is how it appears as the process on a windows system. This is indeed an immunet issue.
  44. 1 point
  45. 1 point
    Hello Diego, Immunet protection improved a lot with the lastest updates. You can use it alone or with another antivirus if you wish. For a normal user Immunet can offer proper protection by itself. This is a video from a test some guy made using Immunet.
  46. 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.
  47. 1 point
    Sorry to hear you had a bad experience with Immunet. Did you create an exclusion rule for Malwarebytes entire Program Files folder with Immunet & create a exclusion rule for Immunet with MB? That can go a long way in avoiding possible conflicts when running Immunet as a companion AV to another product. Like you mentioned, it could also be that your older computer just doesn't have the system resources needed. Especially if it's older SDRAM or DDR memory modules 3 gigs of RAM really isn't that much memory these days as software increasingly becomes more complex requiring more RAM & CPU cycles. I seen this happen to a friend of mine a number of years back. He was using an older rig with Win XP installed. After upgrading to a newer version of Immunet at that time he discovered that his old computer would just shut down after boot-up because "all available SDRAM memory was being used up!" I had to help him uninstall Immunet by using Safe Mode. Immunet no longer supports Windows XP since version 5 was first rolled out. I'm sure you're also aware that Microsoft no longer supports Windows 7 with security updates, bug fixes and system upgrades. That means as time goes by your computer will become more vulnerable to malware, viruses and hackers. Maybe it is time to consider getting a newer rig briab. Regards, Ritchie...
  48. 1 point
    Hello Damokles and thank you for your interest in Immunet, Not sure what you mean by making a complete list. Immunet originally was strictly just a cloud based AV when it was first introduced. The draw back to that was Immunet had to have a constant internet connection for cloud based lookups during normal operation & during a scan. Also there was no off-line scanning capabilities. After the introduction of the open-sourced signature based ClamAV into the program that not only added an additional layer of off-line protection but also added the ability to run scans even if no internet connection is present as it works as a traditional downloaded malware definition signature based AV. You can use just the scalable multi-threaded ClamAV scripting code http://www.clamav.net/ as an automatic or on-demand AV scanner & a email gateway scanner for instance. ClamAV does not have a UI in the traditional sense since everything is handled through Command Line scripts. Of course Immunet provides a traditional UI to users without the need for advanced technical skills to configure or use since ClamAV's scripts are integrated into Immunet's program code via the ClamAV module. Immunet can be used as a "stand-alone" AV solution. If used in this manner it is recommended that the ClamAV module & updates for it be enabled. If Immunet is used as a companion AV to a compatible paid product it is recommended that the ClamAV module remain disabled. This improves the amount of system resources being used. Immunet will work with Defender. Using them both should provide good malware protection for the average user. In fact Immunet has, by default, an exclusion for Defender for improved compatibility. If using Immunet with Defender I would consider "not disabling" the ClamAV module for the reasons described below. Adding an exclusion/exception rule to Defender for Immunet's Program Files folder is also very highly recommended. That way they recognize each other as safe programs and goes a long way in avoiding possible future conflicts. If I "had to choose" one or the other I would definitely go with Immunet over Defender. Microsoft even admits that Defender is meant for users that don't have or don't want to use a different AV solution. Although some improvements have been made with newer builds Defender still is not a stellar anti-malware program as it provides basic protection. The Plus version of Immunet is no longer available. Immunet Protect Free is just like the name implies, it's totally free for individual/home or private network use and for "non-profit" charitable or educational organizations! Immunet is not licensed for any "for profit" business, service, organization or product. If it's found that Immunet is being used in such a manner no support will be offered. This information is included in the End User License Agreement (EULA) when first installing Immunet. We recommend that any for-profit entities use Immunet's paid Enterprise version called AMP for Endpoints. https://www.cisco.com/c/en/us/products/collateral/security/fireamp-endpoints/datasheet-c78-733181.html I hope this answers your questions. Regards, Ritchie...
  49. 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.
  50. 1 point
    A lot of users have a third part firewall running which is a great idea but sometime some problems between the firewall and Immunet happens. Most software based firewalls will automatically ask if you want to allow Immunet passing through but a few dont. The few software based firewalls and most hardware based firewalls who dont allow Immunet to run probably need to be configured to allow Immunet to communicate with the cloud. To allow connection to the internet you need to allow or open a few ports that are being used by Immunet. The port number used for cloud communication are: 80 - TCP (HTTP) 443 - TCP (HTTPS) 32137 - TCP. 53 - UDP is needed for DNS lookup. So keep those ports open for Immunet in software and hardware based firewalls. (Hardware based firewalls are often built-in in routers and modems).
×
×
  • Create New...