Author Topic: Feedback on Help, FAQs and Guides  (Read 50606 times)

Offline mouse1

  • Global Moderator
  • Comodo's Hero
  • *****
  • Posts: 11856
Feedback on Help, FAQs and Guides
« on: March 11, 2010, 02:42:11 PM »
Please post in this topic any suggestions you may have for improvements to the FAQs or any introductory topics, for example the "Introduction to the Sandbox" topic.

Please do not post requests for help here
« Last Edit: May 23, 2013, 06:36:41 AM by mouse1 »

Offline mouse1

  • Global Moderator
  • Comodo's Hero
  • *****
  • Posts: 11856
Summary of Feedback/Issues to deal with
« Reply #1 on: March 16, 2010, 04:53:53 AM »
Summary of things that may need to be dealt with either in the intro to the sandbox or in the FAQ.

(Short notes only)

Done
- interaction with D+ (FAQ entry Done)
- why sandbox is like it is & will work on 64 bit (DONE)
- OS files being sandboxed (DONE)
- how sandbox decides something is an installer (DONE)
- what is virtualised (registry, files) (DONE)
- What happens if a file is detected as malware after submission by sandbox (DONE)
- What happens to sandbox on XP 64bit (DONE)

To do

« Last Edit: July 02, 2010, 06:31:12 AM by mouse1 »

Offline JoWa

  • Global Moderator
  • Comodo's Hero
  • *****
  • Posts: 5938
  • I believe in doubt.
    • Evolutionary history of life
Re: Introduction to the Sandbox - Feedback
« Reply #2 on: March 20, 2010, 01:44:31 AM »
Quote
Will the Comodo sandbox work on 64bit systems?

Yes it will (with the exception of 64bit Windows XP).

This is one of the main reasons why it is designed as it is. Most sandboxes will not work on 64 bit systems because they use undocumented calls (which are not supported in 64bit) to intercept program to program communications. The CIS sandbox avoids this by not sandboxing installed executables, which means it does not need to intercept these communications.
https://forums.comodo.com/defense-sandbox-help-cis/introduction-to-the-sandbox-t53268.0.html

I don't understand the bold part… :-\

And the “undocumented calls” are not supported in Windows 32 bit.
Quote
"Patching the kernel" refers to unsupported modification of the central component or kernel of the Windows operating system. Such modification has never been supported by Microsoft because it can greatly reduce system security and reliability. However, though Microsoft does not recommend it, it is technically possible to patch the kernel on x86 editions of Windows. But with the x64 editions of Windows, Microsoft chose to implement technical barriers to kernel patching.
http://en.wikipedia.org/wiki/Kernel_Patch_Protection

Or does “use undocumented calls” not mean patching the kernel? ???

Thanks. :)
Ubuntu 19.10 | Firefox 70β | HTTPS Everywhere | Privacy Badger
Forum Policy | Comodo Product Help

Offline mouse1

  • Global Moderator
  • Comodo's Hero
  • *****
  • Posts: 11856
Re: Introduction to the Sandbox - Feedback
« Reply #3 on: March 20, 2010, 02:57:32 AM »
First comment! Thanks Jowa

You are right about the word 'supported', a lazy/vague word. I'll replace it by 'Do not work'.

And I'll replace 'not sandboxing' by 'not making virtual copies'. Hope that will make things clear. I'll be putting up a virtualisation FAQ entry today too - so any comments will be welcome.

As for kernel patching, I'm afraid I'm not competent to comment. Maybe Egemen will when he gets back from China!

Best wishes

Mouse

Offline JoWa

  • Global Moderator
  • Comodo's Hero
  • *****
  • Posts: 5938
  • I believe in doubt.
    • Evolutionary history of life
Re: Sandbox help materials - Feedback
« Reply #4 on: March 20, 2010, 05:29:59 AM »
Thanks Mouse. :)

Now I think I understand… When I sandbox e.g. IE, iexplore.exe is run from C:\Program\Internet Explorer\, not copied to C:\Sandbox\iexplore.exe\… and run from there. That folder is only used for files created or modified when running IE. And HKEY_LOCAL_MACHINE\SYSTEM\Sandbox\iexplore.exe\ for registry keys created or modified when running IE.
Ubuntu 19.10 | Firefox 70β | HTTPS Everywhere | Privacy Badger
Forum Policy | Comodo Product Help

Offline mouse1

  • Global Moderator
  • Comodo's Hero
  • *****
  • Posts: 11856
Re: Sandbox help materials - Feedback
« Reply #5 on: March 20, 2010, 05:42:43 AM »
That's exactly it!

Glad the FAQ works. All suggestions for improvments welcome

Mouse

Offline JoWa

  • Global Moderator
  • Comodo's Hero
  • *****
  • Posts: 5938
  • I believe in doubt.
    • Evolutionary history of life
