Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Security
Video Reviews - Security and Privacy
Qihoo Total Security- An initial test
Message
<blockquote data-quote="cruelsister" data-source="post: 555727" data-attributes="member: 7463"><p>Let's talk Java. The other day there was a Java update (to version 8 build 111). I have Java installed on my system and proceeded to the update routine. All went fine and it was updated BUT one file, deploy.jar was sandboxed and not allowed to proceed. First off, this is not an issue for a home user as deploy.jar is for installing Java over multiple endpoints; secondly why was it sandboxed (and it is ALWAYS sandboxed)? Simply because Oracle decided not to sign it!</p><p></p><p>Now whose fault is that? Comodo's because it isolated an unsigned script, or Oracle's because they are too lazy to sign the file?</p><p></p><p>The ONLY issues that one will have in updated applications while using Comodo is if the developer does not sign the updating routine. I'll be making a video with a tentative release date of November where it will be shown how to deal with stuff like this.</p></blockquote><p></p>
[QUOTE="cruelsister, post: 555727, member: 7463"] Let's talk Java. The other day there was a Java update (to version 8 build 111). I have Java installed on my system and proceeded to the update routine. All went fine and it was updated BUT one file, deploy.jar was sandboxed and not allowed to proceed. First off, this is not an issue for a home user as deploy.jar is for installing Java over multiple endpoints; secondly why was it sandboxed (and it is ALWAYS sandboxed)? Simply because Oracle decided not to sign it! Now whose fault is that? Comodo's because it isolated an unsigned script, or Oracle's because they are too lazy to sign the file? The ONLY issues that one will have in updated applications while using Comodo is if the developer does not sign the updating routine. I'll be making a video with a tentative release date of November where it will be shown how to deal with stuff like this. [/QUOTE]
Insert quotes…
Verification
Post reply
Top