Shakedown Social

Kevin Karhan :verified:<a href="https://tweesecake.social/@adisonverlice" class="u-url mention" rel="nofollow noopener" target="_blank">@adisonverlice</a> <a href="https://mastodon.online/@mullvadnet" class="u-url mention" rel="nofollow noopener" target="_blank">@mullvadnet</a> <a href="https://social.freifunk.net/@freifunk" class="u-url mention" rel="nofollow noopener" target="_blank">@freifunk</a> <a href="https://monocles.social/@monocles" class="u-url mention" rel="nofollow noopener" target="_blank">@monocles</a> +9001%I think the same, and a <a href="https://infosec.space/tags/VPN" class="mention hashtag" rel="nofollow noopener" target="_blank">#VPN</a> has it's merits espechally when it comes to <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener" target="_blank">#Geoblocking</a> and high-bandwith applications.<ul><li>In fact <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener" target="_blank">@torproject</a> warns against <a href="https://infosec.space/tags/Torrenting" class="mention hashtag" rel="nofollow noopener" target="_blank">#Torrenting</a> over <a href="https://infosec.space/tags/Tor" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tor</a> <a href="https://infosec.space/tags/BitTorrent" class="mention hashtag" rel="nofollow noopener" target="_blank">#BitTorrent</a> clients routinely fuck up and deanonymize users.</li></ul>(And that's not even accounting for the intensity of traffic that it burdens the Network with!)

Kevin Karhan :verified:<a href="https://tiggi.es/@thygrrr" class="u-url mention" rel="nofollow noopener" target="_blank">@thygrrr</a> <a href="https://social.treehouse.systems/@PallasRiot" class="u-url mention" rel="nofollow noopener" target="_blank">@PallasRiot</a> I mean if you just want to circumvent <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener" target="_blank">#Geoblocking</a> then yeah...<ul><li>Tho not shure if one can VPN to them via <a href="https://infosec.space/tags/Tor" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tor</a>... </li></ul><a href="https://infosec.space/@kkarhan/114953865903981711" translate="no" rel="nofollow noopener" target="_blank">https://infosec.space/@kkarhan/114953865903981711</a>

Kevin Karhan :verified:<a href="https://kolektiva.social/@hakan_geijer" class="u-url mention" rel="nofollow noopener" target="_blank">@hakan_geijer</a> <a href="https://social.treehouse.systems/@PallasRiot" class="u-url mention" rel="nofollow noopener" target="_blank">@PallasRiot</a> The only "legitimate use case" for a commercial <a href="https://infosec.space/tags/VPN" class="mention hashtag" rel="nofollow noopener" target="_blank">#VPN</a> I know of is circumventing <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener" target="_blank">#Geoblocking</a>... <ul><li>Neither will a VPN prevent leakage of data!</li></ul>That's why I explicitly recommended using <a href="https://infosec.space/tags/Tails" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tails</a>, because that does have mitigations in place against that and <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener" target="_blank">@torproject</a> / <a href="https://infosec.space/tags/TorBrowser" class="mention hashtag" rel="nofollow noopener" target="_blank">#TorBrowser</a> does so too...<ul><li>Again: Your mileage may vary and depend on the individual threat assessment on a case-by-case basis.</li></ul>

Lazarou Monkey Terror 🚀💙🌈It's not only Gilead cutting back on Soft Power and pulling back on putting ourselves out into the world...<a href="https://www.bbc.com/news/articles/c5yg065058no" rel="nofollow noopener" translate="no" target="_blank">https://www.bbc.com/news/articles/c5yg065058no</a><a href="https://mastodon.social/tags/BBC" class="mention hashtag" rel="nofollow noopener" target="_blank">#BBC</a> <a href="https://mastodon.social/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener" target="_blank">#Geoblocking</a> <a href="https://mastodon.social/tags/BBCSounds" class="mention hashtag" rel="nofollow noopener" target="_blank">#BBCSounds</a>

feinstrukturQuestion for the technical more affine! Is there a safe and easy way around geoblocking on Youtube?<a href="https://mastodon.social/tags/TechnicalSupport" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechnicalSupport</a> <a href="https://mastodon.social/tags/Help" class="mention hashtag" rel="nofollow noopener" target="_blank">#Help</a> <a href="https://mastodon.social/tags/Question" class="mention hashtag" rel="nofollow noopener" target="_blank">#Question</a> <a href="https://mastodon.social/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener" target="_blank">#Geoblocking</a> <a href="https://mastodon.social/tags/YouTube" class="mention hashtag" rel="nofollow noopener" target="_blank">#YouTube</a>