Re: Sandbox help materials - Feedback
« Reply #6 on: April 07, 2010, 02:46:37 AM »
Maybe add information about what happens when CIS 4 is installed on XP x64? Is sandbox automatically disabled?

Thanks. :)
Ubuntu 19.10 | Firefox 70β | HTTPS Everywhere | Privacy Badger
Forum Policy | Comodo Product Help

Offline mouse1

  • Global Moderator
  • Comodo's Hero
  • *****
  • Posts: 11856
Re: Sandbox help materials - Feedback
« Reply #7 on: April 07, 2010, 03:27:41 AM »
Good point. I don't know, but Egemen will. I'll ask and add this.

Mouse

Offline mouse1

  • Global Moderator
  • Comodo's Hero
  • *****
  • Posts: 11856
Re: Sandbox help materials - Feedback
« Reply #8 on: April 14, 2010, 03:56:18 AM »
Maybe add information about what happens when CIS 4 is installed on XP x64? Is sandbox automatically disabled?

Thanks. :)

No response yet I am afraid Jowa. Hopefully will get one post the .828 release.

Offline mouse1

  • Global Moderator
  • Comodo's Hero
  • *****
  • Posts: 11856
Re: Sandbox help materials - Feedback
« Reply #9 on: May 03, 2010, 09:09:24 AM »
Intro now updated to reflect what happens in the case of 64bit XP

Mouse

Offline JoWa

  • Global Moderator
  • Comodo's Hero
  • *****
  • Posts: 5938
  • I believe in doubt.
    • Evolutionary history of life
Re: Sandbox help materials - Feedback
« Reply #10 on: May 03, 2010, 12:30:02 PM »
Thanks. :)
Ubuntu 19.10 | Firefox 70β | HTTPS Everywhere | Privacy Badger
Forum Policy | Comodo Product Help

Offline mouse1

  • Global Moderator
  • Comodo's Hero
  • *****
  • Posts: 11856
Re: Sandbox help materials - Feedback
« Reply #11 on: May 03, 2010, 03:39:17 PM »
My pleasure

Offline Kimodo

  • Newbie
  • *
  • Posts: 2
Sandbox locks down functionality of my machine -- cavalierly!
« Reply #12 on: July 01, 2010, 06:11:21 PM »
On the Sandbox Help -  Feedback page it says:
"Please post any suggestions you may have for improvements to the "Introduction to the Sandbox" topic.'
AND on the Introduction to the Sandbox page it says:
"Please help us improve this introduction by posting suggestions to the 'Sandbox help materials - Feedback topic'"

Get it straight, will you?

Here is what prompts me to write:   No product that has the potential to lock down functionality of my machine should be rolled out so cavalierly to users with built-out systrems.   

The implementation and roll-out of the SANDBOX feature in CIS is probably fantastic for machines with a fresh install -- the kind of machines that coders and computer scientists use that have only two or three apps on top of the operating system, and virtually no accumulated data files.  However, for an existing system which has an abundance of previously installed applications, and a superabundance of accumulated user files, it sucks!   

The Sandbox has grabbed my machine by the you-know-what, and is squeezing it hard.   It is interfering with things that constitute routine tasks for me, such as printing the screen to a .pdf-creating printer driver, and then really printing to a real printer  Users should be introduced to the Sandbox with some explanation that printer drivers may become dysfunctional, and some examples of the kinds of problems that commonly exhibit themselves when sandboxed apps cannot communicate with non-sandboxed applications. 

Tasks which have never given me any problems are suddenly failing to perform, and without any error message or anything to alert me to the failure.   Programs which automatically are put into the Sandbox and are supposedly being checked by Comodo for safeness, just sit there in the line to be checked.   And this is happening with programs on my machine which have been on the market for years.   Clearly, Comodo's whitlelist was developed by a kindergartner, and the company is using its customers as guinea pigs to build its whitelist for it.   If they are actually checking applications to determine their "safeness,"  I see no evidence of it.

There should be a knowledge base with KNOWN ISSUES on display.   When CIS and Sandbox are installed onto a machine with applications in place,  users should be shown a list of applications on their machine with explanatory details such as KNOWN SAFE, UNKNOWN, KNOWN HAZARD, etc., so that users can get some sense of how harshly their computer experience is going to be handled by COMODO'S SANDBOX, and some advisories about how to best manage the transition to having the Sandbox squeeze less harshly.   
I could keep on with suggestions, but if this rollout had not been handled by persons who are clearly indifferent to existing customers with mature, fully built-out systems, it would be unnecessary for me to be forced to waste my time holding their hands.   

Their management is clearly not up to the task of handling a rollout as complicated as what the Sandbox is.   

The same is also true of the Comodo AntiVirus.    Simple things -- like self-extracting zip files which I have created and stored -- are all, each and every one, being identified as potential problems when a scan is done by the Anti-virus checker.  Absurd to identify a self-extracting zip file as a virus, without letting the user specify that such a class of files should be skipped and presumed to be desirable, at least when they are located in certain folders.    Major things, like invisible system restore points, are being identified as infected with no clue as the crucial significance of those files being cleaned" or "quarantined." 

