Shakedown Social

0 posts0 participants0 posts today

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 noreferrer" target="_blank">#zerotrust</a> <a href="https://infosec.exchange/tags/geoblocking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#geoblocking</a> <a href="https://infosec.exchange/tags/apt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#apt</a> <a href="https://infosec.exchange/tags/scriptkiddie" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#scriptkiddie</a> <a href="https://infosec.exchange/tags/networksecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#networksecurity</a> <a href="https://infosec.exchange/tags/cloudflare" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cloudflare</a>

Veza85UE<a href="https://ec.social-network.europa.eu/@EUCommission" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@EUCommission</a> My proposal for unlocking the potential of one particular 🇪🇺 creative industry (one we invented in Europe) is to smack Ruben Östlund and all politicians he's lobbied for <a href="https://eupolicy.social/tags/geoblocking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#geoblocking</a> over the head with the Consolidated version of The Treaty on the Functioning of the European Union open at Article 101 until they stop blocking Europeans from learning about each other and entertaining each other with 🇪🇺 popculture. <a href="https://eupolicy.social/@Veza85UE/111574381900505708" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://eupolicy.social/@Veza85UE/111574381900505708</a><a href="https://eupolicy.social/tags/cinema" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cinema</a> <a href="https://eupolicy.social/tags/eurocultura" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#eurocultura</a> <a href="https://eupolicy.social/tags/MyOwnPersonalJihad" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MyOwnPersonalJihad</a>

Kevin Karhan :verified:<a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@landley</a> <a href="https://mstdn.social/@jschauma" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jschauma</a> <a href="https://infosec.exchange/@ryanc" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ryanc</a> <a href="https://infosec.exchange/@0xabad1dea" class="u-url mention" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">#IP</a> (which is a <a href="https://infosec.space/tags/privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#privacy</a> nightmare at best that "<a href="https://infosec.space/tags/PrivacyExtensions" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#DECnet</a> approach and use the <a href="https://infosec.space/tags/EUI48" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EUI48</a> / <a href="https://infosec.space/tags/MAC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MAC</a>-Address (or <a href="https://infosec.space/tags/EUI64" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#vendors</a> and not <a href="https://infosec.space/tags/ISPs" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#ICCID</a> dictates <a href="https://infosec.space/tags/GSM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GSM</a> / <a href="https://infosec.space/tags/4G" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#4G</a> / <a href="https://infosec.space/tags/5G" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#5G</a> access and not the <a href="https://infosec.space/tags/IMEI" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#128bit</a> address space was inspired by <a href="https://infosec.space/tags/ZFS" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#IPv6</a> because not only do I only have <a href="https://infosec.space/tags/IPv4only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv4only</a> <a href="https://infosec.space/tags/Internet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Internet</a> but my <a href="https://infosec.space/tags/ISP" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">#HurricaneElectric</a> / <a href="https://infosec.space/tags/HEnet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HEnet</a>'s <a href="https://infosec.space/tags/Tunnelbroker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tunnelbroker</a> fail face first due to <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Geoblocking</a> and the fact that <a href="https://infosec.space/tags/ASNs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ASNs</a> get geolocated, not their <a href="https://infosec.space/tags/PoPs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PoPs</a>... </li></ul>If I was <a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@BNetzA</a> I would've mandated <a href="https://infosec.space/tags/DualStack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DualStack</a> and banned <a href="https://infosec.space/tags/CGNAT" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#RFC1918</a> address spaces) as well as <a href="https://infosec.space/tags/DualStackLite" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DualStackLite</a>!

Kevin Karhan :verified:<a href="https://mastodon.social/@shoppingtonz" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@shoppingtonz</a> <a href="https://mas.to/@alternativeto" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@alternativeto</a> <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@torproject</a> also every <a href="https://infosec.space/tags/Tunneling" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tunneling</a> - regardless if <a href="https://infosec.space/tags/SSH" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSH</a> or <a href="https://infosec.space/tags/VPN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VPN</a> or whatever - will inevitably introduce <a href="https://infosec.space/tags/latency" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#ISP</a> with horrible <a href="https://infosec.space/tags/peering" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#Geoblocking</a> and bypassing <a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IP</a>-based <a href="https://infosec.space/tags/Banning" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Banning</a> (i.e. for <a href="https://infosec.space/tags/Cheating" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#HEnet</a> <a href="https://infosec.space/tags/Tunnelbroker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tunnelbroker</a> and <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a>-<a href="https://infosec.space/tags/GIF" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#IPv4only</a> <a href="https://infosec.space/tags/Internet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Internet</a> connection…

