Exciting News: Comodo Internet Security 2024 Beta Now Open for Testing!

Thanks Infosec for the detailed response

There might be a solution:

This would consist of using only a non-public trusted authority (CA) (in other words limited to the information system (PC)) and avoiding CAs natively integrated into the proxy. Use a key protection system (like HSM) and run the proxy in the Comodo sandbox so that no information comes out of there. CIS analyzing on the fly in the Sandbox.

Additionally, for some time now, hackers have been using encrypted streams to pass the offensive charge under the radar and out of sight.

I know, you are going to tell me: as soon as the charge takes action CIS will block it…

Is reading all of my bank’s PDFs a hostile action?

I have a question :

Is Comodo CIS looking for the possibility that Internet or network streams can be decrypted on the fly on the PC, via proxy or not?

Speaking of which… What is libssl32.dll or libssl64.dll?

I would like to know more and see what is happening on my PC regarding the subject.

Do you think the following sites are safe to perform these tests? :

  1. https://testsafebrowsing.appspot.com/

  2. https://www.ssllabs.com/ssltest/viewMyClient.html

Hi @ilgaz ,

could you help me?

hi @Avos-New-Forum , yes it will be fixed.

1 Like

Thank you very much.
I await with confidence :+1:

Hello, CIS lovers,
Our next beta release plan has been finalized and we’ll share the new beta version on October 23rd, 2023.

Here is the list of bug-fixes that we’ll cover with the new beta version:

  • Fixed an issue where icons in the taskbar disappeared after Explorer.exe restarted.
  • Fixed the issue of missing the “Log as firewall event if this rule is fired” option on the firewall rule screen.
  • Fixed issues with performing Quick Scan, Full Scan, and Rating Scan and errors related to updating the last scan date.
  • Fixed the “Report a Bug” link being incorrect, outdated.
  • Fixed an issue with the first beta version, which had compatibility issues with Win 11 x64 after installation and uninstallation, where the internet connection would be interrupted and a popup would appear in the CIS tray saying "The network firewall is not functioning properly”.
  • Fixed an issue where clicking on the scan exclusion under advanced protection would crash the entire advanced settings window/menu.
  • Fixed an issue where the antivirus still appeared to be running despite disabling all components in CIS and could not be disabled.
  • Fixed the “TDT agent is not working” issue.
  • Fixed the “Intel TDT driver not loaded” issue.
  • Fixed the issue of displaying the IntelTDT options on the UI with not supported CPU. If the CPU does not support TDT, it will be written to the log, and then unload tdt.dll. Users will be able to manually delete TDT’s log files.
  • Fixed an issue with CIS crashing after uninstalling the old version and installing the new beta version.
  • Fixed an issue where firewall settings caused the internet connection is being cut after installation of CIS 2024 Beta.
  • Fixed issues with cmd/diskpart or diskadminisration such as not being able to clean up all or create new volumes and formatted/deleted data/files restoring themselves after formation.
  • Fixed translation errors in Russian, French, Polish, Italian and Portuguese.

Problems with Killswitch, Cleaning Essentials, recognizer, and updater will also be fixed.

Thank you for your patience, we look forward to seeing the results of your experience with the new beta.

Kind regards,
Comodo Team

13 Likes

I don’t know what to do with this, for example :wink:

C:\ProgramData\comodo\Cis\tempscrpt\C_powershell.exe_806C4F4A619CD1C9927A6A5F237CABF3BCB036F3.ps1
containing :
“Get-PhysicalDisk | Select BusType | ft -HideTableHeaders”

I don’t know who created it, when, or what it does.
Sometimes it’s understandable, others… not at all.
So, it’s very nice to warn about powershell tempscripts (or others?), but it would be even nicer if we knew where this is leading us…

Bravo to the whole team for this overhaul!

Hello kindly whether it is worth waiting for the new CIS 2024 Beta I am very happy with this information and thank you to the Comodo team for improving the Polish language errors with uncommonly waiting for Beta greetings from Poland.