A user who is doing an upgrade of Comodo needs to be warned that CIS is going to take control of their machine and possible refuse to let it perform productively in ways that have become routine for the user, and safely so. 

Offline mouse1

  • Global Moderator
  • Comodo's Hero
  • *****
  • Posts: 11856
Re: Sandbox locks down functionality of my machine -- cavalierly!
« Reply #13 on: July 02, 2010, 05:58:02 AM »
On the Sandbox Help -  Feedback page it says:
"Please post any suggestions you may have for improvements to the "Introduction to the Sandbox" topic.'
AND on the Introduction to the Sandbox page it says:
"Please help us improve this introduction by posting suggestions to the 'Sandbox help materials - Feedback topic'"

Get it straight, will you?
Thanks, I have added 'in this topic' to the feedback topic to clarify matters

Quote
Here is what prompts me to write:   No product that has the potential to lock down functionality of my machine should be rolled out so cavalierly to users with built-out systrems.  

The implementation and roll-out of the SANDBOX feature in CIS is probably fantastic for machines with a fresh install -- the kind of machines that coders and computer scientists use that have only two or three apps on top of the operating system, and virtually no accumulated data files.  However, for an existing system which has an abundance of previously installed applications, and a superabundance of accumulated user files, it sucks!  

The Sandbox has grabbed my machine by the you-know-what, and is squeezing it hard.   It is interfering with things that constitute routine tasks for me, such as printing the screen to a .pdf-creating printer driver, and then really printing to a real printer  Users should be introduced to the Sandbox with some explanation that printer drivers may become dysfunctional, and some examples of the kinds of problems that commonly exhibit themselves when sandboxed apps cannot communicate with non-sandboxed applications.  

Tasks which have never given me any problems are suddenly failing to perform, and without any error message or anything to alert me to the failure.   Programs which automatically are put into the Sandbox and are supposedly being checked by Comodo for safeness, just sit there in the line to be checked.   And this is happening with programs on my machine which have been on the market for years.   Clearly, Comodo's whitlelist was developed by a kindergartner, and the company is using its customers as guinea pigs to build its whitelist for it.   If they are actually checking applications to determine their "safeness,"  I see no evidence of it.

There should be a knowledge base with KNOWN ISSUES on display.   When CIS and Sandbox are installed onto a machine with applications in place,  users should be shown a list of applications on their machine with explanatory details such as KNOWN SAFE, UNKNOWN, KNOWN HAZARD, etc., so that users can get some sense of how harshly their computer experience is going to be handled by COMODO'S SANDBOX, and some advisories about how to best manage the transition to having the Sandbox squeeze less harshly.  
I could keep on with suggestions, but if this rollout had not been handled by persons who are clearly indifferent to existing customers with mature, fully built-out systems, it would be unnecessary for me to be forced to waste my time holding their hands.  

Their management is clearly not up to the task of handling a rollout as complicated as what the Sandbox is.    

The same is also true of the Comodo AntiVirus.    Simple things -- like self-extracting zip files which I have created and stored -- are all, each and every one, being identified as potential problems when a scan is done by the Anti-virus checker.  Absurd to identify a self-extracting zip file as a virus, without letting the user specify that such a class of files should be skipped and presumed to be desirable, at least when they are located in certain folders.    Major things, like invisible system restore points, are being identified as infected with no clue as the crucial significance of those files being cleaned" or "quarantined."  

A user who is doing an upgrade of Comodo needs to be warned that CIS is going to take control of their machine and possible refuse to let it perform productively in ways that have become routine for the user, and safely so.  

Thanks for your suggestion regarding the knowledgebase. I believe there is one on the main Comodo site, but I suspect extra content may be needed. Meanwhile the best source of the information you request may be the application incompatibility topic here or the bug reports forum.

I am sorry you have had so many problems with CIS 4.x  - your comments regarding quality control will probably be best addressed if mentioned under Feedback: here - the chief executive of Comodo monitors this forum regularly.

Best wishes

Mouse
« Last Edit: July 02, 2010, 06:13:15 AM by mouse1 »

Offline Tech

  • Usability Study Member
  • Comodo's Hero
  • *****
  • Posts: 3027
Re: Slider controls (Sandbox and D+) - what effects do these have? (under dev)
« Reply #14 on: September 13, 2010, 11:51:28 AM »
The sandbox is not affected by the D+ security level slider
What do you mean?
The sandbox seems to be disabled by the system tray icon  ???

[attachment deleted by admin]
avast! team member
Save freeware snapshot technology of Comodo Time Machine. Vote!

 

Free Endpoint Protection
Seo4Smf 2.0 © SmfMod.Com Smf Destek