Shakedown Social

Kevin Karhan :verified:<a href="https://mastodon.ie/@jherazob" class="u-url mention" rel="nofollow noopener" target="_blank">@jherazob</a> <a href="https://existiert.ch/@leberschnitzel" class="u-url mention" rel="nofollow noopener" target="_blank">@leberschnitzel</a> they <a href="https://infosec.space/@kkarhan/114437851069942896" rel="nofollow noopener" target="_blank">already exist</a>...<ul><li>Worst case fork <a href="https://infosec.space/tags/PoWshield" class="mention hashtag" rel="nofollow noopener" target="_blank">#PoWshield</a> as used by the fmr. admin of <a href="https://infosec.space/tags/IncognitoMarket" class="mention hashtag" rel="nofollow noopener" target="_blank">#IncognitoMarket</a> if you don't want to work with your hoster/upstream to block <a href="https://infosec.space/tags/DDoS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DDoS</a> attacks through <a href="https://infosec.space/tags/blackholing" class="mention hashtag" rel="nofollow noopener" target="_blank">#blackholing</a> and having a proper <a href="https://infosec.space/tags/Firewall" class="mention hashtag" rel="nofollow noopener" target="_blank">#Firewall</a> setup!</li></ul>I think it's bad <a href="https://infosec.space/tags/TechPopulism" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechPopulism</a> to think that <a href="https://infosec.space/tags/Anubis" class="mention hashtag" rel="nofollow noopener" target="_blank">#Anubis</a> will fix all the issues.<ul><li>It's like <a href="https://infosec.space/tags/KernelLevelAnticheat" class="mention hashtag" rel="nofollow noopener" target="_blank">#KernelLevelAnticheat</a>, <a href="https://infosec.space/tags/Antivirus" class="mention hashtag" rel="nofollow noopener" target="_blank">#Antivirus</a> and <a href="https://infosec.space/tags/DRM" class="mention hashtag" rel="nofollow noopener" target="_blank">#DRM</a>: A hamfisted approach that harms legitimate users more than the bad actors!</li></ul>Just block all the <a href="https://infosec.space/tags/GAFAMs" class="mention hashtag" rel="nofollow noopener" target="_blank">#GAFAMs</a> ASNs & <a href="https://infosec.space/tags/hosters" class="mention hashtag" rel="nofollow noopener" target="_blank">#hosters</a> that host <a href="https://infosec.space/tags/Scrapers" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scrapers</a> so the industry cracks down harder on them than on <a href="https://infosec.space/tags/IRC" class="mention hashtag" rel="nofollow noopener" target="_blank">#IRC</a>, <a href="https://infosec.space/tags/Tor" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tor</a> <a href="https://infosec.space/tags/ExitNodes" class="mention hashtag" rel="nofollow noopener" target="_blank">#ExitNodes</a>, <a href="https://infosec.space/tags/CSAM" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSAM</a> & <a href="https://infosec.space/tags/BitTorrent" class="mention hashtag" rel="nofollow noopener" target="_blank">#BitTorrent</a> combined!

Kevin Karhan :verified:<a href="https://toot.wales/@clubchonky" class="u-url mention" rel="nofollow noopener" target="_blank">@clubchonky</a> personally, I disagree to an extent.<a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener" target="_blank">@torproject</a> / <a href="https://infosec.space/tags/Tor" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tor</a> is well battle-tested and combat-hardened and using <a href="https://infosec.space/tags/OnionServices" class="mention hashtag" rel="nofollow noopener" target="_blank">#OnionServices</a> works just fine, as none of the traffic leaves through <a href="https://infosec.space/tags/ExitNodes" class="mention hashtag" rel="nofollow noopener" target="_blank">#ExitNodes</a>...

Kevin Karhan :verified:<a href="https://fearness.org/@gameplayer" class="u-url mention" rel="nofollow noopener" target="_blank">@gameplayer</a> <a href="https://atomicpoet.org/users/atomicpoet" class="u-url mention" rel="nofollow noopener" target="_blank">@atomicpoet</a> it's not that simple.<ul><li>Shure the average cybercriminal can use some hijacked routers and desktops as a proxy for their carding fraud but that doesn't scale with huge amounts of traffic and ISPs do combat proxy use by explicitly checking traffic for it and banning such setups as per ToS.</li></ul>In fact, many ISPs will forcibly disconnect customers if they detect they run an open proxy or tor exit node.<ul><li>Speaking of <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener" target="_blank">@torproject</a>, the bandwith of <a href="https://infosec.space/tags/ExitNodes" class="mention hashtag" rel="nofollow noopener" target="_blank">#ExitNodes</a> is way too low for any industrial-scale <a href="https://infosec.space/tags/scraping" class="mention hashtag" rel="nofollow noopener" target="_blank">#scraping</a> operation needed.</li></ul>