Good morning,
There is a big problem regarding process control under CIS (beta).
Let me explain :
Since updating from Windows 10 to Windows 11 did not work with CIS, I disabled CIS from startup with Revo Uninstaller.
Failure.
Then, I completely uninstalled CIS with the Comodo utility and also with Revo for potential “leftovers”.
So, no more CIS at all.
So the update to Windows 11 worked.
Once on Windows 11 Pro (64), I wanted to reinstall CIS.
The installation went well, he didn’t notice anything or indicate anything.
But now, being used to the software, I noticed that things were not going right.
After several unsuccessful attempts at the diagnostics function, I tried several reinstallations. Without success either.
Then, I had the idea to look at the functions of controlling the users when starting Revo Uninstaller. The entries that I had blocked in Windows 10 to allow the system update were still blocked…

After checking them so that they are at the next startup, the installation worked and so did CIS.

I conclude the following:

  1. Any process can very easily prevent CIS from returning to the next boot
  2. CIS does not know how to realize that it will be blocked at the next boot
  3. CIS does not know how to reactivate at the next boot
  4. The installation of CIS does not notice the problem either and does not restore the start of the program to boot.
  5. But even worse… the diagnosis doesn’t know how to do it either…
  6. And don’t notice it either

It would still be super cool to correct this on this version.
With all the most sincere thanks in advance.

FYI, the CIS config was locked by a password.

I tried to do the same with another antivirus, sure enough, it came back perfect on reboot.

There is also the fact that Comodo CIS files should only belong to Comodo.

I was able to add Killswitch too easily (when it didn’t work on the first beta). The one I added is positive by 7 antiviruses on virustotal. I think I could have even added another exe and named it KillSwitch.

If we can so easily replace the official exe of the current version, this could open the way to out-of-control vulnerabilities.

It is just my humble opinion…

Otherwise… CIS cleanup tools does not uninstall Comdo Secure Shopping which remains in place after uninstalling CIS.
And Comodo SHopping works alone with its environment.

image

Sorry to keep coming back, but the beta testing period doesn’t last forever.
So I communicate everything I notice.
So… something else:
When you install the official version of CIS Pro, it starts doing an update as soon as the installation is complete, then a quick scan, then offers to restart the computer to complete the installation process.
With the beta version, I didn’t see an update starting automatically, nor an analysis, and not a reboot request each time.
However, I installed it several times…

1 Like

Good morning,

A few messages above, I reported CIS malfunctions, particularly on the interface.

I was told that it was due to my configuration.

I’m a little disappointed…

According to you, from Spectrum, Oric, MSX, Atari, Windiows 3.1, 95, NT 4.0 to Windows 10 (and 11), how many software(s) have had their appearance broken by user configuration or by the presence of other software?

And how many times have I been told that in fact…it was my fault…?

I really don’t think this way of doing things is reassuring…

Since, in my opinion, I was not answered correctly, and if I were part of the software quality department, I would not let this pass, but also, because I really and honestly want CIS to really come out at its best of this beta, I cannot give up asking this question:

How is it that an external event (config, other software) can so easily intervene IN Comodo CIS and change its appearance?

I, in your place, would not let this pass.

A derailed appearance doesn’t make for the best publicity.

Hello again,

There is also something that would also be nice to correct in CIS Pro.

This is the license activation system.
On the same PC, sometimes it works, sometimes it doesn’t work.

And each time, you have to wait days for the “Subscriptions Service” to sort out the situation.

Why not use another way of doing things, as the competition can do?

I upgraded from Windows 10 to 11 to be able to test Comodo CIS: impossible to activate the license! (It worked flawlessly under Windows 10)

I am restoring my PC from a backup: unable to activate the license.

Sometimes I even change the config in CIS: it’s impossible to activate the license.

Why not take the digital fingerprint of the PC?
or see on online management that only one PC is connected to this license?

I have the right to three licenses, only one PC tries to take advantage of it, but it doesn’t work!

Please try to see, for example, what Adlice is doing with its licensing system for RogueKiller. It works perfectly!

If we have installed one license too many, we will manage it on the console, we delete the old PC and everything is in order again.

It takes 5 minutes!