Kevin Karhan :verified:<a href="https://netzkms.de/@neu3no" class="u-url mention" rel="nofollow noopener" target="_blank">@neu3no</a> <a href="https://labyrinth.zone/users/halva" class="u-url mention" rel="nofollow noopener" target="_blank">@halva</a> yes and no.<ul><li>I can see the benefit of a miniaturized retro gaming system (I think legacy systems need to be served with properly maintained software & hardware).</li></ul><a href="https://www.youtube.com/watch?v=2P1E2vjpcRo" rel="nofollow noopener" translate="no" target="_blank">https://www.youtube.com/watch?v=2P1E2vjpcRo</a> <a href="https://www.youtube.com/watch?v=B8WfiRRvQXo" rel="nofollow noopener" translate="no" target="_blank">https://www.youtube.com/watch?v=B8WfiRRvQXo</a>As with <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv4</a> the problem is that there is no mandate to provide users with static prefixes and I'm stuck on a /28 of IPv4's and can't even get a singoe /64.<ul><li>And before you ask: No, <a href="https://infosec.space/tags/Tunnelbroker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tunnelbroker</a> is not a valid solution as HE.net's tunnel will get <a href="https://infosec.space/tags/USA" class="mention hashtag" rel="nofollow noopener" target="_blank">#USA</a> <a href="https://infosec.space/tags/GeoIP" class="mention hashtag" rel="nofollow noopener" target="_blank">#GeoIP</a>'d even eith the PoP in FRA so it bricks a shitload of things due to <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener" target="_blank">#Geoblocking</a> and bad <a href="https://infosec.space/tags/peering" class="mention hashtag" rel="nofollow noopener" target="_blank">#peering</a>. Believe me, I tried that already!</li></ul>

Piiieps & Brummm<a href="https://social.wildeboer.net/@jwildeboer" class="u-url mention" rel="nofollow noopener" target="_blank">@jwildeboer</a> I do <a href="https://chaos.social/tags/GeoBlocking" class="mention hashtag" rel="nofollow noopener" target="_blank">#GeoBlocking</a> on the login side of my server (submission, imap). Only login from an European country is allowed. This is possible, because I usually know the whereabouts of my users. If we travel outside Europe, I can temporarily allow that counrty. :-)Do you do anything of that kind?

WalkerWhen can we declare IP Geo location / country code blocking practically dead as a mitigation strategy?Sure it is still useful blocking script kiddies from Iran and other low hanging fruit, but do any serious APT crews actually launch attacks from their home country anymore? With the use of zero trust, distributed attack and delivery networks (looking at you Cloudflare), and VPN usage country blocking feels less useful than in the past. <a href="https://infosec.exchange/tags/zerotrust" class="mention hashtag" rel="nofollow noopener" target="_blank">#zerotrust</a> <a href="https://infosec.exchange/tags/geoblocking" class="mention hashtag" rel="nofollow noopener" target="_blank">#geoblocking</a> <a href="https://infosec.exchange/tags/apt" class="mention hashtag" rel="nofollow noopener" target="_blank">#apt</a> <a href="https://infosec.exchange/tags/scriptkiddie" class="mention hashtag" rel="nofollow noopener" target="_blank">#scriptkiddie</a> <a href="https://infosec.exchange/tags/networksecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#networksecurity</a> <a href="https://infosec.exchange/tags/cloudflare" class="mention hashtag" rel="nofollow noopener" target="_blank">#cloudflare</a>

