#aes-256 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #aes-256, aggregated by home.social.
-
NFC.cool can encrypt secrets on NFC tags 🔐 #nfc #nfccool #nfcbusinesscard #nfctags #nfctools #encryption #aes256
-
NFC.cool can encrypt secrets on NFC tags 🔐 #nfc #nfccool #nfcbusinesscard #nfctags #nfctools #encryption #aes256
-
Как я сделал шифрование поверх MAX, когда приватность стала роскошью
Как я без Mac, с помощью Claude AI и GitHub Actions, создал кроссплатформенное приложение для шифрования сообщений поверх любого мессенджера. Android на Kotlin, iOS на Swift без MacBook, десктоп на Python. AES-256, три платформы, два отказа от Apple и один баг с буквой «а».
https://habr.com/ru/articles/1013960/
#шифрование #AES256 #приватность #мессенджер #криптография #android #ios #AI #GitHub_Actions #безопасность
-
A Copy-Paste Bug That Broke PSpice AES-256 Encryption
https://jtsylve.blog/post/2026/03/18/PSpice-Encryption-Weakness
#HackerNews #CopyPasteBug #PSpice #AES256 #EncryptionWeakness #Cybersecurity #SoftwareFlaw #TechNews
-
A Copy-Paste Bug That Broke PSpice AES-256 Encryption
https://jtsylve.blog/post/2026/03/18/PSpice-Encryption-Weakness
#HackerNews #CopyPasteBug #PSpice #AES256 #EncryptionWeakness #Cybersecurity #SoftwareFlaw #TechNews
-
PrivateBin
Current version: 2.0.3
Anyone on the FediVerse running PrivateBin on their own (small) network?
- PrivateBin
- minimalist
- Open Source
- online pastebin
- server has zero knowledge of stored data
Data is encrypted & decrypted in your browser with 256bit AES in Galois Counter mode.
- PrivateBin is a fork of ZeroBin originally developed by Sébastien Sauvage
- PrivateBin was refactored to allow easier & cleaner extensions
- it has many additional features.
#encryption #programming #PrivateBin #Zero #Knowledge #plausable #deniability #networking #AES256 #Galois #Counter #technology
-
PrivateBin
Current version: 2.0.3
Anyone on the FediVerse running PrivateBin on their own (small) network?
- PrivateBin
- minimalist
- Open Source
- online pastebin
- server has zero knowledge of stored data
Data is encrypted & decrypted in your browser with 256bit AES in Galois Counter mode.
- PrivateBin is a fork of ZeroBin originally developed by Sébastien Sauvage
- PrivateBin was refactored to allow easier & cleaner extensions
- it has many additional features.
#encryption #programming #PrivateBin #Zero #Knowledge #plausable #deniability #networking #AES256 #Galois #Counter #technology
-
RLM-Toolkit v1.2.1: Теоретические основы и оригинальные разработки
От теоремы Шеннона 1948 года до pip install rlm-toolkit 2026 года. 78 лет фундаментальной науки в одной библиотеке.
https://habr.com/ru/articles/986702/
#RLM #LLM #RAG #криптография #AES256 #Information_Bottleneck #сжатие_контекста #MCP #AI_Security #SENTINEL
-
Renesas Releases Dual-Band Wi-Fi 6 and Bluetooth LE MCUs on Cortex-M33 Architecture
-
🔐 Windows 11 BitLocker 自動加密風險完全解析 🔐
前言:一個讓我們印象深刻的救援案例 😢
作為新竹地區資料救援專家,我們最近遇到一位客戶,重新安裝 Windows 11 後,D 槽和 E 槽突然無法存取,系統要求輸入「BitLocker 復原金鑰」。
問題是,他完全不知道什麼是 BitLocker,也沒有備份金鑰。
檢測發現,這兩個磁碟機共儲存近 3TB 資料,包括多年工作檔案、家庭照片和重要文件 💾
由於 BitLocker 採用軍規 AES-256 加密,沒有復原金鑰,資料幾乎無法救回 ⚠️
這並非個案。隨著 Windows 11 預設啟用 BitLocker,越來越多用戶在不知情的情況下加密磁碟,直到系統重灌或更換硬體才發現問題 😱
本文深入探討:
BitLocker 技術細節 🔧
潛在風險 ⚠️
專業金鑰管理建議 🗝️
詳細文章連結:
https://2025.data-recover.com.tw/news/Windows11%E9%BB%98%E8%AA%8D%E5%95%9F%E7%94%A8BitLocker%E5%B0%8E%E8%87%B4%E8%B3%87%E6%96%99%E8%A2%AB%E9%8E%96%E6%AD%BB-SSD%E6%80%A7%E8%83%BD%E5%BD%B1%E9%9F%BF%E8%88%87%E9%87%91%E9%91%B0%E5%82%99%E4%BB%BD%E5%AE%8C%E5%85%A8%E6%8C%87%E5%8D%97
#Windows11 #BitLocker #DataRecovery #Encryption #TechNews #セキュリティ #データ復旧 #クラウド #科技 #資料救援 #硬碟 #AES256 #IT #Tech #StorageTips #SecurityTips #news #Storagenews -
tnyr.me : un raccourcisseur d’URL axé sur la confidentialité, un raccourcisseur, oui… mais chiffré de bout en bout.
Contrairement aux services classiques, tnyr.me ne se contente pas de masquer l’URL d’origine derrière un lien plus court. Il chiffre entièrement cette URL grâce à un algorithme AES-256, avec une clé unique générée à partir de l’identifiant du lien. Ainsi, même les créateurs du service ne peuvent pas accéder à vos liens. Ils ne sont ni stockés en clair, ni lisibles, ni exploitables.
Aucune trace, aucun cookie, aucune collecte
Outre le chiffrement, tnyr.me pousse la confidentialité encore plus loin en ne stockant… rien d’autre. Le service ne garde ni adresses IP, ni journaux d’activité, ni cookies. Aucune analytics, aucun suivi, aucun pistage d’aucune sorte. Chaque visite est considérée comme totalement anonyme, sans empreinte numérique laissée derrière.
Je teste ici :
https://tnyr.me/#LmR4SKr92* -
🔐 AstraCrypt – Open-source file encryption for Android
✅ AES-256 (GCM) encryption
✅ Manage files securely
✅ No trackers, no ads
✅ Clean Material You designKeep your data safe with a modern, privacy-respecting tool.
📥 Download:
https://apt.izzysoft.de/fdroid/index/apk/com.nevidimka655.astracrypt#FOSS #Android #Encryption #Privacy #AES256 #astracrypt #OpenSource #Security
-
🔐 AstraCrypt – Open-source file encryption for Android
✅ AES-256 (GCM) encryption
✅ Manage files securely
✅ No trackers, no ads
✅ Clean Material You designKeep your data safe with a modern, privacy-respecting tool.
📥 Download:
https://apt.izzysoft.de/fdroid/index/apk/com.nevidimka655.astracrypt#FOSS #Android #Encryption #Privacy #AES256 #astracrypt #OpenSource #Security
-
Взлом зашифрованного pdf-файла. Часть 2
Всех приветствую, читатели Хабра! Вторая часть исследования безопаности файлов pdf. После того, как я опубликовал первую часть ( https://habr.com/ru/articles/906076/ ) у одного из моих коллег возник вопрос: а что если зашифровать pdf файл при помощи программы Adobe (естественно на Windows). Естественно что, меня заинтересовал этот вопрос, и мы решили совместно с моим коллегой зашифровать файлы в ОС Windows (10) при помощи Adobe и на сайте, указанном в первой части. Один из файлов был зашифрован в Windows но на сайте указанном в первой части статьи. Сделал я это специально для того, чтобы узнать не будет ли проблем совместимости на двух ОС - Windows и Linux, и возможно ли кракнуть такой файл, который был создан в другой системе, так сказать тестовый запуск. Другие файлы были зашифрованы в программе, опять же на ОС Windows. Почему мой коллега и я задались вопросом возможности крака? В Adobe возможно зашифровать pdf файл при помощи небезызвестного AES! Примечание Правовая информация: Данная статья создана исключительно в ознакомительных/образовательных/развивающих целях. Автор статьи не несет ответственности за ваши действия. Автор статьи ни к чему не призывает, более того напоминаю о существовании некоторых статей в уголовном кодексе РФ, их никто не отменял: УК РФ Статья 272. Неправомерный доступ к компьютерной информации УК РФ Статья 273. Создание, использование и распространение вредоносных компьютерных программ УК РФ Статья 274. Нарушение правил эксплуатации средств хранения, обработки или передачи компьютерной информации и информационно-телекоммуникационных сетей
https://habr.com/ru/articles/907726/
#pdf #hacking #cracking #хакинг #aes #aes256 #aes128 #информационная_безопасность #операционные_системы #софт
-
Парольная защита статичной HTML-страницы на JS
Обычно парольная защита производится через веб-сервер, который проверяет пароль и выдаёт контент. Стандартный способ: .htaccess и htpasswd . Но что, если нужно выложить зашифрованную веб-страницу и файлы на публичном хостинге, где у нас нет контроля над сервером? Эту проблему решают инструменты StatiCrypt и Portable Secret . Для шифрования HTML перед публикацией StatiCrypt использует AES-256 и WebCrypto, а расшифровка происходит с помощью ввода пароля в браузере на стороне клиента, как показано в демо (пароль test ). StatiCrypt генерирует статическую страницу, которую можно безопасно заливать на любой хостинг, в том числе бесплатный сторонний хостинг, такой как GitHub Pages.
https://habr.com/ru/companies/globalsign/articles/868780/
#StatiCrypt #AES256 #WebCrypto #парольная_защита #PBKDF2 #Portable_Secret #шифрование_файлов
-
Развенчан слух, что Китай взломал современную криптографию с помощью квантового компьютера
В октябре 2024 года мировые СМИ стали распространять пугающие новости о том, что китайским учёным якобы удалось взломать современные криптографические шифры военного применения с помощью квантового компьютера D-Wave Advantage (на фото вверху). Эти новости основаны не на пустых словах, а на научной статье от группы исследователей под руководством д-ра Ван Чао (Wang Chao) из Шанхайского университета. Статья опубликована в сентябре 2024 года в журнале Chinese Journal of Computers . Авторы использовали D-Wave Advantage для успешной атаки на три алгоритма — Present, Gift-64 и Rectangle, которые являются критически важными для расширенного стандарта шифрования (AES), используемого для защиты данных в правительственном, военном и финансовом секторах. Западные эксперты по криптографии изучили статью и оценили достижения китайских коллег.
https://habr.com/ru/companies/globalsign/articles/859218/
#квантовый_компьютер #Present #Gift64 #Rectangle #военная_криптография #гражданская_криптография #DWave_Advantage #AES #AES256 #квантовая_нормализация #квантовый_отжиг
-
Interesting development of ransomware, however I find the title misleading as AES-256 isn't really "stronger" than ChaCha20: https://www.bleepingcomputer.com/news/security/new-qilin-ransomware-encryptor-features-stronger-encryption-evasion/
-
中國上海大學科學家聲稱:已用量子電腦突破軍用級加密! - INSIDE
Link
📌 Summary:
中國上海大學的科學家宣佈,成功利用量子電腦破解了多種加密演算法,包括被認為是軍用級的AES-256,這預示著量子電腦對資訊安全的重大威脅。研究團隊使用的D-Wave Advantage量子電腦採用「量子退火」演算法,能更有效率地解決複雜的組合優化問題。儘管目前研究仍處於初期階段且量子計算存在技術限制,這一成果為量子計算的未來發展鋪平了道路,促使各國積極研發量子安全加密技術以應對未來的安全挑戰。
🎯 Key Points:
- 上海大學研究團隊成功破解軍用級加密演算法,包括AES-256。
- 使用D-Wave Advantage量子電腦,利用「量子退火」技術來進行攻擊。
- 量子退火能以量子隧道效應和疊加性來解決組合問題,增強運算效率。
- 研究仍處於初期階段,未來面臨技術挑戰,但此次突破為量子計算奠定基礎。
- 各國目前積極研究量子安全加密技術,如NIST已著手發展抗量子攻擊的加密方案。
🔖 Keywords:
#量子電腦 #加密演算法 #AES-256 #量子安全 #量子退火 -
📬 SAV7: Einzelne Dateien oder Ordner kostenlos verschlüsseln
#Datenschutz #Empfehlungen #ITSicherheit #AES256 #KeyFile #Passwort #SAV7 #Verschlüsselung https://sc.tarnkappe.info/f8d9d7 -
📬 SAV7: Einzelne Dateien oder Ordner kostenlos verschlüsseln
#Datenschutz #Empfehlungen #ITSicherheit #AES256 #KeyFile #Passwort #SAV7 #Verschlüsselung https://sc.tarnkappe.info/f8d9d7 -
How safe is it to store my private gpg key in the open? It requires a passphrase, and
I thought about adding an additional passphrase for the file stored in publicgpg --armor --export-secret-keys MY-KEY-ID | gpg --symmetric --cipher-algo AES256 --output MY-PRIVATE-KEY
AES256 should be safe with a strong passphrase, right?
Is this Safe Enough, or is this insanity?
-
How safe is it to store my private gpg key in the open? It requires a passphrase, and
I thought about adding an additional passphrase for the file stored in publicgpg --armor --export-secret-keys MY-KEY-ID | gpg --symmetric --cipher-algo AES256 --output MY-PRIVATE-KEY
AES256 should be safe with a strong passphrase, right?
Is this Safe Enough, or is this insanity?
-
We recently reached 256 posts on Mastodon, so it's time to talk about AES-256! But what exactly is it and why use it?
Extremely secure: Practically unbreakable
Future-proof: Better protection against advances in computing power
Familiar and proven: Government and military standard
Protect your sensitive data now! 💪✨#Security #Encryption #AES256 #Data protection #CyberSecurity #Tech #Cryptomator #DataProtection #ITSecurity #SecureConnections #FutureProof #DigitalLife
-
We recently reached 256 posts on Mastodon, so it's time to talk about AES-256! But what exactly is it and why use it?
Extremely secure: Practically unbreakable
Future-proof: Better protection against advances in computing power
Familiar and proven: Government and military standard
Protect your sensitive data now! 💪✨#Security #Encryption #AES256 #Data protection #CyberSecurity #Tech #Cryptomator #DataProtection #ITSecurity #SecureConnections #FutureProof #DigitalLife
-
Кому #AES256 в рациях за 3 т.р.?
Честный, полноценный #AES в том же Baofeng DR1909, которых много в продаже стало.
Качество изготовления, ну там распайка элементов на плате, отсутствие водозащиты и т.п. — хероватые, фактически одноразовое всё. Однако, параметры технические у рации не просто неплохие, а вполне достойные, для аппарата «на чипе». Прямо даже не стыдно называть моделью, а используется в ней чип #Auctus A6.
AES256 работает с другими рациями, других вендоров, проверено.
Про общие педостатки рация «на чипе» для городской среды было тут. Как именно дела именно у этого чипа — не в курсе, надо собирать отзывы. Качество работы у RDA и того же BK незначительно, но отличались. Возможно, этот самый Auctus будет показывать себя так же или лучше или хуже — неизвестно.
P.S. закупать ли на «первую линию», ну вместо аналога на «чипах»? Много чего заливать-герметизировать придётся, чтобы обеспечить влагозащиту, да и пайку на платах от флюса отмыть бы.
#связь #baofeng #радио #радиосвязь #AuctusA6 #lang_ru @Russia @RUssian Reposter -
🎊 We are starting #2024 off right! 🎉
With the latest update all Tuta accounts are now utilizing #Argon2 and #AES256 encryption by default.🔒💪
This security improvement is the next step towards full #postquantum encryption!
👉 https://tuta.com/blog/aes-256-encryption -
🎊 We are starting #2024 off right! 🎉
With the latest update all Tuta accounts are now utilizing #Argon2 and #AES256 encryption by default.🔒💪
This security improvement is the next step towards full #postquantum encryption!
👉 https://tuta.com/blog/aes-256-encryption -
Das überrascht mich - iOS kann inzwischen AES256 direkt "entzippen"?
Könnt Ihr das bestätigen?
1. Datei mit 7zip verschlüsselt (AES256-Modus).
2. Datei auf Nextcloud geladen.
3. Nextcloud-Pfad in iOS-Dateien-App geöffnet.
4. Passwort wird abgefragt und entschlüsselt.
Früher musste ich da den Umweg über Filebrowser oder andere Tools nehmen. -
@marcan @lanodan the only cases where one would need even more Power are setups like High-Bandwith #VPN Gateways like some huge #pfSense if one needs 40+ GBit/s throughput on #OpenVPN or #WireGuard.
Mind you that #LUKS - aside from the encryption of the key in the header, uses #AES256 by default for a long time and is pretty efficient even prior to #AESni.
So no, in most cases the impact is purely synthetic and not really of any impact...
-
Many of you have been asking for my thoughts on the #LastPass breach, and I apologize that I'm a couple days late delivering.
Apart from all of the other commentary out there, here's what you need to know from a #password cracker's perspective!
Your vault is encrypted with #AES256 using a key that is derived from your master password, which is hashed using a minimum of 100,100 rounds of PBKDF2-HMAC-SHA256 (can be configured to use more rounds, but most people don't). #PBKDF2 is the minimum acceptable standard in key derivation functions (KDFs); it is compute-hard only and fits entirely within registers, so it is highly amenable to acceleration. However, it is the only #KDF that is FIPS/NIST approved, so it's the best (or only) KDF available to many applications. So while there are LOTS of things wrong with LastPass, key derivation isn't necessarily one of them.
Using #Hashcat with the top-of-the-line RTX 4090, you can crack PBKDF2-HMAC-SHA256 with 100,100 rounds at about 88 KH/s. At this speed an attacker could test ~7.6 billion passwords per day, which may sound like a lot, but it really isn't. By comparison, the same GPU can test Windows NT hashes at a rate of 288.5 GH/s, or ~25 quadrillion passwords per day. So while LastPass's hashing is nearly two orders of magnitude faster than the < 10 KH/s that I recommend, it's still more than 3 million times slower than cracking Windows/Active Directory passwords. In practice, it would take you about 3.25 hours to run through rockyou.txt + best64.rule, and a little under two months to exhaust rockyou.txt + rockyou-30000.rule.
Keep in mind these are the speeds for cracking a single vault; for an attacker to achieve this speed, they would have to single out your vault and dedicate their resources to cracking only your vault. If they're trying 1,000 vaults simultaneously, the speed would drop to just 88 H/s. With 1 million vaults, the speed drops to an abysmal 0.088 H/s, or 11.4 seconds to test just one password. Practically speaking, what this means is the attackers will target four groups of users:
1. users for which they have previously-compromised passwords (password reuse, credential stuffing)
2. users with laughably weak master passwords (think top20k)
3. users they can phish
4. high value targets (celebs, .gov, .mil, fortune 100)If you are not in this list / you don't get phished, then it is highly unlikely your vault will be targeted. And due to the fairly expensive KDF, even passwords of moderate complexity should be safe.
I've seen several people recommend changing your master password as a mitigation for this breach. While changing your master password will help mitigate future breaches should you continue to use LastPass (you shouldn't), it does literally nothing to mitigate this current breach. The attacker has your vault, which was encrypted using a key derived from your master password. That's done, that's in the past. Changing your password will re-encrypt your vault with the new password, but of course it won't re-encrypt the copy of the vault the attacker has with your new password. That would be impossible unless you somehow had access to the attacker's copy of the vault, which if you do, please let me know?
A proper mitigation would be to migrate to #Bitwarden or #1Password, change the passwords for each of your accounts as you migrate over, and also review the MFA status of each of your accounts as well. The perfect way to spend your holiday vacation! Start the new year fresh with proper password hygiene.
For more password insights like this, give me a follow!
-
Many of you have been asking for my thoughts on the #LastPass breach, and I apologize that I'm a couple days late delivering.
Apart from all of the other commentary out there, here's what you need to know from a #password cracker's perspective!
Your vault is encrypted with #AES256 using a key that is derived from your master password, which is hashed using a minimum of 100,100 rounds of PBKDF2-HMAC-SHA256 (can be configured to use more rounds, but most people don't). #PBKDF2 is the minimum acceptable standard in key derivation functions (KDFs); it is compute-hard only and fits entirely within registers, so it is highly amenable to acceleration. However, it is the only #KDF that is FIPS/NIST approved, so it's the best (or only) KDF available to many applications. So while there are LOTS of things wrong with LastPass, key derivation isn't necessarily one of them.
Using #Hashcat with the top-of-the-line RTX 4090, you can crack PBKDF2-HMAC-SHA256 with 100,100 rounds at about 88 KH/s. At this speed an attacker could test ~7.6 billion passwords per day, which may sound like a lot, but it really isn't. By comparison, the same GPU can test Windows NT hashes at a rate of 288.5 GH/s, or ~25 quadrillion passwords per day. So while LastPass's hashing is nearly two orders of magnitude faster than the < 10 KH/s that I recommend, it's still more than 3 million times slower than cracking Windows/Active Directory passwords. In practice, it would take you about 3.25 hours to run through rockyou.txt + best64.rule, and a little under two months to exhaust rockyou.txt + rockyou-30000.rule.
Keep in mind these are the speeds for cracking a single vault; for an attacker to achieve this speed, they would have to single out your vault and dedicate their resources to cracking only your vault. If they're trying 1,000 vaults simultaneously, the speed would drop to just 88 H/s. With 1 million vaults, the speed drops to an abysmal 0.088 H/s, or 11.4 seconds to test just one password. Practically speaking, what this means is the attackers will target four groups of users:
1. users for which they have previously-compromised passwords (password reuse, credential stuffing)
2. users with laughably weak master passwords (think top20k)
3. users they can phish
4. high value targets (celebs, .gov, .mil, fortune 100)If you are not in this list / you don't get phished, then it is highly unlikely your vault will be targeted. And due to the fairly expensive KDF, even passwords of moderate complexity should be safe.
I've seen several people recommend changing your master password as a mitigation for this breach. While changing your master password will help mitigate future breaches should you continue to use LastPass (you shouldn't), it does literally nothing to mitigate this current breach. The attacker has your vault, which was encrypted using a key derived from your master password. That's done, that's in the past. Changing your password will re-encrypt your vault with the new password, but of course it won't re-encrypt the copy of the vault the attacker has with your new password. That would be impossible unless you somehow had access to the attacker's copy of the vault, which if you do, please let me know?
A proper mitigation would be to migrate to #Bitwarden or #1Password, change the passwords for each of your accounts as you migrate over, and also review the MFA status of each of your accounts as well. The perfect way to spend your holiday vacation! Start the new year fresh with proper password hygiene.
For more password insights like this, give me a follow!
-
Toplip - A Very Strong File Encryption And Decryption CLI Utility #Toplip #Encryption #Decryption #AES256 #Security #Opensource #Linux
https://www.ostechnix.com/toplip-strong-file-encryption-decryption-cli-utility/ -
Toplip - A Very Strong File Encryption And Decryption CLI Utility #Toplip #Encryption #Decryption #AES256 #Security #Opensource #Linux
https://www.ostechnix.com/toplip-strong-file-encryption-decryption-cli-utility/