I think you also rely on the IP address to validate the licenses, because once I was asked for it to reactivate my license
And then, there are many countries where Internet Providers do not give a fixed IP address.
This manual license validation technique dates from a time when VPNs did not exist. Furthermore, what should we do with the laptops of people who travel a lot and whose IP address is constantly changing?

The Comodo “subscriptions” team (in my opinion “the person”) should not be fired. She is to be promoted for having lasted so long with such boring work!

Likewise, after a System upgrade, the files being the same, except those brought by the system update, is it really worth letting CIS scan all the hard drives again for hours, while it already done it during license validation under Windows 10?

Why do you need to reactivate the license during a system upgrade?

Why not take the SHA256 fingerprint of the files to avoid a long and restrictive re-scan?

I really hope that with this new 2024 version, which looks very good and will be, you will have so many sales that it will be impossible to manage licenses by hand as you still do!

Best wishes and thank you in advance for thinking about it…

Where are the promised bug fixes of the bugs on the List of current bugs ?

4 Likes

Here I am, 12+ years later, hoping for a usable product, and yet this “beta” is nothing better than an “alpha”.
I REALLY want Comodo AV / Firewall to succeed, but until QC and UAT improve to an acceptable level, both the users and developers will remain very frustrated…

1 Like

Hi Varan-de-C0m0d0,

Thank you for reporting.
We will check and report this to the team.

Thanks
C.O.M.O.D.O RT

Good morning,

Thanks C.O.M.O.D.O RT

News of the day:

  1. CIS heats my SSD up to 90 degrees!

  2. Before CIS, computer shutdown: 4 seconds
    With CIS 10 minutes (What does he do during this time?)

  3. On Windows 10 and Windows 11, I thought it was functional (everything was green), but there was no indication that it was not. Why at the end of the installation and periodically during a quiet period for the PC, would CIS not do the check (Diagnostic) itself to ensure its status?

  4. CIS creates a duplicate profile of the real browser profile.
    For what ?

  5. For me, the quick scan is extremely fast, to the point that I seriously question whether it really works. Idea: It would be nice to bold the letters indicating that the analysis is complete

  6. Idea: Why not use the same active circle graph (the same as the analyses) during updates?

  7. Impossible to save or load a config, access to the disk is refused (CIS is however alone on the PC)


Picture : Impossible to save or load a config, access to the disk is refused (CIS is however alone on the PC).

I noticed that this happened after restoring the system with a backup. At this point, the system disk is no longer encrypted by Bitlocker. I don’t know if there is a cause and effect link.

Still, with Bitlocker activated, no problem with CIS on this and with a restoration without Bitlocker, problems.

I also wondered if CIS was not partly (even very small) coded in 16 bits (the main part in 64 bits, a part in 32 and a whole part in 16 bits).

For what ?

I saw truncated file names, like in the past on much older Windows. This did not happen before installing CIS.

  1. A quick pass under Ashampoo WinOptimizer allowed me to see that the uninstaller provided earlier on this page leaves some residue.
    But also, after uninstalling, I sometimes have oem42.inf, eom107.inf, oem42.inf, oem.88.inf. Sometimes only two of them remain after uninstallation. So I think that the uninstallation utility must adapt to the Beta version…

  2. It looks like you have telemetry set up to see what’s happening with beta installs, correct?
    Is private information circulating? I live in the European Union, the rights to private data are not the same. It is more restrictive.

  3. Without CIS my SSD lost 37 degrees… phew!

  4. Are so few of us testing the beta version?


Note: My system is clean (Windows 11 Pro (64)

and SFC /SCANNOW does not find any errors

UAT = User Acceptance Test
QC = Quality Control

Helo Cavehomme !

I completely agree with you = it’s an Alpha release and I just wasted over two weeks trying to get it working for them.
In addition, I find myself on Windows 11 “because CIS had been even better adapted to Windows 11”, which is what I didn’t want! :stuck_out_tongue_winking_eye: :crazy_face: :nerd_face: :sob: :sob: :sweat_smile:

I trusted, I regret. If they had openly said it was an Alpha that could crash the system, I would have installed it on a specific PC.

I was a little naive on this one… It’s not for lack of having participated in other betas from other publishers…