Yep definitely bug. And I also hope that comodo will add more option under password protection, for ex. if you disable the protection require password(witch is good), but if you re-enable the protection no need to enter a password for this, this isn’t the purpose of password protection, honestly.
The password protection is to protect the system from unauthorised users changing or disabling settings, which then could allow malicious actions to take place.
If the suppress alerts (Auto block) function is unavailable, then alerts would need to be password protected IMO.
Without this what is the point of password protection if unauthorised users can just bypass the alerts and password, allowing any type of activity regardless of the configuration settings?
....this isn't the purpose of password protection, honestly.
Honestly what is the purpose of the password protection?
I apologise if I am wrong, but I still say this is by design even if it is lacking configurable functionality.
Well don’t get me wrong, my point was clear, comodo should add more option under password field. Well imagine you enable the password protection, just to protect the setting, and instead you will have to enter the password for every alert, believe me at some point this will start to annoy you. And if you re-enable protection no need to input password, since this isn’t a security issue, but the contrary. Look at avast free for ex. if you had pass protection enable, if you disable all shield, or one, it will ask to input password, but if you decided to re-enable protection it won’t ask you to re-type password, since is a good thing. Same thing on ‘‘check for update’’. If more option will be added you could chose what and when you should enter the password, so I don’t think my point was wrong. :-\
This bug/issue/design is about security alerts, nothing more nothing less.
I agree the password management in its current form does lack options and functionality.
Could it do with some improvements? IMO yes, which we both agree on.
Is lack of options and functionality a bug? IMO no, this is lack of design and sounds like a wish.
We should also have password requirements (Optional) for updates or any configuration changes.
An example is currently happening with V6, one update caused issues for some users.
An admin (Password holder) might prefer to disable and postpone updates until the issue is rectified.
We are either looking at this slightly differently to each other, or we do not totally agree.
Either way I am happy to agree to disagree.
Apologies for letting this run of topic away from password requirements for security alerts.
Captainsticks you done the right thing and thank you for making me think and check so I don’t waste Comodo staff and my time further if it turned out not to be a bug. You don’t need to apologise for anything in fact thank you for getting involved ;D :-TU
Yes thank you very much Seany, the report is just great now.
Regarding the great debate, I’d say as stated it’s an ‘issue’ and so valid in this forum in any case, rephrased as ‘loss of configuration of password protection from version 5.x’ it’s probably unintended and so crosses the line into being a bug.
But it’s all pretty subtle , and does not matter greatly. It’s a problem that needs fixing, probably through re-instating the configurability (as there are security reasons for some form of protection on elevated privs alerts).
Thank you, that’s a relief. If the next release will be out in about a month, then CIS will protect my pc, I hope once and forever. My only hope is to have releases with less issues as possible. Again !ot! but is a good news for me, because I use password protection so
Thank you very much for your report in standard format, with all information supplied. The care you have taken is much appreciated by Comodo, and will increase the likelihood that this bug can be fixed.
Developers may or may or may not communicate with you in the forum or by PM/IM, depending on time availability and need. Because you have supplied complete information they may be able to replicate and fix the bug without doing so.