#Encryption

Hashing Is Not Encryption 🧩 Encryption reverses with a key. Hashing is one-way. 💡 Store passwords with Argon2id or bcrypt, never encryption. WhatsApp: #Hashing #Encryption

Lenovo sold its ThinkPlus FU100 as AES-256 encrypted. Inside: a plain SD card; the fingerprint just switched USB on. Codex pulled a hardcoded key out of Netac's protection in ~7 min. No published crypto design? Assume there's no crypto. #InfoSec #HardwareSecurity #Encryption

If one encryption key is exposed, can old chats still stay private? Forward secrecy is designed to help. Explore privacy tools at . #Privacy #Encryption #Cybersecurity #VPN Subscribe Now - unlock streaming freedom with VPNGENIX

Introducing Red-SecretsXAI — encryption with a distinctive visual encoding system, flexible key management, and developer-focused integrations. At Red-XAI, we’re building Red-SecretsXAI to give developers and users more control over how information is protected, packaged, shared, and recovered. Our goal goes beyond placing a password on a file. We’re bringing together encrypted containers, a custom red-X image format, multiple key-management options, and documented development interfaces in one toolkit. The red-X image is part of that system—not simply a logo or a decorative cover. Tiny numbers. Custom visual layers. A purpose-built decoder. Red-SecretsXAI’s QR-style red-X PNG uses micro-sized numerical glyphs embedded throughout the image. At normal viewing size, these tiny digits blend into the surrounding texture rather than appearing as readable numbers. The image format incorporates custom visual transformations and filtering. Its numerical patterns and surrounding visual layers must be interpreted correctly to reconstruct the encrypted payload. The decoder processes that structure, accounts for the corresponding transformations, and separates the encoded information from the surrounding texture. This is not an ordinary QR code that a standard barcode reader can interpret. A compatible decoder needs to understand the Red-SecretsXAI format and apply the appropriate decoding operations. After the encrypted payload is recovered from the image, it still has to pass cryptographic authentication and decryption using the required password or key material. That is the distinction: the image contributes a custom visual encoding and obfuscation layer, while the cryptographic layer protects the underlying information. They are separate stages working together within the same workflow—not a claim that hiding the appearance or implementation alone guarantees security. Protect more than a message. Red-SecretsXAI’s documented workflows cover text, individual files, folders, application bundles, archives, disk images, and supported drive operations. For straightforward sharing, password mode creates a self-contained encrypted file that opens with the correct password. For workflows that keep key material separately, port mode uses a dedicated .red-xai-port directory alongside the password. That gives users a choice between convenient password-based sharing and workflows where the encrypted file is kept separate from additional material required to open it. Plan for access—and for recovery. Encryption is only one part of protecting information. Keeping control of access, choosing where keys live, and preparing for lost credentials are equally important design decisions. Red-SecretsXAI documents optional workflows for port recovery, Shamir key cards, and hardware binding. These features have specific requirements: recovery options must be prepared in advance, hardware-binding strength depends on the available provider, and password-only files do not automatically receive a separate recovery mechanism. The toolkit also includes an optional decoy-password container, where different passwords open their corresponding payloads within the same sealed blob. This is a distinct SDK feature—not an automatic property of every encrypted file. We want these choices to be understandable, documented, and deliberate. Built for integration. Our public documentation includes guides for Python, JavaScript, C#, Java, and C++, together with a command-line interface distributed through the Python package. Developers can explore file-protection workflows, integrate supported operations into applications, and use the documented binary format across language implementations. Python provides the red-X image tooling; other SDKs can use the documented conversion workflow where direct image handling is unavailable. Features and platform support vary by SDK and package version, so the documentation identifies those differences rather than treating every interface as identical. The cryptographic core uses established primitives including Argon2id, ChaCha20-Poly1305, and HKDF. Red-SecretsXAI is currently pre-audit and has not yet undergone an independent external security audit. We believe that distinction should be stated openly. Security researchers and developers: put it to the test. We welcome people who want to evaluate Red-SecretsXAI, encrypt their own disposable test data, and investigate whether they can recover protected information without the required credentials—or identify another reproducible weakness. If you successfully bypass a protection, recover information you should not be able to access, or discover a vulnerability, please contact us privately and explain how you did it. Send your findings to support@infected-nation.com with the subject “SECURITY: Red-SecretsXAI.” Include the affected version, operating system, settings, exact reproduction steps, and a proof of concept using dummy data. Please explain what passwords, keys, ports, or recovery material you did or did not have access to during the test. Testing under this invitation is limited to your own files and an isolated local environment. It does not authorize attacks against our website, live infrastructure, third-party services, or anyone else’s devices or information. Our goal is to learn from reproducible findings and make the software more secure. Constructive technical scrutiny is welcome. We’re looking for investors and partners. Red-XAI is actively seeking investors, strategic partners, integration partners, and technical collaborators. We’re interested in conversations with developers, software companies, privacy-focused businesses, and investors who see value in advancing encryption tooling and practical data-protection workflows. We welcome opportunities to support independent security review, improve developer integrations, expand platform coverage, and explore useful applications of Red-SecretsXAI within other products. Whether your interest is integrating the toolkit, contributing technical expertise, supporting its development, or discussing a broader partnership, we would be glad to hear from you. Explore the documentation. Evaluate the technology. Help us build what comes next. Public documentation: Red-XAI website: Security reports, partnerships, and investment inquiries: support@infected-nation.com Red-SecretsXAI — encrypted information, custom visual encoding, and more deliberate control over access. #Encryption #CyberSecurity #SoftwareDevelopment #DeveloperTools #RedXAI

