Questionable COMODO Actions

Comodo Internet Security - CIS Install / Setup / Configuration Help - CIS
#1

I tested COMODO Internet Security 7.0.313494.415 on a isolated, testbed computer, and also on several virtual machines. I don’t use Trusted Vendors, because I’m not going to have COMODO tell me who I should trust or not; so I turned that feature off, and deleted all the Trusted Vendors. I closed the GUI, but didn’t turn off CIS. I reopened CIS, went to the Trusted Vendor area, and before my eyes, @Last Software, Inc (a GOOGLE company) was added back in, despite me turning off Trusted Vendors. See attachment.

In version 6, when I imported an exported config, with messages from COMODO being turned off, it honored it. But in version 7 they over rode that, so I would get messages from COMODO. I had to go in and turn it off, again. Yes, it was turned off in the exported config, because when I’d rebuild my computer, I’d use the exported settings, and that item would be turned off.

COMODO IS V6 users are under the impression (just like me) that trusted.db houses the trusted files, and vendors.* houses information about the trusted vendors. After the above, I did some more digging, and found the files that a lot of COMODO users thought was new, are actually there in V6 also, as this shows:

C:\ProgramData\COMODO\Firewall Pro>dir
Volume in drive C is (MASKED FOR POST)
Volume Serial Number is (MASKED FOR POST)

Directory of C:\ProgramData\COMODO\Firewall Pro

03/29/2014 11:58 AM .
03/29/2014 11:58 AM …
03/14/2014 07:10 PM 45,056 cisboost.sdb
03/29/2014 10:25 AM 32,768 cisboost.sdb-shm
03/29/2014 10:14 AM 3,547,352 cisboost.sdb-wal
03/14/2014 07:10 PM 32,768 cisdata.sdb
03/29/2014 11:58 AM 647,168 cislogs.sdb
5 File(s) (MASKED FOR POST)
2 Dir(s) (MASKED FOR POST) bytes free

After the above, makes me consider even more seriously whether to stay with COMODO or not. I mean, come on:

  1. They add stuff in, even though I tell them I’m not using a feature.
  2. They turn on features that I had previously turned off.
  3. They are using two locations for trusted items, so it questionable what to back up.
  4. In order to properly back things up (*.db and the ProgramData location), and insure the backup copies aren’t corrupted, because they’re open for write access, you have to do mote than just tell the backup program to back stuff up, as the following shows:

WinZip(R) Command Line Support Add-On Version 4.0 64-bit (Build 10562)
Copyright (c) 1991-2013 WinZip International LLC - All Rights Reserved

Adding program files\COMODO\COMODO internet security\database\submit.n
Adding program files\COMODO\COMODO internet security\database\trusted.db
Adding program files\COMODO\COMODO internet security\database\vendor.h
The following file is open by another program. If that program
writes to the file while WinZip is zipping the file, the zipped
Adding program files\COMODO\COMODO internet security\database\vendor.n
file may be corrupt: “c:\program files\COMODO\COMODO internet security\database\vendor.h”.

Could not open for reading: “c:\programdata\COMODO\firewall pro\cisboost.sdb-shm”.

Adding programdata\COMODO\firewall pro\cisboost.sdb
The following file is open by another program. If that program
writes to the file while WinZip is zipping the file, the zipped
file may be corrupt: “c:\programdata\COMODO\firewall pro\cisboost.sdb”.

Adding programdata\COMODO\firewall pro\cisboost.sdb-wal
The following file is open by another program. If that program
Adding programdata\COMODO\firewall pro\cisdata.sdb
writes to the file while WinZip is zipping the file, the zipped
file may be corrupt: “c:\programdata\COMODO\firewall pro\cisboost.sdb-wal”.

Adding programdata\COMODO\firewall pro\cislogs.sdb
The following file is open by another program. If that program
writes to the file while WinZip is zipping the file, the zipped
file may be corrupt: “c:\programdata\COMODO\firewall pro\cisdata.sdb”.

The following file is open by another program. If that program
writes to the file while WinZip is zipping the file, the zipped
file may be corrupt: “c:\programdata\COMODO\firewall pro\cislogs.sdb”.

Total bytes=12978548, Compressed=1682402 → 87 percent savings.

Copying Zip file “f:$$backups$$tauri$$\wz_testtesttest.zip”.

Press any key to continue . . .

[attachment deleted by admin]

#2

I don’t use Trusted Vendors, because I’m not going to have COMODO tell me who I should trust or not …
so it seems you are right but is it a test version (7) ?

After the above, makes me consider even more seriously whether to stay with COMODO or not. I mean, come on:

  1. They add stuff in, even though I tell them I’m not using a feature.
  2. They turn on features that I had previously turned off.
  3. They are using two locations for trusted items, so it questionable what to back up.
  4. In order to properly back things up (*.db and the ProgramData location), and insure the backup copies aren’t corrupted, because they’re open for write access, you have to do mote than just tell the backup program to back stuff up, as the following shows:
    if comodo do something wrong it is the time to choose another product

I changed the color of your comments because I could not read them in yellow. Eric

#3

YOUR COMMENT: so it seems you are right but is it a test version (7) ?

MY COMMENT: There is no indication on the post where the download link is. So because of that, it can only be taken as a full version. If it is a test version, then COMODO is wrong again, for not indicating it.

============

YOUR COMMENT: if comodo do something wrong it is the time to choose another product

MY COMMENT: I’ve been testing others out, for some time. But, when I went from SYMANTEC to COMODO, it was after a year of testing others out, I don’t jump from one to the other without extensive testings. after decades in computers, it makes me insure that things are tested extensively. From COMODO V5 to V6, the amount of messages have become excessive. I’d see the same message for the same processes I previously had approved COMODO to remember.

#4

not indicating it means that something is wrong behind … better informed better protected.
In shorts, is version 7 like you expected it - finished and ready - ?

#5

I kind of think I am reading numerous possible issues all in one topic here, which kind of makes it a little hard to follow.
If you have found bugs or have wishes, please create a separate topic for each individual issue following the guidelines.
Bug Reports - CIS
Required Format For Reporting Bugs
Wishlist - CIS
Required Wish Format

Thanks.

Is CIS V7 ready for release, yes but all software will have issues/bugs and not be 100% suited to everyone’s personal preference.
Is CIS V7 finished, no because it is still being actively developed.

Kind regards.

#6

Thx captainsticks_answers clear & neat
:smiley:

#7

I did some more experimenting, on the Trusted Vendor issue. Here is what I did, and found out:

  1. Downloaded an SQLite GUI (that’s what the databases are) and installed it.
  2. Tested my steps above, where I deleted all vendors. The [at]Last Software, Inc reappeared.
  3. Disabled all stuff (HIPS, Sandbox, etc). There are services behind the scene that keeps the databases locked, even after CIS is shutdown.
    3.1. COMODO Internet Security Helper Service
    3.2. COMODO Virtual Service Manager
  4. Shutdown CIS.
  5. Fired up the SQLite GUI, and saw the [at]Last Software, Inc in the trusted vendor table.
  6. Deleted [at]Last Software, Inc via SQL.
  7. Started CIS, enabled all components.
  8. Looked at trusted vendor list, [at]Last Software, Inc wasn’t there, even after 10 minutes.
  9. Rebooted the computer.
  10. Looked at trusted vendor list, [at]Last Software, Inc wasn’t there.
  11. Looked at trusted vendor list, after 10 minutes, [at]Last Software, Inc wasn’t there.

This means there’s a bug in the Delete portion of Trusted Vendors.