Le Pouls Du Monde

Kevin Karhan :verified:<a href="https://mastodon.social/@dzwiedziu" class="u-url mention" rel="nofollow noopener" target="_blank">@dzwiedziu</a> <a href="https://mastodon.social/@fj" class="u-url mention" rel="nofollow noopener" target="_blank">@fj</a> <a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener" target="_blank">@signalapp</a> not really, as the <a href="https://infosec.space/tags/Metadata" class="mention hashtag" rel="nofollow noopener" target="_blank">#Metadata</a> <a href="https://infosec.space/tags/FUD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FUD</a> cited by <a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Signal</a> is mitigateable with proper measures.<ul><li>You can't even run Signal over <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener" target="_blank">@torproject</a> and even if that point is moot when you're forced to quasi-<a href="https://infosec.space/tags/KYC" class="mention hashtag" rel="nofollow noopener" target="_blank">#KYC</a> by virtue of a <a href="https://infosec.space/tags/PhoneNumber" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhoneNumber</a> aka. <a href="https://infosec.space/tags/PII" class="mention hashtag" rel="nofollow noopener" target="_blank">#PII</a> they have neither legitimate interest nor technical reason to demand in the first place!</li></ul>Every claim that things like <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> can be solved with "Just use Signal!" is "<a href="https://infosec.space/tags/TechPopulism" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechPopulism</a>" at best if not being a "<a href="https://infosec.space/tags/UsefulIdiot" class="mention hashtag" rel="nofollow noopener" target="_blank">#UsefulIdiot</a>"!<ul><li>All <a href="https://infosec.space/tags/centralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#centralized</a>, <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleVendor</a> & <a href="https://infosec.space/tags/SingleProbider" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleProbider</a> systems are inherently insecure!</li></ul><a href="https://infosec.space/tags/EOD" class="mention hashtag" rel="nofollow noopener" target="_blank">#EOD</a> <a href="https://infosec.space/tags/thxbye" class="mention hashtag" rel="nofollow noopener" target="_blank">#thxbye</a> <a href="https://infosec.space/tags/next" class="mention hashtag" rel="nofollow noopener" target="_blank">#next</a>

Kevin Karhan :verified:<a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener" target="_blank">@signalapp</a> I disagree because your platform is <a href="https://infosec.space/tags/proprietary" class="mention hashtag" rel="nofollow noopener" target="_blank">#proprietary</a>, <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleVendor</a>, <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleProvider</a> and doesn't allow for <a href="https://infosec.space/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosting</a>, <a href="https://infosec.space/tags/SelfCustody" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfCustody</a> of all the Keys and you demand <a href="https://infosec.space/tags/PII" class="mention hashtag" rel="nofollow noopener" target="_blank">#PII</a> in the form of a <a href="https://infosec.space/tags/PhoneNumber" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhoneNumber</a> which can be used.to track users down!<ul><li>If <a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Signal</a> was as secure as claimed, it would've been shut down like <a href="https://infosec.space/tags/EncroChat" class="mention hashtag" rel="nofollow noopener" target="_blank">#EncroChat</a>, <a href="https://infosec.space/tags/SkyECC" class="mention hashtag" rel="nofollow noopener" target="_blank">#SkyECC</a> & others...</li></ul>