Kevin Karhan :verified:<a href="https://infosec.space/@fennix" class="u-url mention" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#geoblocking</a> and potentially <a href="https://infosec.space/tags/InternetCensorship" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#InternetCensorship</a> as well as <a href="https://infosec.space/tags/TrafficDiscrimination" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TrafficDiscrimination</a> due to lack of <a href="https://infosec.space/tags/NetNeutrality" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#loglessVPN</a>|s" and no <a href="https://infosec.space/tags/VPN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VPN</a> provider will <a href="https://web.archive.org/web/20210606070919/twitter.com/thegrugq/status/1085614812581715968" rel="nofollow noopener noreferrer" target="_blank">risk jailtime for any.client</a>…

Spruwel<a href="https://infosec.exchange/@0xabad1dea" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@0xabad1dea</a> I'm pretty sure there weren't <a href="https://chaos.social/tags/geoblocking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#geoblocking</a> in 1985.

Kevin Karhan :verified:<a href="https://chaos.social/@kubikpixel" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@kubikpixel</a> <a href="https://infosec.exchange/@malwaretech" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@malwaretech</a> <a href="https://mastodon.social/@tomscott" class="u-url mention" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#VPN</a> has similar utilization as a <a href="https://infosec.space/tags/CGNAT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CGNAT</a>, so easily they'll have <a href="https://infosec.space/tags/LawfulInterception" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">logless VPNs are a lie</a> and besides circumventing <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">@torproject</a> <a href="https://venera.social/profile/tails_live" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@tails_live</a> <a href="https://fosstodon.org/@tails" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@tails</a> / <a href="https://infosec.space/tags/Tails" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tails</a> and good.

Kevin Karhan :verified:<a href="https://chaos.social/@wmd" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@wmd</a> <a href="https://denden.world/@miqokin" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@miqokin</a> <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@torproject</a> there is a shitton of information.<ul><li>Check out the <a href="https://infosec.space/tags/documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#documentation</a> by <a href="https://social.librem.one/@guardianproject" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@guardianproject</a> (and yes you can simply choose on a per-connection basis to use <a href="https://infosec.space/tags/Tor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tor</a> or not woth <a href="https://infosec.space/tags/Orbot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Orbot</a>).</li></ul><a href="https://infosec.space/tags/VPN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VPN</a>|s only work great to circumvent <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Geoblocking</a> and they won't protect users against prosecution and surveillance!<ul><li>You'd know that if you read <a href="https://infosec.exchange/@thegrugq" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@thegrugq@infosec.exchange</a> / <a href="https://social.librem.one/@thegrugq" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@thegrugq@librem.one</a> 's original post and the linked <a href="https://infosec.space/tags/case" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#case</a> against someone abusing a VPN.</li></ul>Whereas with Tor that doesn't work that well...<ul><li>And people who have the time, money and means to get a custom <a href="https://infosec.space/tags/SSH" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSH</a> tunnel to some <a href="https://infosec.space/tags/VPS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VPS</a> setup are not the average users...</li></ul>Whereas I can get someone started on <a href="https://infosec.space/tags/Orbot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Orbot</a> + <a href="https://monocles.social/@monocles" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@monocles</a> / <a href="https://infosec.space/tags/monoclesChat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#monoclesChat</a> within minutes.

Maximilian HenningThe European Court of Auditors published an interesting report on <a href="https://darmstadt.social/tags/geoblocking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#geoblocking</a> in the <a href="https://darmstadt.social/tags/EU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EU</a> yesterday. The EU is supposed to have a common market, where goods, services and money flow freely – but this report shows that in the digital world, that often isn’t the case.<a href="https://www.eca.europa.eu/en/publications/SR-2025-03" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.eca.europa.eu/en/publications/SR-2025-03</a>