Kevin Karhan :verified:<a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@landley</a> <a href="https://mstdn.social/@jschauma" class="u-url mention" rel="nofollow noopener" target="_blank">@jschauma</a> <a href="https://infosec.exchange/@ryanc" class="u-url mention" rel="nofollow noopener" target="_blank">@ryanc</a> <a href="https://infosec.exchange/@0xabad1dea" class="u-url mention" rel="nofollow noopener" target="_blank">@0xabad1dea</a> yeah, the exhaustion problem would've been shoved back with a <a href="https://infosec.space/tags/64bit" class="mention hashtag" rel="nofollow noopener" target="_blank">#64bit</a> or sufficiently delayed by a 40bit number.Unless we also hate <a href="https://infosec.space/tags/NAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#NAT</a> and expect every device to have a unique static <a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener" target="_blank">#IP</a> (which is a <a href="https://infosec.space/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#privacy</a> nightmare at best that "<a href="https://infosec.space/tags/PrivacyExtensions" class="mention hashtag" rel="nofollow noopener" target="_blank">#PrivacyExtensions</a>" barely fixed.) <ul><li>I mean they could've also gone the <a href="https://infosec.space/tags/DECnet" class="mention hashtag" rel="nofollow noopener" target="_blank">#DECnet</a> approach and use the <a href="https://infosec.space/tags/EUI48" class="mention hashtag" rel="nofollow noopener" target="_blank">#EUI48</a> / <a href="https://infosec.space/tags/MAC" class="mention hashtag" rel="nofollow noopener" target="_blank">#MAC</a>-Address (or <a href="https://infosec.space/tags/EUI64" class="mention hashtag" rel="nofollow noopener" target="_blank">#EUI64</a>) as static addressing system, but that would've made <a href="https://infosec.space/tags/vendors" class="mention hashtag" rel="nofollow noopener" target="_blank">#vendors</a> and not <a href="https://infosec.space/tags/ISPs" class="mention hashtag" rel="nofollow noopener" target="_blank">#ISPs</a> the powerful forces of allocation. (Similar to how technically the <a href="https://infosec.space/tags/ICCID" class="mention hashtag" rel="nofollow noopener" target="_blank">#ICCID</a> dictates <a href="https://infosec.space/tags/GSM" class="mention hashtag" rel="nofollow noopener" target="_blank">#GSM</a> / <a href="https://infosec.space/tags/4G" class="mention hashtag" rel="nofollow noopener" target="_blank">#4G</a> / <a href="https://infosec.space/tags/5G" class="mention hashtag" rel="nofollow noopener" target="_blank">#5G</a> access and not the <a href="https://infosec.space/tags/IMEI" class="mention hashtag" rel="nofollow noopener" target="_blank">#IMEI</a> unless places like Australia ban imported devices.</li></ul> I guess using a <a href="https://infosec.space/tags/128bit" class="mention hashtag" rel="nofollow noopener" target="_blank">#128bit</a> address space was inspired by <a href="https://infosec.space/tags/ZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#ZFS</a> doing the same before, as the folks who designed both wanted to design a solution that clearly will outlive them (way harder than COBOL has outlived Grace Hopper)...<ul><li>Personally I've only had headaches with <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv6</a> because not only do I only have <a href="https://infosec.space/tags/IPv4only" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv4only</a> <a href="https://infosec.space/tags/Internet" class="mention hashtag" rel="nofollow noopener" target="_blank">#Internet</a> but my <a href="https://infosec.space/tags/ISP" class="mention hashtag" rel="nofollow noopener" target="_blank">#ISP</a> refuses to allocate even a singe /64 to me (but has no problem throwing in a free /29 of <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv4</a>'s in with my contract!)and stuff like <a href="https://infosec.space/tags/HurricaneElectric" class="mention hashtag" rel="nofollow noopener" target="_blank">#HurricaneElectric</a> / <a href="https://infosec.space/tags/HEnet" class="mention hashtag" rel="nofollow noopener" target="_blank">#HEnet</a>'s <a href="https://infosec.space/tags/Tunnelbroker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tunnelbroker</a> fail face first due to <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener" target="_blank">#Geoblocking</a> and the fact that <a href="https://infosec.space/tags/ASNs" class="mention hashtag" rel="nofollow noopener" target="_blank">#ASNs</a> get geolocated, not their <a href="https://infosec.space/tags/PoPs" class="mention hashtag" rel="nofollow noopener" target="_blank">#PoPs</a>... </li></ul>If I was <a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener" target="_blank">@BNetzA</a> I would've mandated <a href="https://infosec.space/tags/DualStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#DualStack</a> and banned <a href="https://infosec.space/tags/CGNAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#CGNAT</a> (or at least the use of CGNAT in <a href="https://infosec.space/tags/RFC1918" class="mention hashtag" rel="nofollow noopener" target="_blank">#RFC1918</a> address spaces) as well as <a href="https://infosec.space/tags/DualStackLite" class="mention hashtag" rel="nofollow noopener" target="_blank">#DualStackLite</a>!

