++prettysocks
This commit is contained in:
parent
25288414db
commit
6fccb819f6
1 changed files with 19 additions and 0 deletions
|
@ -203,6 +203,25 @@ to fe80::1"
|
||||||
|
|
||||||
Thanks again for the pointer!
|
Thanks again for the pointer!
|
||||||
|
|
||||||
|
### The prettysocks SOCKS5 proxy (update 2021-11-24)
|
||||||
|
|
||||||
|
On 2021-11-23 we have been notified that there is a new workaround
|
||||||
|
available:
|
||||||
|
[prettysock](https://github.com/twisteroidambassador/prettysocks/tree/ipv6-literal)
|
||||||
|
is a Socks5 proxy written in python that allows the use of Microsoft's
|
||||||
|
**ipv6-literal.net** domain, but from any OS or browser, which is
|
||||||
|
pointed to the proxy. So to access **fe80::1ff:fe23:4567:890a%3**,
|
||||||
|
configure your browser to use the local prettysocks Socks5 proxy,
|
||||||
|
replace the link local address with
|
||||||
|
**fe80--1ff-fe23-4567-890as3.ipv6-literal.net** and there you go.
|
||||||
|
|
||||||
|
There are two interesting things to say about this solution:
|
||||||
|
|
||||||
|
* It is a very simple solution
|
||||||
|
* It is surprising that browser vendors haven't implement such a
|
||||||
|
simple solution themselves so far - does it need an RFC that defines
|
||||||
|
the domain to be used?
|
||||||
|
|
||||||
## Other resources
|
## Other resources
|
||||||
|
|
||||||
If you are aware of other resources regarding IPv6 link local support
|
If you are aware of other resources regarding IPv6 link local support
|
||||||
|
|
Loading…
Reference in a new issue