Kevin Karhan :verified:<a href="https://infosec.exchange/@tasket" class="u-url mention" rel="nofollow noopener" target="_blank">@tasket</a> I don't say @tor#Tor is perfect - far from it.BUT an <a href="https://infosec.space/tags/OnionService" class="mention hashtag" rel="nofollow noopener" target="_blank">#OnionService</a> is way easier to conceal, shield and secure than a <a href="https://infosec.space/tags/SurfaceWeb" class="mention hashtag" rel="nofollow noopener" target="_blank">#SurfaceWeb</a> site.<ul><li>Also the main disadvantage of Tor is speed and the fact that <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener" target="_blank">@torproject</a> publishes their <a href="https://infosec.space/tags/ExitNodes" class="mention hashtag" rel="nofollow noopener" target="_blank">#ExitNodes</a>, so blocking Tor users is too easy.</li></ul>Needless to say that there may be different scenarios and it takes individual assessment of needs, capabilities and <a href="https://infosec.space/tags/ITsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#ITsec</a>, <a href="https://infosec.space/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#InfoSec</a>, <a href="https://infosec.space/tags/OpSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpSec</a> & <a href="https://infosec.space/tags/ComSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#ComSec</a> to the point that I think it's important to teach people to make that decision instead of blanket VPN shilling...<a href="https://infosec.space/tags/DontBlockTor" class="mention hashtag" rel="nofollow noopener" target="_blank">#DontBlockTor</a>

Kevin Karhan :verified:Q: Is there any Hoster that doesn't block or ban <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener" target="_blank">@torproject</a> ? <ul><li>Cuz <a href="https://infosec.space/tags/Contabo" class="mention hashtag" rel="nofollow noopener" target="_blank">#Contabo</a> <a href="https://contabo.com/en/legal/terms-and-conditions/" rel="nofollow noopener" target="_blank">does per their ToS</a>...</li></ul>I could understand it if they don't want <a href="https://infosec.space/tags/ExitNodes" class="mention hashtag" rel="nofollow noopener" target="_blank">#ExitNodes</a> and subsequent traffic to taint their rep, but they literally <a href="https://infosec.space/tags/ban" class="mention hashtag" rel="nofollow noopener" target="_blank">#ban</a> <a href="https://infosec.space/tags/Tor" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tor</a> entirely regardless if <a href="https://infosec.space/tags/OnionService" class="mention hashtag" rel="nofollow noopener" target="_blank">#OnionService</a>, <a href="https://infosec.space/tags/Relay" class="mention hashtag" rel="nofollow noopener" target="_blank">#Relay</a> or a private <a href="https://infosec.space/tags/Bridge" class="mention hashtag" rel="nofollow noopener" target="_blank">#Bridge</a>.<a href="https://infosec.space/tags/DontBlockTor" class="mention hashtag" rel="nofollow noopener" target="_blank">#DontBlockTor</a> <a href="https://infosec.space/tags/Bridges" class="mention hashtag" rel="nofollow noopener" target="_blank">#Bridges</a>

Kevin Karhan :verified:<a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener" target="_blank">@torproject</a> not to mention it's kinda sad that <a href="https://mstdn.social/tags/TorBulkExitList" class="mention hashtag" rel="nofollow noopener" target="_blank">#TorBulkExitList</a> still doesn't list <a href="https://mstdn.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv6</a> <a href="https://mstdn.social/tags/ExitNodes" class="mention hashtag" rel="nofollow noopener" target="_blank">#ExitNodes</a> to this day.That issue us 7 years (!!!) old. <a href="https://gitlab.torproject.org/tpo/anti-censorship/bridgedb/-/issues/19997" rel="nofollow noopener" translate="no" target="_blank">https://gitlab.torproject.org/tpo/anti-censorship/bridgedb/-/issues/19997</a> via <a href="https://mastodon.social/@isis" class="u-url mention" rel="nofollow noopener" target="_blank">@isis</a> <a href="https://check.torproject.org/torbulkexitlist" rel="nofollow noopener" translate="no" target="_blank">https://check.torproject.org/torbulkexitlist</a>

Recent searches

Search options

Administered by:

Server stats:

#exitnodes