Kevin Karhan :verified:<a href="https://mastodon.social/@shoppingtonz" class="u-url mention" rel="nofollow noopener" target="_blank">@shoppingtonz</a> <a href="https://mas.to/@alternativeto" class="u-url mention" rel="nofollow noopener" target="_blank">@alternativeto</a> <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener" target="_blank">@torproject</a> also every <a href="https://infosec.space/tags/Tunneling" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tunneling</a> - regardless if <a href="https://infosec.space/tags/SSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSH</a> or <a href="https://infosec.space/tags/VPN" class="mention hashtag" rel="nofollow noopener" target="_blank">#VPN</a> or whatever - will inevitably introduce <a href="https://infosec.space/tags/latency" class="mention hashtag" rel="nofollow noopener" target="_blank">#latency</a> (unless you happen to be customer of a shitty <a href="https://infosec.space/tags/ISP" class="mention hashtag" rel="nofollow noopener" target="_blank">#ISP</a> with horrible <a href="https://infosec.space/tags/peering" class="mention hashtag" rel="nofollow noopener" target="_blank">#peering</a> and thus can cut down on hops needed, which is AFAIK only a theoretical scenario)...<ul><li>Outside of circumventing <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener" target="_blank">#Geoblocking</a> and bypassing <a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener" target="_blank">#IP</a>-based <a href="https://infosec.space/tags/Banning" class="mention hashtag" rel="nofollow noopener" target="_blank">#Banning</a> (i.e. for <a href="https://infosec.space/tags/Cheating" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cheating</a>) I've not seen any use-cases.</li></ul>In fact I stopped using <a href="https://infosec.space/tags/HEnet" class="mention hashtag" rel="nofollow noopener" target="_blank">#HEnet</a> <a href="https://infosec.space/tags/Tunnelbroker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tunnelbroker</a> and <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv6</a>-<a href="https://infosec.space/tags/GIF" class="mention hashtag" rel="nofollow noopener" target="_blank">#GIF</a>-Tunneling because it created more issued than it solved on my <a href="https://infosec.space/tags/IPv4only" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv4only</a> <a href="https://infosec.space/tags/Internet" class="mention hashtag" rel="nofollow noopener" target="_blank">#Internet</a> connection…

Kevin Karhan :verified:<a href="https://infosec.space/@fennix" class="u-url mention" rel="nofollow noopener" target="_blank">@fennix</a> TBH, I think those bs claims should be illegal.The only valid claims I've seen is that it enables people to circumvent <a href="https://infosec.space/tags/geoblocking" class="mention hashtag" rel="nofollow noopener" target="_blank">#geoblocking</a> and potentially <a href="https://infosec.space/tags/InternetCensorship" class="mention hashtag" rel="nofollow noopener" target="_blank">#InternetCensorship</a> as well as <a href="https://infosec.space/tags/TrafficDiscrimination" class="mention hashtag" rel="nofollow noopener" target="_blank">#TrafficDiscrimination</a> due to lack of <a href="https://infosec.space/tags/NetNeutrality" class="mention hashtag" rel="nofollow noopener" target="_blank">#NetNeutrality</a>, but those are always to be taken with a truckload of salt!Most certsinly, there are no "<a href="https://infosec.space/tags/loglessVPN" class="mention hashtag" rel="nofollow noopener" target="_blank">#loglessVPN</a>|s" and no <a href="https://infosec.space/tags/VPN" class="mention hashtag" rel="nofollow noopener" target="_blank">#VPN</a> provider will <a href="https://web.archive.org/web/20210606070919/twitter.com/thegrugq/status/1085614812581715968" rel="nofollow noopener" target="_blank">risk jailtime for any.client</a>…