Kevin Karhan :verified:<a href="https://hachyderm.io/@jetsoft" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jetsoft</a> <a href="https://mastodon.social/@hanse_mina" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@hanse_mina</a> <a href="https://infosec.space/tags/Funfact" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Funfact</a>, i worked at several firms where <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Geoblocking</a> <a href="https://infosec.space/tags/Russia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Russia</a> alongside "P.R." <a href="https://infosec.space/tags/China" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#China</a> and <a href="https://infosec.space/tags/NorthKorea" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NorthKorea</a> was part of their <a href="https://infosec.space/tags/ITsec" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#DDoS</a>'d or face hacking attempts.<ul><li><a href="https://infosec.space/tags/BGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BGP</a>-<a href="https://infosec.space/tags/Blackholing" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">@jana</a> what if my <a href="https://infosec.space/tags/ISP" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#Geoblocking</a> makes using <a href="https://infosec.space/tags/HurricaneElectric" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HurricaneElectric</a>'s <a href="https://tunnelbroker.net" rel="nofollow noopener noreferrer" target="_blank">Tunnelbroker</a> useless cuz some idiots decided to <a href="https://infosec.space/tags/Geolocate" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Geolocate</a> based off <a href="https://infosec.space/tags/ASN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ASN</a> not location...

Kevin Karhan :verified:<a href="https://techhub.social/@leeloo" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@leeloo</a> Until regulators like <a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#IPv6</a> to be supplied to every <a href="https://infosec.space/tags/internet" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#IPv4</a>.<ul><li>Worse is only <a href="https://infosec.space/tags/DualStackLite" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DualStackLite</a> and having to do unreliable (due to <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Geoblocking</a>) hacks like <a href="https://infosec.space/tags/6in4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#6in4</a> / <a href="https://infosec.space/tags/6over4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#6over4</a> with <a href="https://tunnelbroker.net" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">#Geoblocking</a> <a href="https://ec.europa.eu/commission/presscorner/detail/en/ip_24_5727" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">@kline</a> sadly no, as my <a href="https://infosec.space/tags/ISP" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#IPv6</a>, but happily gives me a /28 of <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">@ripencc</a> can calm down.</li><li>No, <a href="https://infosec.space/tags/HurricaneElectric" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HurricaneElectric</a>'s <a href="https://infosec.space/tags/Tunnelbroker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tunnelbroker</a> at <a href="https://tunnelbroker.net" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#USA</a> by virtue of it's <a href="https://infosec.space/tags/ASN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ASN</a> despite choosing <a href="https://infosec.space/tags/FFM" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#GIF</a>-tunnel thanks to <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Geoblocking</a>!</li></ul>

Kevin Karhan :verified:<a href="https://freeradical.zone/@steevmi1" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@steevmi1</a> <a href="https://hackers.town/@thegibson" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@thegibson</a> <a href="https://infosec.exchange/@hrbrmstr" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@hrbrmstr</a> personally, I consider all <a href="https://infosec.space/tags/VPN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VPN</a> that isn't a connection to your own business/home network to a <a href="https://infosec.space/tags/Snakeoil" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Snakeoil</a> except when it comes to circumventing <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Geoblocking</a> and/or <a href="https://infosec.space/tags/InternetCensorship" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#InternetCensorship</a> and accessing sites & content!That's why <a href="https://monocles.social/@monocles" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@monocles</a> don't offer a <a href="https://infosec.space/tags/VPN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VPN</a> (They could easily buy that as a white-label/ "Managed Service for Reselling" or shove some stuff in a datacenter and callit a day.<ul><li>for <a href="https://infosec.space/tags/Privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Privacy</a> you're way better off using <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@torproject</a> / <a href="https://infosec.space/tags/Tor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tor</a>, espechally since <a href="https://web.archive.org/web/20220112020000/https://twitter.com/thegrugq/status/1085614812581715968" rel="nofollow noopener noreferrer" target="_blank">they can't rat you out like any telco (incl. VPNs) MUST BE ABLE TO DO</a>…</li></ul>

