assets |
|
|
content |
|
|
GuardianClient.sys.mjs |
An HTTP Client to talk to the Guardian service.
Allows to enroll FxA users to the proxy service,
fetch a proxy pass and check if the user is a proxy user.
|
15920 |
IPPChannelFilter.sys.mjs |
IPPChannelFilter is a class that implements the nsIProtocolProxyChannelFilter
when active it will funnel all requests to its provided proxy.
the connection can be stopped
|
4459 |
IPProtection.sys.mjs |
IPProtectionWidget is the class for the singleton IPProtection.
It is a minimal manager for creating and removing a CustomizableUI widget
for IP protection features.
It maintains the state of the panels and updates them when the
panel is shown or hidden.
|
10188 |
IPProtectionPanel.sys.mjs |
Manages updates for a IP Protection panelView in a given browser window.
|
11234 |
IPProtectionServerlist.sys.mjs |
This file contains functions that work on top of the RemoteSettings
Bucket for the IP Protection server list.
|
2417 |
IPProtectionService.sys.mjs |
A singleton service that manages proxy integration and backend functionality.
It exposes init and uninit for app startup.
@fires event:"IPProtectionService:Started"
When the proxy has started and includes the timestamp of when
it was activated as `detail.activatedAt`.
@fires event:"IPProtectionService:Stopped"
When the proxy is stopped
@fires event:"IPProtectionService:SignedIn"
When user signs into their account
@fires event:"IPProtectionService:SignedOut"
When user signs out of their account
@fires event:"IPProtectionService:UpdateHasUpgraded"
When the hasUpgraded property is updated.
True if the user upgraded to a Mozilla VPN subscription.
@fires event:"IPProtectionService:Error"
When there has been an error
|
17095 |
IPProtectionUsage.sys.mjs |
Service Class to observe and record IP protection usage.
When started it will observe all HTTP requests and record the
transfer sizes of requests and responses that are proxied through
the IP protection proxy.
It should be started when the IP protection proxy is active.
It should be stopped when we know all proxy requests have been completed.
It will record all Proxied Requests that match the isolation keys.
So after a connection is established, the isolation key should be added.
|
3141 |
jar.mn |
|
1280 |
metrics.yaml |
|
2658 |
moz.build |
|
780 |
tests |
|
|