Kevin Karhan :verified:<a href="https://chaos.social/@kubikpixel" class="u-url mention" rel="nofollow noopener" target="_blank">@kubikpixel</a> <a href="https://infosec.exchange/@malwaretech" class="u-url mention" rel="nofollow noopener" target="_blank">@malwaretech</a> <a href="https://mastodon.social/@tomscott" class="u-url mention" rel="nofollow noopener" target="_blank">@tomscott</a> or to put it into perspective:I worked at a telco, and whilst clients were above-average in terns of bahaviour, one does get a high single digit or low double-digit amount of LEA requests per day per x million customers.Now imagine the average <a href="https://infosec.space/tags/VPN" class="mention hashtag" rel="nofollow noopener" target="_blank">#VPN</a> has similar utilization as a <a href="https://infosec.space/tags/CGNAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#CGNAT</a>, so easily they'll have <a href="https://infosec.space/tags/LawfulInterception" class="mention hashtag" rel="nofollow noopener" target="_blank">#LawfulInterception</a> going on 24/7 because <a href="https://web.archive.org/web/20220112020000/https://twitter.com/thegrugq/status/1085614812581715968" rel="nofollow noopener" target="_blank">logless VPNs are a lie</a> and besides circumventing <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener" target="_blank">#Geoblocking</a> they don't do anything else...<ul><li>In fact I'd argue it'll be more privacy friendly to self-host a VPN on-demand with flexible hoster or just having a fixed IP at home, simply because those usually have a higher bar for getting surveillance approved.</li></ul>TLDR: Just get <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener" target="_blank">@torproject</a> <a href="https://venera.social/profile/tails_live" class="u-url mention" rel="nofollow noopener" target="_blank">@tails_live</a> <a href="https://fosstodon.org/@tails" class="u-url mention" rel="nofollow noopener" target="_blank">@tails</a> / <a href="https://infosec.space/tags/Tails" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tails</a> and good.

Kevin Karhan :verified:vpn, tor, education.

Kevin Karhan :verified:<a href="https://chaos.social/@wmd" class="u-url mention" rel="nofollow noopener" target="_blank">@wmd</a> <a href="https://denden.world/@miqokin" class="u-url mention" rel="nofollow noopener" target="_blank">@miqokin</a> <a href="https://infosec.space/tags/VPN" class="mention hashtag" rel="nofollow noopener" target="_blank">#VPN</a>|s are - for the most part and with the exception of circumventing <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener" target="_blank">#Geoblocking</a> - a <a href="https://infosec.space/tags/Scam" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scam</a> catering towards <a href="https://infosec.space/tags/TechIlliterates" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechIlliterates</a>.<a href="https://web.archive.org/web/20220112020000/https://twitter.com/thegrugq/status/1085614812581715968" rel="nofollow noopener" translate="no" target="_blank">https://web.archive.org/web/20220112020000/https://twitter.com/thegrugq/status/1085614812581715968</a><a href="https://infosec.space/tags/TLDR" class="mention hashtag" rel="nofollow noopener" target="_blank">#TLDR</a>:<ul><li>Use <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener" target="_blank">@torproject</a> or GTFO!</li></ul>

Kevin Karhan :verified:<a href="https://hachyderm.io/@jetsoft" class="u-url mention" rel="nofollow noopener" target="_blank">@jetsoft</a> <a href="https://mastodon.social/@hanse_mina" class="u-url mention" rel="nofollow noopener" target="_blank">@hanse_mina</a> <a href="https://infosec.space/tags/Funfact" class="mention hashtag" rel="nofollow noopener" target="_blank">#Funfact</a>, i worked at several firms where <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener" target="_blank">#Geoblocking</a> <a href="https://infosec.space/tags/Russia" class="mention hashtag" rel="nofollow noopener" target="_blank">#Russia</a> alongside "P.R." <a href="https://infosec.space/tags/China" class="mention hashtag" rel="nofollow noopener" target="_blank">#China</a> and <a href="https://infosec.space/tags/NorthKorea" class="mention hashtag" rel="nofollow noopener" target="_blank">#NorthKorea</a> was part of their <a href="https://infosec.space/tags/ITsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#ITsec</a> protocol simply because otherwise they'd constantly get <a href="https://infosec.space/tags/DDoS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DDoS</a>'d or face hacking attempts.<ul><li><a href="https://infosec.space/tags/BGP" class="mention hashtag" rel="nofollow noopener" target="_blank">#BGP</a>-<a href="https://infosec.space/tags/Blackholing" class="mention hashtag" rel="nofollow noopener" target="_blank">#Blackholing</a> traffic from entire ASNs helped a lot!</li></ul>

Kevin Karhan :verified:<a href="https://social.jsteuernagel.de/@jana" class="u-url mention" rel="nofollow noopener" target="_blank">@jana</a> what if my <a href="https://infosec.space/tags/ISP" class="mention hashtag" rel="nofollow noopener" target="_blank">#ISP</a> refuses to allocate me even a /64 and <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener" target="_blank">#Geoblocking</a> makes using <a href="https://infosec.space/tags/HurricaneElectric" class="mention hashtag" rel="nofollow noopener" target="_blank">#HurricaneElectric</a>'s <a href="https://tunnelbroker.net" rel="nofollow noopener" target="_blank">Tunnelbroker</a> useless cuz some idiots decided to <a href="https://infosec.space/tags/Geolocate" class="mention hashtag" rel="nofollow noopener" target="_blank">#Geolocate</a> based off <a href="https://infosec.space/tags/ASN" class="mention hashtag" rel="nofollow noopener" target="_blank">#ASN</a> not location...

