https-everywhere VS cli

What's the issue with Firefox's implementation? And this doesn't change the fact that HTTPSe is literally fully sunset.

Here's a small historical curiosity: In HTTPS Everywhere, the functionality used to be call "Block all HTTP requests" but when that functionality was changed (back in 2016 [0]) to not block connections to non-HTTPS hidden services, it was renamed to "Block all unencrypted requests".

I just checked, and indeed Tor Browser 11.5 does not block non-HTTPS connections to hidden services, even when in "HTTPS-Only" mode. Thankfully.

[0]: https://github.com/EFForg/https-everywhere/pull/4370

HTTPS Everywhere is discontinued by its creator and will be removed completely next year, because every major browser includes the functionality already anyways.

HTTPS Everywhere Chrome Web Store Github

[1] https://github.com/EFForg/https-everywhere/tree/master/src/chrome/content/rules

You should ask those writers or see if you find anything useful at their github page here

It's a ruleset for the HTTP Everywhere browser extension.

Maybe try upstream at https://github.com/EFForg/https-everywhere

You need an access token from ipinfo to access their API. Go to ipinfo.io and sign up for an account. After signing up, you'll get an access token. Keep it handy as we'll need it in the next step.

stories: - name: get-ip-info steps: - name: get-ip url: https://api.ipify.org/?format=json http_method: GET - name: get-location url: https://ipinfo.io/${{steps.get-ip.response.body.ip}}/geo http_method: GET expectations: - field: Body operation: Contains value: "Australia" schedule: initial_delay: 10 interval: 60 alerts: - url: https://my.site/notify

3- IPinfo

Mullvad VPN location set to Frankfurt germany

Using the us east test server:

Proxy Score: 10/100 - Very likely not a Proxy

VPN Score: 0/55 - Very likely not a VPN

Using german test server:

Proxy Score: 10/100 - Very likely not a Proxy

VPN Score: 30/55 - Very likely a VPN

The thing that changed between both tests was the flow latencies vs ping latencies check. Clicking on more info it said: "flow variance too large in relation to avg flow: 0.6937484181219945"

I guess it works kinda, but not very consistent.

But e.g. https://ipinfo.io/ reveals immediately that this IP is a VPN IP address.

If it's a work computer it may be connecting to it's own VPN automatically. If you go to a site like https://ipinfo.io/ do you recognize the external IP address, region, and org?

Then just check IP of the server when ping is high for you, put IP in https://ipinfo.io/, and block range for all other servers in same datacenter.

3. Check the IP address information by ipinfo.io, and confirm the IP location information is right with okeyproxy's we pasted into ProxyHelper.

IPinfo.io | Various Roles | Remote (Anywhere) | Fulltime / Contract | https://ipinfo.io

IPinfo is a leading provider of IP address data. Our API handles almost 100 billion requests a month, and we also license our data for use in many products and services you might have used. We started as a side project back in 2013, offering a free geolocation API, and we've since bootstrapped ourselves to a profitable business with a global team of over 20, and grown our data offerings to include geolocation, IP to company, carrier detection, and VPN detection. Our customers include T-Mobile, Nike, DataDog, DemandBase, Clearbit and many more.

We're looking for exceptional and ambitious people to join our team. The main role we're hiring for currently is a Product Manager - ideally with SaaS/DaaS experience, and a technical understanding of our products / services. Apply here: https://ipinfo.bamboohr.com/careers/45?source=aWQ9Mjg%3D

We're always on the look out to strong software or data engineers with an internet measuremenet / analysis background to join our team too. Any questions about the roles or IPinfo feel free to reach out to me directly at [email protected]

2023-11-07T10:10:50+01:00 ERROR [ip getter] Get "https://ipinfo.io/": dial tcp: lookup ipinfo.io on 1.1.1.1:53: write udp 172.18.0.22:41311->1.1.1.1:53: write: operation not permitted - retrying in 5s