Med-Mastodon

Kevin Karhan :verified:<a href="https://mastodon.thenewoil.org/@thenewoil" class="u-url mention" rel="nofollow noopener" target="_blank">@thenewoil</a> which it inevitably does!<ul><li>There is no way to do effective <a href="https://infosec.space/tags/AgeVerification" class="mention hashtag" rel="nofollow noopener" target="_blank">#AgeVerification</a> without <a href="https://infosec.space/tags/Deanonymization" class="mention hashtag" rel="nofollow noopener" target="_blank">#Deanonymization</a> - either explicit or implicit.</li></ul>

LisPiOne issue I consider to remain with low-latency mixnets and overlay networks is that downtime can be deanonymizing. Even if one has constant bitrate with randomly-selected short downtime/network degradation simulation, that doesn't really help when one's town loses power entirely a few times in a year or whatever and someone bothers to try and map the downtimes onto known locations of power outages over the same year. Is there any sensible model for handling this failure case? <a class="hashtag" href="https://udongein.xyz/tag/mixnet" rel="nofollow noopener" target="_blank">#Mixnet</a> <a class="hashtag" href="https://udongein.xyz/tag/timinganalysis" rel="nofollow noopener" target="_blank">#TimingAnalysis</a> <a class="hashtag" href="https://udongein.xyz/tag/sidechannels" rel="nofollow noopener" target="_blank">#SideChannels</a> <a class="hashtag" href="https://udongein.xyz/tag/anonymization" rel="nofollow noopener" target="_blank">#Anonymization</a> <a class="hashtag" href="https://udongein.xyz/tag/deanonymization" rel="nofollow noopener" target="_blank">#Deanonymization</a> <a class="hashtag" href="https://udongein.xyz/tag/whynodirecttageditinginapobjectsyet" rel="nofollow noopener" target="_blank">#WhyNoDirectTagEditingInAPObjectsYet</a>

Kevin Karhan :verified:Apparently the <a href="https://social.bau-ha.us/@CCC" class="u-url mention" rel="nofollow noopener" target="_blank">@CCC</a> has some infos <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener" target="_blank">@torproject</a> needs, and <a href="http://dreadytofatroptsdj6io7l3xptbet6onoyno2yv7jicoxknyazubrad.onion/post/bb8ca1c9262a0af96640" rel="nofollow noopener" target="_blank">it seems they're desperate to get their hands onto that intel</a>.<ul><li>Dear folks at the <a href="https://infosec.space/tags/CCC" class="mention hashtag" rel="nofollow noopener" target="_blank">#CCC</a>, do the right and responsibe thing and send the details to <a href="https://infosec.space/tags/TorProject" class="mention hashtag" rel="nofollow noopener" target="_blank">#TorProject</a> so they can assess the relevance re: <a href="https://infosec.space/tags/Tor" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tor</a> and take appropriate steps!</li></ul>Anyone who has details is asked to sent them in a <a href="https://infosec.space/tags/PGP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PGP</a>/MIME-encrypted eMail to [security@torproject.org]( malto:security@torproject.org ) using the Pubkey [ 835B 4E04 F6F7 4211 04C4 751A 3EF9 EF99 6604 DE41 ]( <a href="https://keys.openpgp.org/vks/v1/by-fingerprint/835B4E04F6F7421104C4751A3EF9EF996604DE41" rel="nofollow noopener" translate="no" target="_blank">https://keys.openpgp.org/vks/v1/by-fingerprint/835B4E04F6F7421104C4751A3EF9EF996604DE41</a> ].<ul><li>Anonymous submissions are accepted AFAICT - All they care is to enshure the <a href="https://infosec.space/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> of Tor <a href="https://infosec.space/tags/users" class="mention hashtag" rel="nofollow noopener" target="_blank">#users</a> against <a href="https://infosec.space/tags/deanonymization" class="mention hashtag" rel="nofollow noopener" target="_blank">#deanonymization</a> attacks, which can and will be leveraged by <a href="https://infosec.space/tags/dictatorships" class="mention hashtag" rel="nofollow noopener" target="_blank">#dictatorships</a> and supressive <a href="https://infosec.space/tags/regimes" class="mention hashtag" rel="nofollow noopener" target="_blank">#regimes</a> if not addressed!</li></ul><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> <a href="https://infosec.space/tags/TorNetwork" class="mention hashtag" rel="nofollow noopener" target="_blank">#TorNetwork</a> <a href="https://infosec.space/tags/dread" class="mention hashtag" rel="nofollow noopener" target="_blank">#dread</a> <a href="https://infosec.space/tags/CyberSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#CyberSecurity</a> <a href="https://infosec.space/tags/News" class="mention hashtag" rel="nofollow noopener" target="_blank">#News</a> <a href="https://infosec.space/tags/PleaseBoost" class="mention hashtag" rel="nofollow noopener" target="_blank">#PleaseBoost</a> <a href="https://infosec.space/tags/FollowerPower" class="mention hashtag" rel="nofollow noopener" target="_blank">#FollowerPower</a> <a href="https://infosec.space/tags/CyberSecurityNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#CyberSecurityNews</a> <a href="https://infosec.space/tags/forensics" class="mention hashtag" rel="nofollow noopener" target="_blank">#forensics</a> <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FLOSS</a> <a href="https://infosec.space/tags/FOOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOOS</a> <a href="https://infosec.space/tags/OSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OSS</a> <a href="https://infosec.space/tags/hardening" class="mention hashtag" rel="nofollow noopener" target="_blank">#hardening</a> <a href="https://infosec.space/tags/CyberAttacks" class="mention hashtag" rel="nofollow noopener" target="_blank">#CyberAttacks</a> äDigitalForensics <a href="https://infosec.space/tags/TorBrowser" class="mention hashtag" rel="nofollow noopener" target="_blank">#TorBrowser</a>