Kevin Karhan :verified:<a href="https://techhub.social/@leeloo" class="u-url mention" rel="nofollow noopener" target="_blank">@leeloo</a> Until regulators like <a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener" target="_blank">@BNetzA</a> get their shit together and mandate a /64 of <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv6</a> to be supplied to every <a href="https://infosec.space/tags/internet" class="mention hashtag" rel="nofollow noopener" target="_blank">#internet</a> connection with no exceptioms or charges and mandates services and devices to support it as well, we'll not he above to get rid of <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv4</a>.<ul><li>Worse is only <a href="https://infosec.space/tags/DualStackLite" class="mention hashtag" rel="nofollow noopener" target="_blank">#DualStackLite</a> and having to do unreliable (due to <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener" target="_blank">#Geoblocking</a>) hacks like <a href="https://infosec.space/tags/6in4" class="mention hashtag" rel="nofollow noopener" target="_blank">#6in4</a> / <a href="https://infosec.space/tags/6over4" class="mention hashtag" rel="nofollow noopener" target="_blank">#6over4</a> with <a href="https://tunnelbroker.net" rel="nofollow noopener" translate="no" target="_blank">https://tunnelbroker.net</a> ...</li></ul>Meanwhile it would be cheaper and easier for me to literally get my own private /24 of IPv4s than to convince my ISP to offer me even a single /48 of IPv6s...

Chuck DarwinEuropean Commission and national authorities call on <a href="https://c.im/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apple</a> to stop geo-blocking practices on Apple Media ServicesToday, following a coordinated investigation at European level, the Consumer Protection Cooperation (CPC) Network of national consumer authorities and the European Commission notified Apple of several potentially prohibited geo-blocking practices that the CPC Network has identified on certain Apple Media Services, namely App Store, Apple Arcade, Music, iTunes Store, Books and Podcasts. The network requested Apple to align their practices with the EU's anti-geo-blocking rules. <a href="https://c.im/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener" target="_blank">#Geoblocking</a> <a href="https://ec.europa.eu/commission/presscorner/detail/en/ip_24_5727" rel="nofollow noopener" translate="no" target="_blank">https://ec.europa.eu/commission/presscorner/detail/en/ip_24_5727</a>

Kevin Karhan :verified:<a href="https://mastodon.sdf.org/@kline" class="u-url mention" rel="nofollow noopener" target="_blank">@kline</a> sadly no, as my <a href="https://infosec.space/tags/ISP" class="mention hashtag" rel="nofollow noopener" target="_blank">#ISP</a> refuses to allocate me even a single /64 of <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv6</a>, but happily gives me a /28 of <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv4</a>|s at no extra charge.<ul><li>Yes, I do put that to good use, <a href="https://mastodon.social/@ripencc" class="u-url mention" rel="nofollow noopener" target="_blank">@ripencc</a> can calm down.</li><li>No, <a href="https://infosec.space/tags/HurricaneElectric" class="mention hashtag" rel="nofollow noopener" target="_blank">#HurricaneElectric</a>'s <a href="https://infosec.space/tags/Tunnelbroker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tunnelbroker</a> at <a href="https://tunnelbroker.net" rel="nofollow noopener" translate="no" target="_blank">https://tunnelbroker.net</a> doesn't help due to it being geolocated wrongly in the <a href="https://infosec.space/tags/USA" class="mention hashtag" rel="nofollow noopener" target="_blank">#USA</a> by virtue of it's <a href="https://infosec.space/tags/ASN" class="mention hashtag" rel="nofollow noopener" target="_blank">#ASN</a> despite choosing <a href="https://infosec.space/tags/FFM" class="mention hashtag" rel="nofollow noopener" target="_blank">#FFM</a> as exit, so most stuff just doesn't work through the <a href="https://infosec.space/tags/GIF" class="mention hashtag" rel="nofollow noopener" target="_blank">#GIF</a>-tunnel thanks to <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener" target="_blank">#Geoblocking</a>!</li></ul>

Recent searches

Search options

Administered by:

Server stats:

#geoblocking