Social 📸 Photography

boredsquirrelA few counterarguments on <a href="https://tux.social/tags/LocalMess" class="mention hashtag" rel="nofollow noopener" target="_blank">#LocalMess</a> (<a href="https://tux.social/tags/Facebook" class="mention hashtag" rel="nofollow noopener" target="_blank">#Facebook</a> <a href="https://tux.social/tags/Instagram" class="mention hashtag" rel="nofollow noopener" target="_blank">#Instagram</a> <a href="https://tux.social/tags/Yandex" class="mention hashtag" rel="nofollow noopener" target="_blank">#Yandex</a> <a href="https://tux.social/tags/LocalhostTracking" class="mention hashtag" rel="nofollow noopener" target="_blank">#LocalhostTracking</a>), why this would make <a href="https://tux.social/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#Android</a> worse than <a href="https://tux.social/tags/iOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#iOS</a>:This vuln seems to only have existed on Android, but not everyone would need to be affected by it.I see <a href="https://tux.social/tags/GrapheneOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#GrapheneOS</a> as a perfected form of the Android idea (stripping the <a href="https://tux.social/tags/Advertizing" class="mention hashtag" rel="nofollow noopener" target="_blank">#Advertizing</a> and Tracking from it, and adding needed permissions).1/8

Kevin Karhan :verified:<a href="https://mstdn.social/@BrodieOnLinux" class="u-url mention" rel="nofollow noopener" target="_blank">@BrodieOnLinux</a> <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener" target="_blank">@torproject</a> <a href="https://social.librem.one/@guardianproject" class="u-url mention" rel="nofollow noopener" target="_blank">@guardianproject</a> At this point I'd like to ask when <a href="https://ec.social-network.europa.eu/@EUCommission" class="u-url mention" rel="nofollow noopener" target="_blank">@EUCommission</a> and other <a href="https://infosec.space/tags/regulators" class="mention hashtag" rel="nofollow noopener" target="_blank">#regulators</a> start <a href="https://infosec.space/tags/banning" class="mention hashtag" rel="nofollow noopener" target="_blank">#banning</a> <a href="https://infosec.space/tags/StasiBook" class="mention hashtag" rel="nofollow noopener" target="_blank">#StasiBook</a> and other <a href="https://infosec.space/tags/GAFAM" class="mention hashtag" rel="nofollow noopener" target="_blank">#GAFAM</a>|s for their blatant actions as <a href="https://infosec.space/tags/OrganizedCrime" class="mention hashtag" rel="nofollow noopener" target="_blank">#OrganizedCrime</a> to violate <a href="https://infosec.space/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#privacy</a> standards in the <a href="https://infosec.space/tags/EU" class="mention hashtag" rel="nofollow noopener" target="_blank">#EU</a> and elsewhere?<a href="https://infosec.space/@kkarhan/114733606176520273" translate="no" rel="nofollow noopener" target="_blank">https://infosec.space/@kkarhan/114733606176520273</a>Cuz at this point the €32B fines at maximum are a joke. <ul><li>I think that people espechally in Germany who may be affected [I'm not!] consider seeking legal advice and potentially file charges for said <a href="https://www.gesetze-im-internet.de/stgb/__202c.html" rel="nofollow noopener" target="_blank">digital espionage</a> and <a href="https://www.gesetze-im-internet.de/stgb/__303b.html" rel="nofollow noopener" target="_blank">computer sabotage</a> against <a href="https://infosec.space/tags/NSAbook" class="mention hashtag" rel="nofollow noopener" target="_blank">#NSAbook</a>! </li></ul>Simply because this isn't a mere violation of <a href="https://infosec.space/tags/GDPR" class="mention hashtag" rel="nofollow noopener" target="_blank">#GDPR</a>, <a href="https://infosec.space/tags/BDSG" class="mention hashtag" rel="nofollow noopener" target="_blank">#BDSG</a> and other standards, but literal <a href="https://infosec.space/tags/malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#malware</a> that has been deployed against users in the wild... <ul><li>Anything but actual prison sentences & arrest warrants against the persons responsible would be undue leniency.</li></ul><a href="https://infosec.space/tags/Spyware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Spyware</a> <a href="https://infosec.space/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#InfoSec</a> <a href="https://infosec.space/tags/ComSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#ComSec</a> <a href="https://infosec.space/tags/ITsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#ITsec</a> <a href="https://infosec.space/tags/OpSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpSec</a> <a href="https://infosec.space/tags/LocalhostTracking" class="mention hashtag" rel="nofollow noopener" target="_blank">#LocalhostTracking</a> <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Govware</a> <a href="https://infosec.space/tags/StasiBook" class="mention hashtag" rel="nofollow noopener" target="_blank">#StasiBook</a> <a href="https://infosec.space/tags/Facebook" class="mention hashtag" rel="nofollow noopener" target="_blank">#Facebook</a> <a href="https://infosec.space/tags/Meta" class="mention hashtag" rel="nofollow noopener" target="_blank">#Meta</a>