Kevin Karhan :verified:<a href="https://mastodon.social/@shaknais" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@shaknais</a> I tried GIF-Tunneling with <a href="https://infosec.space/tags/HurricaneElectric" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HurricaneElectric</a> and while they offer static subnets (I got a /48 & /64) this isn't workibg reliably and causes issues due to <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Geoblocking</a> despite choosibg their PoP in Frankfurt am Main.

Kevin Karhan :verified:<a href="https://infosec.exchange/@0xabad1dea" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@0xabad1dea</a> I don't think the security argument is the point, cuz most sites that do <a href="https://infosec.space/tags/geoblocking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#geoblocking</a> select only few nations they can clearly say they don't want clients from (i.e. PRC & Russia to avoid carding, North Korea.due to nalware)...<ul><li>In fact, most sites I've seen from the <a href="https://infosec.space/tags/USA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#USA</a> that do <a href="https://infosec.space/tags/geoblock" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#geoblock</a> me from <a href="https://infosec.space/tags/Germany" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Germany</a> do so because they don:t wajt to comply with <a href="https://infosec.space/tags/GDPR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GDPR</a> and instead vomit thousands (!!!) of <a href="https://infosec.space/tags/tracking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tracking</a> <a href="https://infosec.space/tags/cookies" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cookies</a> on me at every visit.</li></ul>I mean it's not as if any gun dealer from Germany would be able to sent a costly C&D to SilencerCo for not disclosing the need for a purchase permit in Germany (like with all guns and -parts regulated) when they don't even accept overseas customer at all to buy directly from them...

Kevin Karhan :verified:<a href="https://sfba.social/@mvilain" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mvilain</a> <a href="https://mastodon.online/@standev" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@standev</a> <a href="https://infosec.exchange/@jerry" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jerry</a> well, <a href="https://monocles.social/@monocles" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@monocles</a> doesn't offer a <a href="https://infosec.space/tags/VPN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VPN</a> cuz setting up such a service comes with a shitload of issues and besides circumventing <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Geoblocking</a> there isn't any reason to use <a href="https://infosec.space/tags/VPNs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VPNs</a> over <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@torproject</a> / <a href="https://infosec.space/tags/Tor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tor</a>...

Kevin Karhan :verified:<a href="https://mastodon.online/@standev" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@standev</a> <a href="https://sfba.social/@mvilain" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mvilain</a> <a href="https://infosec.exchange/@jerry" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jerry</a> That's propably because of that.<ul><li>I know companies that'll instantly block any domain registered or adminitrated or linked to <a href="https://infosec.space/tags/GoDaddy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GoDaddy</a>, <a href="https://infosec.space/tags/NameCheap" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NameCheap</a>, <a href="https://infosec.space/tags/NiceNIc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NiceNIc</a>, <a href="https://infosec.space/tags/CloudFlare" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CloudFlare</a> or <a href="https://infosec.space/tags/ProtonMail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ProtonMail</a> due to rampant <a href="https://infosec.space/tags/spam" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#spam</a>, <a href="https://infosec.space/tags/scams" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#scams</a> and abuse by <a href="https://infosec.space/tags/CyberCrime" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CyberCrime</a> groups. </li></ul>In fact I did that - alongside <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Geoblocking</a> - to prevent and deter <a href="https://infosec.space/tags/carding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#carding</a> attempts at a fmr. employer.<ul><li>And like many modern sites, attempts of registering an account would just get <a href="https://infosec.space/tags/blackholed" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#blackholed</a> without any notification and said IPs [the entire block allocation as per WHOIS!] temporarily blocklisted for 24 hours.</li></ul>Granted this wasn't my decision but basically what the CLO & CFO saw fit as "cybersecurity and risk avoidance strategy" towards regulatory pressure by <a href="https://social.bund.de/@bsi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@bsi</a> & <a href="https://social.bund.de/@BaFin" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@BaFin</a> ...

Recent searches

Search options

Administered by:

Server stats:

#geoblocking