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
Inactive Support Threads
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
Software
Browsers
Web Extensions
JShelter - JavaScript Restrictor
Message
<blockquote data-quote="ForgottenSeer 92963" data-source="post: 972020"><p>First of all good to see you are joining this forum. It is one of the best ways to get feedback on security/privacy, thanks for joining <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite130" alt="(y)" title="Thumbs up (y)" loading="lazy" data-shortname="(y)" /></p><p></p><p>In Dutch we have a saying based on 17th century sailing and trading history which says "the flag should represent the cargo". In branding this translates that the name of the product should represents its purpose/benefits (functional name) or relate to the user/life style group you are targeting (fantasy name).</p><p></p><p>I have a hard time discovering which assocations you used to come up with a name. When this extension modifies API's to prevent misuse, why did you call the extension "JAVASCRIPT SHELTER" in the first place?</p><p></p><p></p><p><strong>FEATURE REQUEST 1</strong></p><p>In stead of randomizing responses, which results in non-existing values making it very easy to fingerprint someone OVER DIFFERENT SESSION when combined with IP/address and/or GEO location, it is much better to hide in the herd.</p><p></p><p>Because data can be combined from different sources and some data categories are related, it is much better to hide in the herd using realistic most prevalent values than generating random return values. By reducing the precision of some API-results (e.g. time/geo) and providing most common or default values related to OS/rendering engine (chromium based/firefox/Safari)/browser language it is much harder to back track returning users.</p><p></p><p><strong>FEATURE REQUEST 2</strong></p><p>Allowing users to define which API's to block makes no sense, because most users don't know that plug-ins/accepts/navigator data can be combined from the user agent or are related to each other (e.g. geo location, time and language). In 9 out of 10 cases an average home user starts fiddling with these settings that user makes himself more unique and easier to track.</p><p></p><p>Presets should be based on functionality and risk of website breakage. A better approach would be to offer four levels of protection and allow a user to change this setting for a website: 0 = OFF for trusted websites, 1 = best for compatibility, 2 = balanced, 3 = best for protection</p><p></p><p>Regards Kees</p></blockquote><p></p>
[QUOTE="ForgottenSeer 92963, post: 972020"] First of all good to see you are joining this forum. It is one of the best ways to get feedback on security/privacy, thanks for joining (y) In Dutch we have a saying based on 17th century sailing and trading history which says "the flag should represent the cargo". In branding this translates that the name of the product should represents its purpose/benefits (functional name) or relate to the user/life style group you are targeting (fantasy name). I have a hard time discovering which assocations you used to come up with a name. When this extension modifies API's to prevent misuse, why did you call the extension "JAVASCRIPT SHELTER" in the first place? [B]FEATURE REQUEST 1[/B] In stead of randomizing responses, which results in non-existing values making it very easy to fingerprint someone OVER DIFFERENT SESSION when combined with IP/address and/or GEO location, it is much better to hide in the herd. Because data can be combined from different sources and some data categories are related, it is much better to hide in the herd using realistic most prevalent values than generating random return values. By reducing the precision of some API-results (e.g. time/geo) and providing most common or default values related to OS/rendering engine (chromium based/firefox/Safari)/browser language it is much harder to back track returning users. [B]FEATURE REQUEST 2[/B] Allowing users to define which API's to block makes no sense, because most users don't know that plug-ins/accepts/navigator data can be combined from the user agent or are related to each other (e.g. geo location, time and language). In 9 out of 10 cases an average home user starts fiddling with these settings that user makes himself more unique and easier to track. Presets should be based on functionality and risk of website breakage. A better approach would be to offer four levels of protection and allow a user to change this setting for a website: 0 = OFF for trusted websites, 1 = best for compatibility, 2 = balanced, 3 = best for protection Regards Kees [/QUOTE]
Insert quotes…
Verification
Post reply
Top