Researchers Demonstrated How #NSA Broke Trillions of Encrypted Connections #encryption #cryptography #hacking

“Encryption is for criminals.” Your bank login uses it. Your online checkout uses it. Your health portal uses it. Your work email uses it. Encryption isn’t how you hide a crime. It’s how an ordinary day stays ordinary.

ChatGPT now locks chats with a 4-digit PIN or Face ID, even on free. Not encryption, just a screen lock. Resetting the PIN deletes locked chats.

🆘🚨WHATS GOING ON IN CRYPTO RN???? The one privacy amendment in play is ConfidentialTransfer (spec XLS-96, "Confidential Transfers for Multi-Purpose Tokens"). It is the XRPL's first native privacy amendment. What it does •It would encrypt MPT balances and payment amounts. Accounts and token types stay visible. •It uses EC-ElGamal encryption and zero-knowledge proofs. •Validators can still mathematically verify total token supply. It includes selective disclosure with view keys so regulators can see transactions for compliance. •Balances are split into a spendable part and an "inbox" buffer, so outdated proofs don't freeze wallets. Limits in version one •Holders have to opt in to the encrypted format. •It covers direct account-to-account payments only, not DEX trades, escrow or checks. •It applies only to Multi-Purpose Tokens. XRP itself is not encrypted. Status •It shipped in XRPL version 3.3.0 on August 6, alongside five other amendments. •As of October 15 it had 22 validator votes. The activation threshold is 29. A dashboard snapshot from October 24 showed 21 of 35 votes. •To activate, it needs more than 80% of trusted validators, held continuously for two weeks. If support drops during that window, the timer restarts. It is not active and has no activation date.

ChatGPT can now lock a chat behind a 4-digit PIN or your device sign-in, and it hides that chat from history and search. Worth knowing: it's not end-to-end encryption. Would you actually use it?

Canada’s Bill C‑22 risks turning privacy protection into a conditional privilege, even after amendments intended to protect encryption. Its proposed section 2(4) generally prevents compelled decryption where the provider lacks the necessary information, but the definition of “systemic vulnerability” excludes certain risks confined to legally authorised targets. This creates a troubling ambiguity: an intervention aimed at one person may escape that particular safeguard even though the capability could introduce wider security risks. Lawful investigative authority cannot, by itself, establish that a technical intervention is secure. Citizen Lab’s October criticism challenges the assumption that companies can safely weaken cybersecurity protections. The unresolved question is how the targeted-risk exclusion interacts with the decryption safeguard. Neither an unrestricted backdoor mandate nor absolute protection for encryption can responsibly be inferred from the bill. For FaceTime, Signal, and other privacy services, the concern extends beyond access to existing records to pressure to build future collection capabilities. A September 2026 industry letter—including Tuta, Windscribe and Nord Security—warned that metadata retention could conflict with privacy-focused architectures and create valuable targets for attackers. If implementation weakens encryption-key protection or introduces exploitable interception mechanisms, the consequences could extend across Canada’s economy: financial institutions, major companies, emerging entrepreneurs, prominent business leaders and international investors could reconsider locating sensitive operations, capital and future investment in Canada. A perception that confidential financial and commercial communications are less secure could deter investment and encourage relocation, although an inevitable departure of all businesses would be an unsupported prediction. C‑22 should expressly prohibit compelled weakening of encryption and authentication, narrowly constrain retention, and guarantee independent technical scrutiny and effective judicial review before implementation. Protecting digital security is essential to protecting Canada’s economic credibility. @MarkJCarney , , @SenateCA , @yuenpauwoo , @denisebatters

EU's controversial proposal to scan private messages for CSAM detection raises alarms for end-to-end #encryption. Signal Foundation president warns of severe risks. Learn more: #cybersecurity #infosec #privacy

Windows Fix #17: BitLocker Recovery Key Bypass 🧵[1/8] Stuck in an endless BitLocker recovery loop on Windows 10/11? 🛑 Even after entering the correct 48-digit key, your PC keeps asking for it on every reboot? Don't panic — you don't always have to lose your data. Here are 6 proven ways to bypass & fix it! 👇 #WindowsFix #BitLocker #Windows10 #Windows11

🧵[3/8] Tweak Secure Boot & Legacy Boot Hardware changes or firmware updates often trigger BitLocker recovery loops. Try modifying your boot settings: 🔹 Toggle Secure Boot: Go to BIOS/UEFI > Security > Enable or Disable Secure Boot. Save (F10) and reboot. 🔹 Switch to Legacy Boot: Open CMD as Admin and run:bcdedit /set {default} bootmenupolicy legacy #WindowsFix #BIOS #UEFI