h o ʍ l e t t<a href="https://mamot.fr/tags/Urgence" class="mention hashtag" rel="nofollow noopener" target="_blank">#Urgence</a> à FranceTélévisions : inventer le <a href="https://mamot.fr/tags/floutage" class="mention hashtag" rel="nofollow noopener" target="_blank">#floutage</a> de demain <a href="https://larevuedesmedias.ina.fr/urgence-france-televisions-inventer-le-floutage-de-demain" rel="nofollow noopener" translate="no" target="_blank">https://larevuedesmedias.ina.fr/urgence-france-televisions-inventer-le-floutage-de-demain</a> <a href="https://mamot.fr/tags/FranceTV" class="mention hashtag" rel="nofollow noopener" target="_blank">#FranceTV</a> is creating a new <a href="https://mamot.fr/tags/anonymity" class="mention hashtag" rel="nofollow noopener" target="_blank">#anonymity</a> charter with strict <a href="https://mamot.fr/tags/guidelines" class="mention hashtag" rel="nofollow noopener" target="_blank">#guidelines</a> on <a href="https://mamot.fr/tags/voice" class="mention hashtag" rel="nofollow noopener" target="_blank">#voice</a> and face anonymization to protect <a href="https://mamot.fr/tags/sources" class="mention hashtag" rel="nofollow noopener" target="_blank">#sources</a>, as current anonymization methods are susceptible to <a href="https://mamot.fr/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#AI</a>-driven <a href="https://mamot.fr/tags/deanonymization" class="mention hashtag" rel="nofollow noopener" target="_blank">#deanonymization</a>. After reviewing 1100 news segments, 30 were unpublished due to high deanonymization <a href="https://mamot.fr/tags/risk" class="mention hashtag" rel="nofollow noopener" target="_blank">#risk</a>.

LisPi<a href="https://infosec.exchange/@iampytest1" class="u-url mention" rel="nofollow noopener" target="_blank">@iampytest1</a> <a href="https://hachyderm.io/@dalias" class="u-url mention" rel="nofollow noopener" target="_blank">@dalias</a> <a href="https://mastodon.social/@campuscodi" class="u-url mention" rel="nofollow noopener" target="_blank">@campuscodi</a> So basically this is the same old "don't expose <a href="https://mastodon.top/tags/darknet" class="mention hashtag" rel="nofollow noopener" target="_blank">#darknet</a> servers to the <a href="https://mastodon.top/tags/clearnet" class="mention hashtag" rel="nofollow noopener" target="_blank">#clearnet</a>" thing?I'd be wary of even reusing the same server across different <a href="https://mastodon.top/tags/darknets" class="mention hashtag" rel="nofollow noopener" target="_blank">#darknets</a>, and spinning up a VM for each is cheap-enough to do with little-enough hassle there's really no good reason not to do it.<a href="https://mastodon.top/tags/Anonymization" class="mention hashtag" rel="nofollow noopener" target="_blank">#Anonymization</a> <a href="https://mastodon.top/tags/DeAnonymization" class="mention hashtag" rel="nofollow noopener" target="_blank">#DeAnonymization</a>

Recent searches

Search options

Administered by:

Server stats:

#deanonymization