WebAPI Manager
大小:0.37MiB版本:v 0.9.27更新时间:2018-02-14
Improves browser security and privacy by controlling page access to the Web API.
WebAPI Manager 的使用方法详解,最全面的教程
WebAPI Manager 描述:
用户数:617
分类:开发者工具插件
扩展大小:0.37M
最后更新时间:2018-02-14
版本:v 0.9.27
WebAPI Manager 插件简介:
这是来自Chrome商店的 WebAPI Manager 浏览器插件,您可以在当前页面下载它的最新版本安装文件,并安装在Chrome、Edge等浏览器上。
WebAPI Manager插件下载方法/流程:
点击下载按钮,关注“扩展迷Extfans”公众号并获取验证码,在网页弹窗中输入验证码,即可下载最新安装文件。
WebAPI Manager插件安装教程/方法:
(1)将扩展迷上下载的安装包文件(.zip)解压为文件夹,其中类型为“crx”的文件就是接下来需要用到的安装文件
(2) 从设置->更多工具->扩展程序 打开扩展程序页面,或者地址栏输入 Chrome://extensions/ 按下回车打开扩展程序页面
(3) 打开扩展程序页面的“开发者模式”
(4) 将crx文件拖拽到扩展程序页面,
完成安装如有其它安装问题,
请扫描网站底部二维码与客服联系如有疑问请参考:
https://www.extfans.com/installation/Web API Manager
===
Changes
---
- added ability to edit match patterns for existing rules (#76)
Overview
---
This extension allows users to selectively allow different hosts on the web
to have access to different types of browser functionality. Doing so allows
security and privacy sensitive web users to limit the attack surface presented
to websites, and to limit websites to the functionality they actually need
to carry out user-serving purposes.
Background
---
Web browsers gain staggering numbers of new features, without their users
knowing what new functionality is being pushed into their trusted base.
While some of this functionality is broadly useful for things commonly thought
of as "web" related, a large amount of it is useful in only rare situations,
if ever. Examples of this rarely-needed functionality includes the
low level audio synthesis capabilities of the [Web Audio API](https://webaudio.github.io/web-audio-api/),
the low level graphics capabilities of [WebGL](https://get.webgl.org/),
or the light sensing capabilities of the [Ambient Light Sensor API](https://www.w3.org/TR/ambient-light/).
Such complex-but-rarely-used functionality has been often used in attacks
on the security and privacy of the web.
Other functionality is frequently used by web sites, but for non-user-serving
purposes, like fingerprinting anonymous users and tracking them across websites.
Examples of such functionality includes parts of the [SVG API](https://www.w3.org/TR/SVG/),
parts of the the [Canvas Element](https://html.spec.whatwg.org/multipage/scripting.html#the-canvas-element)'s functionality,
and the [Beacon standard](https://www.w3.org/TR/beacon/), among many others.
This extension helps users stay private and secure online by limiting websites
to only the functionality they need, and prevent them from accessing rarely
needed and/or privacy violating functionality.
Functionality
---
The extension currently includes the following functionality:
* Creation of domain-specific functionality rules, based on host-matching
regular expressions.
* Blocking of functionality across all domains, with a fallback, "default"
blocking rule.
* A novel method of blocking functionality, designed to minimize the effect
of removing functionality on existing code that expects that functionality
to be in place.
* A categorization of approximately 1,400 JavaScript methods into 74 different
Web API standards (and, where appropriate, sub-standards).
* User feedback to alert users how many hosts are executing script every time
they visit a site, to ease the creating of new rules.
The following functionality is not currently implemented, but is being considered
for future inclusion:
* The ability to subscribe to blocking rule sets created by trusted third
parties, similar to the EasyList / AdBlockPlus model of rule subscriptions.
* Blocking property accesses on non-global structures through an additional
level of interposition on runtime created objects.
* Adding new Web API standards into the code base.
* Extend blocking to properties and events (currently only functions and
methods are interposed on).
Background
---
This extension is based on research conducted at the [BITSLab](https://www.cs.uic.edu/Bits/)
at the [University of Illinois at Chicago](https://www.cs.uic.edu/). Further
information on the measurements and techniques used in this extension can
be found in the following papers.
* Peter Snyder, Cynthia Taylor, and Chris Kanich,
“[Most Websites Don’t Need to Vibrate: A Cost–Benefit Approach to Improving Browser Security](https://arxiv.org/abs/1708.08510),”
in Proceedings of the [2017 ACM Conference on Computer and Communications Security](https://www.sigsac.org/ccs/CCS2017/), 2017.
* Pete Snyder, Laura Waitker, Cynthia Taylor, and Chris Kanich,
“[CDF: Predictably Secure Web Documents](https://www.cs.uic.edu/~psnyder/static/papers/CDF_Predictably_Secure_Web_Documents.pdf),”
in Proceedings of the [2017 Workshop on Technology and Consumer Protection](http://www.ieee-security.org/TC/SPW2017/ConPro/), 2017.
* Peter Snyder, Lara Ansari, Cynthia Taylor, and Chris Kanich,
“[Browser Feature Usage on the Modern Web](https://www.cs.uic.edu/~psnyder/static/papers/Browser_Feature_Usage_on_the_Modern_Web.pdf),”
in Proceedings of the [2016 Internet Measurement Conference](http://conferences.sigcomm.org/imc/2016/), 2016.