🧵[4/8] Turn Off Auto-Unlock Windows has an automatic unlock option enabled by default, which can cause the recovery screen to reappear continuously: 1️⃣ Open Control Panel 2️⃣ Navigate to System and Security > BitLocker Drive Encryption 3️⃣ Click Turn off auto-unlock for the encrypted drive This simple toggle often stops the loop on next restart! #WindowsFix #PCRepair

your “deleted” iphone photos aren’t deleted. my backup still had a seed phrase screenshot from 5 years ago i plugged the phone into my macbook, made a backup and asked claude code to run a security check on it it flagged PhotoData/Thumbnails thousands of files. photos, screenshots, document scans i thought were gone first find: the seed phrase screenshot i took “just for a second” second find: bank app screenshots with account numbers third find: photos of documents i cleared from Recently Deleted the big mistake: thinking delete + empty Recently Deleted = gone. small copies can outlive the original an unencrypted backup is just a folder on your mac then i checked Full Disk Access on the mac. way more apps than i expected, including ones i forgot i had. any app on that list can read that folder the fix: Finder → your iPhone → Encrypt local backup System Settings → Privacy & Security → Full Disk Access → cut what you don’t use the limit: this isn’t a remote hack. someone needs your phone, your mac or your backup. and with iCloud Photos on, your local backup may hold no photos at all if a seed phrase ever lived in your camera roll, treat that wallet as burned full prompt in the comments ↓

the prompt. paste it into claude code on your mac: “Run a read-only security check on my iPhone backups. Don’t delete, move or upload anything. Never open images with your file-reading tool and never print text found in them. Look in ~/Library/Application Support/MobileSync/Backup. If access is denied, tell me to add my terminal to Full Disk Access and stop. For each backup, read Manifest.plist: device name, date, and whether IsEncrypted is true. If encrypted, say it’s protected and skip it. Open Manifest.db with sqlite3 and map hashed files to real paths. Count files under Media/PhotoData/Thumbnails and Media/DCIM. If there are almost none, tell me iCloud Photos is probably on and stop. Run OCR locally (a small Swift script with Apple’s Vision framework, or tesseract via brew). Process everything on this Mac. Download the BIP39 English wordlist from Flag images with 12 or more BIP39 words as possible seed phrases. Also flag passwords, card or IBAN numbers, IDs and passport data. Save a report to ~/Desktop/backup-scan.txt: file path, image date, reason flagged. No detected text. Tell me how to turn on ‘Encrypt local backup’ in Finder and how to review Full Disk Access in System Settings.”

📱 AzCrypt — encrypt your private files behind biometrics. Your fingerprint is the key. ▶️ Watch the promo: 📲 Get it on Google Play: #PrivacyApp #Encryption #CyberSecurity

Protecting Australians online means strengthening security, not creating new vulnerabilities. CCIA is urging Australian lawmakers to safeguard strong #encryption and ensure online safety rules are clear, proportionate, and effective. Vague obligations and weakened encryption can undermine #privacy, expose users to cyber threats, and restrict access to lawful content. Safety policies should address real risks without creating new ones.

Stop taking corporations at their word. I launched Chryptor - a fully offline app for hardcore data encryption right on your device. The mechanics are simple: encrypt your sensitive text or files locally, then send that unreadable data block via any standard messenger, email, or cloud. No one but the recipient with the password can open it. 🛡️🔐

New Enigma discovery #encryption

We have great news: tomorrow (1 Nov 2026) Crypto Museum will be revealing an Enigma cipher machine that was developed after WWII (1957). It is a rotor/pin-wheel hybrid that was used by the German Foreign Office:

@InevitableChina To prove that my encryptions are real. I am releasing the key to one of the short ones. "GCTSDVTLEXUSCZTLHYON" I used the Playfair Cipher to encrypt it. I used a 5 × 5 grid. Here is the KEY to solve it. GSMTBKWELVOYZXNHDICRFQUAP Place the letters in the GRID horizontally.

🔥 #WhatsApp has sued the Indian government over new Internet regulations that could force it to break #encryption for "traceability,' eventually putting the #privacy of billions of users at risk. Read: #infosec #cybersecurity #Whatsappban #technews

You can now hide a ChatGPT chat behind a 4-digit PIN. But if you ever reset that PIN, every locked chat is deleted. For good. 🔒 OpenAI started rolling out locked chats on Oct 20 for Free, Go, Plus and Pro users. Try it: 1. Open a chat and tap ••• 2. Tap Lock chat 3. Create a 4-digit PIN (Face ID, Touch ID or device unlock also work on supported phones) Find them later under Projects > Locked chats. The fine print, from OpenAI's own help page: • Resetting your PIN deletes every locked chat. Support can't get them back • It's not end-to-end encryption • It hides the chat. It doesn't erase what ChatGPT already remembered Changing your PIN is safe, it keeps your chats: Settings > Security and login > Account PIN. How would you unlock yours: A) Face ID or B) the 4-digit PIN?