Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
veganism.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Veganism Social is a welcoming space on the internet for vegans to connect and engage with the broader decentralized social media community.

Administered by:

Server stats:

196
active users

veganism.social: AboutStatusPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#backdoored

0 posts0 participants0 posts today
PrivacyDigest<p>Sellers of Anom, the FBI's Secret <a href="https://mas.to/tags/Backdoored" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Backdoored</span></a> Phone, Plead Guilty </p><p>The court records released as part of the plea deals also provide new insight into how some of the phone sellers discussed drug <a href="https://mas.to/tags/trafficking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>trafficking</span></a> on their <a href="https://mas.to/tags/Anom" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Anom</span></a> devices as well.<br><a href="https://mas.to/tags/privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>privacy</span></a> <a href="https://mas.to/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>security</span></a> <a href="https://mas.to/tags/backdoor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>backdoor</span></a></p><p><a href="https://www.404media.co/sellers-of-anom-the-fbis-secret-backdoored-phone-plead-guilty/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">404media.co/sellers-of-anom-th</span><span class="invisible">e-fbis-secret-backdoored-phone-plead-guilty/</span></a></p>
PrivacyDigest<p>Government to Name ‘Key Witness’ Who Provided <a href="https://mas.to/tags/FBI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FBI</span></a> With <a href="https://mas.to/tags/Backdoored" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Backdoored</span></a> <a href="https://mas.to/tags/Encrypted" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Encrypted</span></a> <a href="https://mas.to/tags/Chat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Chat</span></a> App <a href="https://mas.to/tags/Anom" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Anom</span></a> <br><a href="https://mas.to/tags/privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>privacy</span></a> <a href="https://mas.to/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>security</span></a> </p><p><a href="https://www.404media.co/government-to-name-key-witness-who-provided-fbi-with-backdoored-encrypted-chat-app-anom-2/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">404media.co/government-to-name</span><span class="invisible">-key-witness-who-provided-fbi-with-backdoored-encrypted-chat-app-anom-2/</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://transfem.social/@puppygirlhornypost2" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>puppygirlhornypost2</span></a></span> <span class="h-card" translate="no"><a href="https://social.vlhl.dev/users/navi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>navi</span></a></span> yeah, but that's a common problem based off <a href="https://infosec.space/tags/TechIlliteracy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TechIlliteracy</span></a> and lack of proper explaination!</p><ul><li>Given the <a href="https://infosec.space/tags/CryptoAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CryptoAPI</span></a> of <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Windows</span></a> is <a href="https://infosec.space/tags/backdoored" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>backdoored</span></a> for <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Govware</span></a> [<a href="https://infosec.space/tags/NSAKEY_" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>NSAKEY_</span></a> &amp; <a href="https://infosec.space/tags/SSL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SSL</span></a>-<a href="https://github.com/kkarhan/windows-ca-backdoor-fix" rel="nofollow noopener noreferrer" target="_blank">Updates</a> I'd consider <a href="https://infosec.space/tags/BitLocker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BitLocker</span></a> insecure and the least of it's problems!</li></ul><p>Bonus points if <a href="https://infosec.space/tags/TPM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TPM</span></a> bs prevents <a href="https://infosec.space/tags/DataRecovery" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DataRecovery</span></a>.</p><ul><li>My biggest problem with <a href="https://infosec.space/tags/FDE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FDE</span></a>/ <a href="https://infosec.space/tags/FullDiskEncryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FullDiskEncryption</span></a> is that is mandates direct access to a system to authenticate, thus one needs to manually mount stuff on servers post-boot instead.</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mas.to/@tokyo_0" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>tokyo_0</span></a></span> Well, <a href="https://infosec.space/tags/VeraCrypt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>VeraCrypt</span></a> does get audited from time to time, and it's so far the only <a href="https://infosec.space/tags/CrossPlatform" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CrossPlatform</span></a> <a href="https://infosec.space/tags/FullDiskEncryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FullDiskEncryption</span></a> solution there is that isn't a <a href="https://infosec.space/tags/proprietary" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>proprietary</span></a> <em>"<a href="https://infosec.space/tags/TrustMeBroWare" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TrustMeBroWare</span></a>"</em> or flatout <a href="https://infosec.space/tags/backdoored" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>backdoored</span></a>. </p><p>There are numerous reasons why <a href="https://infosec.space/tags/TrueCrypt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TrueCrypt</span></a> got forked into VeraCrypt and I'm shure the <a href="https://infosec.space/tags/Wikipedia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Wikipedia</span></a> articles mention why...</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mas.to/@tokyo_0" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>tokyo_0</span></a></span> <a href="https://infosec.space/tags/TrueCrypt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TrueCrypt</span></a> is <a href="https://infosec.space/tags/abandonware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>abandonware</span></a> with serious security issues. </p><ul><li><em>DO NOT USE TRUECRYPT FFS!!!</em></li></ul><p>Use <a href="https://infosec.space/tags/VeraCrypt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>VeraCrypt</span></a> or even better: migrate machines to <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> and use <a href="https://infosec.space/tags/LUKS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LUKS</span></a> / <a href="https://infosec.space/tags/dmcrypt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dmcrypt</span></a> instead, as it's the best option at hand.</p><ul><li>If you need to shuttle data to <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Windows</span></a> and <a href="https://infosec.space/tags/macOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>macOS</span></a> machines and using <a href="https://infosec.space/tags/SFTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SFTP</span></a> / <a href="https://infosec.space/tags/SSHFS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SSHFS</span></a> to mount a secure storage over the network isn't an option, than you're stuck with VeraCrypt, as <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Windows</span></a>' <a href="https://infosec.space/tags/CryptoAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CryptoAPI</span></a> is evidently <a href="https://infosec.space/tags/backdoored" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>backdoored</span></a> to the point that every <a href="https://infosec.space/tags/Browser" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Browser</span></a> except <a href="https://infosec.space/tags/Firefox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Firefox</span></a> is susceptible to <a href="https://infosec.space/tags/SSL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SSL</span></a> hijacking with background updates...</li></ul><p><a href="https://github.com/kkarhan/windows-ca-backdoor-fix" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/kkarhan/windows-ca-</span><span class="invisible">backdoor-fix</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://chaos.social/@frumble" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>frumble</span></a></span> alle <a href="https://infosec.space/tags/GSMA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GSMA</span></a>-Standards sind <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Govware</span></a>-<a href="https://infosec.space/tags/backdoored" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>backdoored</span></a> seit <a href="https://infosec.space/tags/GSM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GSM</span></a>...</p><p>Da gibt's nix zu fixen!</p><p>Meanwhile <a href="https://infosec.space/tags/Cisco" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Cisco</span></a>, <a href="https://infosec.space/tags/Juniper" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Juniper</span></a> &amp; Co. integrierten <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Govware</span></a> wie <a href="https://infosec.space/tags/DUAL_EC_DRBG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DUAL_EC_DRBG</span></a> und hben sich bis heute dafür nicht entschuldigt!</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://infosec.space/@wravoc" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>wravoc</span></a></span> IMHO, <a href="https://infosec.space/tags/TPM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TPM</span></a> &amp; <a href="https://infosec.space/tags/UEFI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>UEFI</span></a> are both <a href="https://infosec.space/tags/Scams" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Scams</span></a> and neither can be trusted due to being <a href="https://infosec.space/tags/backdoored" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>backdoored</span></a> and <a href="https://infosec.space/tags/Bloatware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Bloatware</span></a> respectably.</p><p>Personally, I want a machine that is purposefully <a href="https://infosec.space/tags/incompatible" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>incompatible</span></a> with <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CensorBoot</span></a> by <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Microsoft</span></a> (and thus <a href="https://infosec.space/tags/Windows11" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Windows11</span></a>) by using <a href="https://infosec.space/tags/LinuxBoot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LinuxBoot</span></a> / <a href="https://infosec.space/tags/NERF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>NERF</span></a> and no TPM at all!</p><p>Sadly I guess that means I've to use the <a href="https://infosec.space/tags/RISCv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RISCv</span></a> version of the <span class="h-card" translate="no"><a href="https://fosstodon.org/@frameworkcomputer" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>frameworkcomputer</span></a></span> mainboard for that...</p> <p>The fact that UEFI has more code than the <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> <a href="https://infosec.space/tags/Kernel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Kernel</span></a> with all it's drivers yet less than 100 contributors makes it inacceptable!</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@nuintari" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>nuintari</span></a></span> I think people should get firednfor buying <a href="https://infosec.space/tags/backdoored" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>backdoored</span></a> Networkibg gear like <a href="https://infosec.space/tags/Cisco" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Cisco</span></a> since they didn't even apologize for the <a href="https://infosec.space/tags/DUAL_ED_DRBG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DUAL_ED_DRBG</span></a> <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Govware</span></a> in their products...</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://pl.voltrina.net/users/voltrina" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>voltrina</span></a></span> because it's <a href="https://infosec.space/tags/backdoored" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>backdoored</span></a> if not <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Govware</span></a>...</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.gamedev.place/@YoSoyFreeman" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>YoSoyFreeman</span></a></span> <a href="https://infosec.space/tags/GSM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GSM</span></a> and all it's successors as well as competitiors are inherently <a href="https://infosec.space/tags/backdoored" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>backdoored</span></a> with so much <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Govware</span></a> that it should be considered "unfixably insecure under any circumstances"...</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://chaos.social/@Dexruus" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>Dexruus</span></a></span> <span class="h-card" translate="no"><a href="https://social.tchncs.de/@jesterchen" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>jesterchen</span></a></span> <span class="h-card" translate="no"><a href="https://ard.social/@tagesschau" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>tagesschau</span></a></span> das sowieso...</p><p>Außerdem hätte <a href="https://infosec.space/tags/eCall" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>eCall</span></a> anstelle bon <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Govware</span></a>-<a href="https://infosec.space/tags/backdoored" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>backdoored</span></a> <a href="https://infosec.space/tags/GSM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GSM</span></a> auch einfach nen <a href="https://infosec.space/tags/APRS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>APRS</span></a>-Paket auf <a href="https://infosec.space/tags/CB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CB</span></a>-Funk (27MHz-Band, Kanal 9) sein können...</p><p>Das würde wenigstens überall funktionieren unabhängig vom Handynetz und Einsatzkräften trivial die Peilung ermöglichen (bspw. wenn Fahrzeuge Böschungen hinab gefahren sind)...</p><p>Es ist halt bewusst so designed damit die <a href="https://infosec.space/tags/Anonymit%C3%A4t" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Anonymität</span></a> (<a href="https://infosec.space/tags/SIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SIM</span></a> seit 07.2017 nur gegen Identifikation) auch gleich für die Tonne ist!</p>
VegansExploreLive feeds
About