Kevin Karhan :verified:The fact that <a href="https://infosec.space/tags/NSAbook" class="mention hashtag" rel="nofollow noopener" target="_blank">#NSAbook</a> is literally developing <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Govware</a> to track users and bypass <a href="https://infosec.space/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#Android</a> <a href="https://infosec.space/tags/sandbox" class="mention hashtag" rel="nofollow noopener" target="_blank">#sandbox</a> as well as <a href="https://infosec.space/tags/tracking" class="mention hashtag" rel="nofollow noopener" target="_blank">#tracking</a> them regardless of <a href="https://infosec.space/tags/VPN" class="mention hashtag" rel="nofollow noopener" target="_blank">#VPN</a>, <a href="https://infosec.space/tags/Cookies" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cookies</a> or <a href="https://infosec.space/tags/IncognitoMode" class="mention hashtag" rel="nofollow noopener" target="_blank">#IncognitoMode</a> use or blockage.<a href="https://www.youtube.com/watch?v=LUtctMShGJw" rel="nofollow noopener" translate="no" target="_blank">https://www.youtube.com/watch?v=LUtctMShGJw</a> via <a href="https://mstdn.social/@BrodieOnLinux" class="u-url mention" rel="nofollow noopener" target="_blank">@BrodieOnLinux</a> More to readup upon. <a href="https://redact.dev/blog/meta-yandex-localhost-tracking" rel="nofollow noopener" translate="no" target="_blank">https://redact.dev/blog/meta-yandex-localhost-tracking</a> <a href="https://www.zeropartydata.es/p/localhost-tracking-explained-it-could" rel="nofollow noopener" translate="no" target="_blank">https://www.zeropartydata.es/p/localhost-tracking-explained-it-could</a><a href="https://infosec.space/tags/Spyware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Spyware</a> <a href="https://infosec.space/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#InfoSec</a> <a href="https://infosec.space/tags/ComSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#ComSec</a> <a href="https://infosec.space/tags/ITsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#ITsec</a> <a href="https://infosec.space/tags/OpSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpSec</a> <a href="https://infosec.space/tags/Malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Malware</a> <a href="https://infosec.space/tags/LocalhostTracking" class="mention hashtag" rel="nofollow noopener" target="_blank">#LocalhostTracking</a> <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Govware</a> <a href="https://infosec.space/tags/StasiBook" class="mention hashtag" rel="nofollow noopener" target="_blank">#StasiBook</a> <a href="https://infosec.space/tags/Facebook" class="mention hashtag" rel="nofollow noopener" target="_blank">#Facebook</a> <a href="https://infosec.space/tags/Meta" class="mention hashtag" rel="nofollow noopener" target="_blank">#Meta</a>

m_berberich<a href="https://social.heise.de/@heiseonline" class="u-url mention" rel="nofollow noopener" target="_blank">@heiseonline</a> <blockquote>Die Chats selbst sollen davon aber nicht betroffen sein, beteuert das Unternehmen.</blockquote>Nur zur Info: Das ist das gleiche Unternehmen, daß mit localhost tracking die Sicherheitsmechanismen von Android umgangen hat um Benutzer besser tracken zu können·<a href="https://infosec.exchange/@isotopp/114663960595107813" translate="no" rel="nofollow noopener" target="_blank">https://infosec.exchange/@isotopp/114663960595107813</a><a href="https://infosec.exchange/tags/Meta" class="mention hashtag" rel="nofollow noopener" target="_blank">#Meta</a> <a href="https://infosec.exchange/tags/Whatsapp" class="mention hashtag" rel="nofollow noopener" target="_blank">#Whatsapp</a> <a href="https://infosec.exchange/tags/localhosttracking" class="mention hashtag" rel="nofollow noopener" target="_blank">#localhosttracking</a>

Recent searches

Search options

Administered by:

Server stats:

#localhosttracking