Kevin Karhan :verified:<a href="https://mastodon.social/@walkinglampshade" class="u-url mention" rel="nofollow noopener" target="_blank">@walkinglampshade</a> <a href="https://mastodon.world/@jrredho" class="u-url mention" rel="nofollow noopener" target="_blank">@jrredho</a> <a href="https://mastodon.social/@fj" class="u-url mention" rel="nofollow noopener" target="_blank">@fj</a> It's basic <a href="https://infosec.space/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#InfoSec</a>, really:<ul><li><a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener" target="_blank">@signalapp</a> has no "<a href="https://infosec.space/tags/LegitimateInterest" class="mention hashtag" rel="nofollow noopener" target="_blank">#LegitimateInterest</a>" to demand <a href="https://infosec.space/tags/PII" class="mention hashtag" rel="nofollow noopener" target="_blank">#PII</a> like a <a href="https://infosec.space/tags/PhoneNumber" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhoneNumber</a> and they use and abuse that to restrict functionality of their App (it doesn't matter that they merely claim "comply with <a href="https://infosec.space/tags/sanctions" class="mention hashtag" rel="nofollow noopener" target="_blank">#sanctions</a>" [their <a href="https://infosec.space/tags/MobileCoin" class="mention hashtag" rel="nofollow noopener" target="_blank">#MobileCoin</a> <a href="https://infosec.space/tags/Shitcoin" class="mention hashtag" rel="nofollow noopener" target="_blank">#Shitcoin</a> <a href="https://infosec.space/tags/Scam" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scam</a> disqalifies them even more!] because they have the tech to distinguish and discriminate users)...</li></ul>Thus <a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Signal</a> fails at protevting <a href="https://infosec.space/tags/Journalists" class="mention hashtag" rel="nofollow noopener" target="_blank">#Journalists</a> and theor sources because they do have that data and can be <a href="https://infosec.space/tags/subopena" class="mention hashtag" rel="nofollow noopener" target="_blank">#subopena</a>'d for it if they don't already provide <a href="https://infosec.space/tags/BulkSurveillance" class="mention hashtag" rel="nofollow noopener" target="_blank">#BulkSurveillance</a> & <a href="https://infosec.space/tags/LawfulInterception" class="mention hashtag" rel="nofollow noopener" target="_blank">#LawfulInterception</a> <a href="https://infosec.space/tags/API" class="mention hashtag" rel="nofollow noopener" target="_blank">#API</a>|s to comply with <a href="https://infosec.space/tags/CloudAct" class="mention hashtag" rel="nofollow noopener" target="_blank">#CloudAct</a>. (Or are you guys so naive and believe <a href="https://mastodon.world/@Mer__edith" class="u-url mention" rel="nofollow noopener" target="_blank">@Mer__edith</a> will risk <a href="https://web.archive.org/web/20210606070919/twitter.com/thegrugq/status/1085614812581715968" rel="nofollow noopener" target="_blank">dying of old age in jail for non-paying users?</a>)<ul><li>This entire "thread vector" just doesn't exist with <a href="https://infosec.space/tags/XMPP" class="mention hashtag" rel="nofollow noopener" target="_blank">#XMPP</a>+<a href="https://infosec.space/tags/OMEMO" class="mention hashtag" rel="nofollow noopener" target="_blank">#OMEMO</a> nor <a href="https://infosec.space/tags/PGP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PGP</a>/MIME! </li></ul>And if you believe "this won't ne used/abused me because I'm from 'Murica!" and point at <a href="https://infosec.space/tags/AN%C3%98M" class="mention hashtag" rel="nofollow noopener" target="_blank">#ANØM</a> as an example, then you really ignored all tze <a href="https://infosec.space/tags/Cyberfacism" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cyberfacism</a> since 9/11…

Kevin Karhan :verified:<a href="https://mastodon.social/@fj" class="u-url mention" rel="nofollow noopener" target="_blank">@fj</a> I still think <a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener" target="_blank">@signalapp</a> has fundamental flaws like demanding <a href="https://infosec.space/tags/PII" class="mention hashtag" rel="nofollow noopener" target="_blank">#PII</a> (<a href="https://infosec.space/tags/PhoneNumbers" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhoneNumbers</a> can't be obtained anonymously around the globe and are trivial to track down to devices and thus users), being subject to <a href="https://infosec.space/tags/CloudAct" class="mention hashtag" rel="nofollow noopener" target="_blank">#CloudAct</a> as an unnecessary & 100% avoidable risk as well as <a href="https://infosec.space/tags/Shitcoin" class="mention hashtag" rel="nofollow noopener" target="_blank">#Shitcoin</a>-<a href="https://infosec.space/tags/Scam" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scam</a> shilling (<a href="https://infosec.space/tags/MobileCoin" class="mention hashtag" rel="nofollow noopener" target="_blank">#MobileCoin</a>) and it's <a href="https://infosec.space/tags/proprietary" class="mention hashtag" rel="nofollow noopener" target="_blank">#proprietary</a>, <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleVendor</a> & <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleProvider</a> nature that makes it inferior to real <a href="https://infosec.space/tags/E2EE" class="mention hashtag" rel="nofollow noopener" target="_blank">#E2EE</a> with <a href="https://infosec.space/tags/SelfCustody" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfCustody</a> like <a href="https://infosec.space/tags/PGP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PGP</a>/MIME & <a href="https://infosec.space/tags/XMPP" class="mention hashtag" rel="nofollow noopener" target="_blank">#XMPP</a>+<a href="https://infosec.space/tags/OMEMO" class="mention hashtag" rel="nofollow noopener" target="_blank">#OMEMO</a>!

NonilexIn an interview Fri, Dudek argued that the judge’s ruling was *overly broad* & that a reference to “DOGE affiliates” could apply to all employees who access personally identifiable info, or <a href="https://masto.ai/tags/PII" class="mention hashtag" rel="nofollow noopener" target="_blank">#PII</a>, because they are obligated to cooperate w/ <a href="https://masto.ai/tags/DOGE" class="mention hashtag" rel="nofollow noopener" target="_blank">#DOGE</a>.Dudek said the agency plans to file an affidavit as soon as Fri asking Hollander to clarify language in her ruling….  “Everything in this agency is PII. Unless I get clarification, I’ll just start to shut it down. I don’t have much of a choice here.”

Recent searches

Search options

Administered by:

Server stats:

#pii