#argon2id — Public Fediverse posts

Три архитектурных решения для multi-tenant B2B SaaS, о которых я пожалел, что не узнал раньше

Самая дорогая ошибка моего B2B SaaS имела ровно одну строчку Самая дорогая ошибка моего B2B SaaS имела ровно одну строчку: TENANT_ID = “tenant-1” в config.py . Полтора дня поиска бага показали, почему multi-tenant архитектуру нужно закладывать с первого коммита. Разбор трёх архитектурных решений для multi-tenant SaaS в регулируемой отрасли — tenant_id helper, PostgreSQL EXCLUDE USING gist против double-booking, 152-ФЗ как код на FastAPI и SQLAlchemy.

https://habr.com/ru/articles/1033488/

#multitenant #fastapi #postgresql #sqlalchemy #exclude_using_gist #argon2id #pbkdf2 #152фз #audit_log #b2b_saas

Три архитектурных решения для multi-tenant B2B SaaS, о которых я пожалел, что не узнал раньше

Самая дорогая ошибка моего B2B SaaS имела ровно одну строчку Самая дорогая ошибка моего B2B SaaS имела ровно одну строчку: TENANT_ID = “tenant-1” в config.py . Полтора дня поиска бага показали, почему multi-tenant архитектуру нужно закладывать с первого коммита. Разбор трёх архитектурных решений для multi-tenant SaaS в регулируемой отрасли — tenant_id helper, PostgreSQL EXCLUDE USING gist против double-booking, 152-ФЗ как код на FastAPI и SQLAlchemy.

https://habr.com/ru/articles/1033488/

#multitenant #fastapi #postgresql #sqlalchemy #exclude_using_gist #argon2id #pbkdf2 #152фз #audit_log #b2b_saas

Три архитектурных решения для multi-tenant B2B SaaS, о которых я пожалел, что не узнал раньше

Самая дорогая ошибка моего B2B SaaS имела ровно одну строчку Самая дорогая ошибка моего B2B SaaS имела ровно одну строчку: TENANT_ID = “tenant-1” в config.py . Полтора дня поиска бага показали, почему multi-tenant архитектуру нужно закладывать с первого коммита. Разбор трёх архитектурных решений для multi-tenant SaaS в регулируемой отрасли — tenant_id helper, PostgreSQL EXCLUDE USING gist против double-booking, 152-ФЗ как код на FastAPI и SQLAlchemy.

https://habr.com/ru/articles/1033488/

#multitenant #fastapi #postgresql #sqlalchemy #exclude_using_gist #argon2id #pbkdf2 #152фз #audit_log #b2b_saas

Три архитектурных решения для multi-tenant B2B SaaS, о которых я пожалел, что не узнал раньше

Самая дорогая ошибка моего B2B SaaS имела ровно одну строчку Самая дорогая ошибка моего B2B SaaS имела ровно одну строчку: TENANT_ID = “tenant-1” в config.py . Полтора дня поиска бага показали, почему multi-tenant архитектуру нужно закладывать с первого коммита. Разбор трёх архитектурных решений для multi-tenant SaaS в регулируемой отрасли — tenant_id helper, PostgreSQL EXCLUDE USING gist против double-booking, 152-ФЗ как код на FastAPI и SQLAlchemy.

https://habr.com/ru/articles/1033488/

#multitenant #fastapi #postgresql #sqlalchemy #exclude_using_gist #argon2id #pbkdf2 #152фз #audit_log #b2b_saas

Microsoft gerät in die Datenschutzkritik: Der Konzern soll BitLocker-Schlüssel an das FBI weitergegeben haben – mit Folgen für das Vertrauen in Cloud-Sicherheit 🔐🇺🇸 Mehr dazu: https://www.golem.de/news/datenschutzdebatte-microsoft-gibt-bitlocker-schluessel-an-fbi-weiter-2601-204576.html #Microsoft #BitLocker #Datenschutz #FBI #Newz

Die coolen Kidz nutzen #Linux mit #LUKS2 & #Argon2id

Es gibt auch #Veracrypt statt Bitlocker

https://www.drensec.com/kostenlose-festplattenverschluesselung-fuer-windows-11-mit-veracrypt/

Argh, sucks. #Picocrypt is (was) a nice little tool for encrypting files and folders in Go with #XChaCha20 and #Argon2id. Thanks for the hard work.

> I originally intended to work in the software engineering industry, but seeing the complete disregard for high quality code, overpowering greed and hype, and the layoffs that follow from it, I am shifting into academic research instead. [1]

**I'm archiving Picocrypt** [2]

[1]: https://github.com/Picocrypt/Picocrypt/issues/134
[2]: https://discuss.privacyguides.net/t/im-archiving-picocrypt/29785

#Encryption

Argh, sucks. #Picocrypt is (was) a nice little tool for encrypting files and folders in Go with #XChaCha20 and #Argon2id. Thanks for the hard work.

> I originally intended to work in the software engineering industry, but seeing the complete disregard for high quality code, overpowering greed and hype, and the layoffs that follow from it, I am shifting into academic research instead. [1]

**I'm archiving Picocrypt** [2]

[1]: https://github.com/Picocrypt/Picocrypt/issues/134
[2]: https://discuss.privacyguides.net/t/im-archiving-picocrypt/29785

#Encryption

Argh, sucks. #Picocrypt is (was) a nice little tool for encrypting files and folders in Go with #XChaCha20 and #Argon2id. Thanks for the hard work.

> I originally intended to work in the software engineering industry, but seeing the complete disregard for high quality code, overpowering greed and hype, and the layoffs that follow from it, I am shifting into academic research instead. [1]

**I'm archiving Picocrypt** [2]

[1]: https://github.com/Picocrypt/Picocrypt/issues/134
[2]: https://discuss.privacyguides.net/t/im-archiving-picocrypt/29785

#Encryption

Argh, sucks. #Picocrypt is (was) a nice little tool for encrypting files and folders in Go with #XChaCha20 and #Argon2id. Thanks for the hard work.

> I originally intended to work in the software engineering industry, but seeing the complete disregard for high quality code, overpowering greed and hype, and the layoffs that follow from it, I am shifting into academic research instead. [1]

**I'm archiving Picocrypt** [2]

[1]: https://github.com/Picocrypt/Picocrypt/issues/134
[2]: https://discuss.privacyguides.net/t/im-archiving-picocrypt/29785

#Encryption

Argh, sucks. #Picocrypt is (was) a nice little tool for encrypting files and folders in Go with #XChaCha20 and #Argon2id. Thanks for the hard work.

> I originally intended to work in the software engineering industry, but seeing the complete disregard for high quality code, overpowering greed and hype, and the layoffs that follow from it, I am shifting into academic research instead. [1]

**I'm archiving Picocrypt** [2]

[1]: https://github.com/Picocrypt/Picocrypt/issues/134
[2]: https://discuss.privacyguides.net/t/im-archiving-picocrypt/29785

#Encryption

#Veracrypt 1.26.26 (dev) has been released (#TrueCrypt / #CipherShed / #DiskCryptor / #OTFE / #Crypto / #Encryption / #DiskEncryption / #Argon2 / #Argon2id / #GOSTBlockCipher / #RFC7801 / #RFC8891 / #BLAKE2s256 / #Streebog / #AES / #Camellia / #Kuznyechik / #Twofish / #IDRIX / #AMCrypto) https://veracrypt.io/

#Veracrypt 1.26.26 (dev) has been released (#TrueCrypt / #CipherShed / #DiskCryptor / #OTFE / #Crypto / #Encryption / #DiskEncryption / #Argon2 / #Argon2id / #GOSTBlockCipher / #RFC7801 / #RFC8891 / #BLAKE2s256 / #Streebog / #AES / #Camellia / #Kuznyechik / #Twofish / #IDRIX / #AMCrypto) https://veracrypt.io/

#Veracrypt 1.26.26 (dev) has been released (#TrueCrypt / #CipherShed / #DiskCryptor / #OTFE / #Crypto / #Encryption / #DiskEncryption / #Argon2 / #Argon2id / #GOSTBlockCipher / #RFC7801 / #RFC8891 / #BLAKE2s256 / #Streebog / #AES / #Camellia / #Kuznyechik / #Twofish / #IDRIX / #AMCrypto) https://veracrypt.io/

70000 | argon2id [Bridged: reference implementation + tunings] | Raw Hash

#argon2id #hashcat

#Veracrypt 1.26.25 has been released (#TrueCrypt / #CipherShed / #DiskCryptor / #OTFE / #Crypto / #Encryption / #DiskEncryption / #Argon2 / #Argon2id / #GOSTBlockCipher / #RFC7801 / #RFC8891 / #BLAKE2s256 / #Streebog / #AES / #Camellia / #Kuznyechik / #Twofish / #IDRIX / #AMCrypto) https://veracrypt.io/

#Veracrypt 1.26.25 has been released (#TrueCrypt / #CipherShed / #DiskCryptor / #OTFE / #Crypto / #Encryption / #DiskEncryption / #Argon2 / #Argon2id / #GOSTBlockCipher / #RFC7801 / #RFC8891 / #BLAKE2s256 / #Streebog / #AES / #Camellia / #Kuznyechik / #Twofish / #IDRIX / #AMCrypto) https://veracrypt.io/

#Veracrypt 1.26.25 has been released (#TrueCrypt / #CipherShed / #DiskCryptor / #OTFE / #Crypto / #Encryption / #DiskEncryption / #Argon2 / #Argon2id / #GOSTBlockCipher / #RFC7801 / #RFC8891 / #BLAKE2s256 / #Streebog / #AES / #Camellia / #Kuznyechik / #Twofish / #IDRIX / #AMCrypto) https://veracrypt.io/

New version of #hashgen published.

Changelog:
v1.1.0; 2025-03-19
added modes: #base58, #argon2id, #bcrypt w/custom cost factor

https://forum.hashpwn.net/post/89

#hashgenerator #hashcracking #hashcat #hashpwn #cyclone #golang

New version of #hashgen published.

Changelog:
v1.1.0; 2025-03-19
added modes: #base58, #argon2id, #bcrypt w/custom cost factor

https://forum.hashpwn.net/post/89

#hashgenerator #hashcracking #hashcat #hashpwn #cyclone #golang

New version of #hashgen published.

Changelog:
v1.1.0; 2025-03-19
added modes: #base58, #argon2id, #bcrypt w/custom cost factor

https://forum.hashpwn.net/post/89

#hashgenerator #hashcracking #hashcat #hashpwn #cyclone #golang

New version of #hashgen published.

Changelog:
v1.1.0; 2025-03-19
added modes: #base58, #argon2id, #bcrypt w/custom cost factor

https://forum.hashpwn.net/post/89

#hashgenerator #hashcracking #hashcat #hashpwn #cyclone #golang

New version of #hashgen published.

Changelog:
v1.1.0; 2025-03-19
added modes: #base58, #argon2id, #bcrypt w/custom cost factor

https://forum.hashpwn.net/post/89

#hashgenerator #hashcracking #hashcat #hashpwn #cyclone #golang

#Picocrypt is a very small (hence Pico), very simple, yet very #secure #encryption tool that you can use to protect your #files. It's designed to be the go-to tool for encryption, with a focus on security, simplicity, and reliability. Picocrypt uses the secure #XChaCha20 cipher and the #Argon2id key derivation function to provide a high level of security, even from three-letter agencies like the NSA. Your privacy and security is under attack. Take it back with confidence by protecting your files with Picocrypt.
https://github.com/HACKERALERT/Picocrypt?tab=readme-ov-file

#Picocrypt is a very small (hence Pico), very simple, yet very #secure #encryption tool that you can use to protect your #files. It's designed to be the go-to tool for encryption, with a focus on security, simplicity, and reliability. Picocrypt uses the secure #XChaCha20 cipher and the #Argon2id key derivation function to provide a high level of security, even from three-letter agencies like the NSA. Your privacy and security is under attack. Take it back with confidence by protecting your files with Picocrypt.
https://github.com/HACKERALERT/Picocrypt?tab=readme-ov-file

Tails - Weak cryptographic parameters in LUKS1 https://tails.boum.org/security/argon2id/index.en.html #cryptsetup #parameter #dm-crypt #argon2id #weakness #crypto #pbkdf2 #tails #luks #kdf

@mjg59

Thank you for sounding the alert!

I identified a minor issue with your otherwise nice explanation: According to my sources (man cryptsetup, #rfc9106), all #argon2 varieties are memory-hard. RFC 9106 is even titled “Argon2 Memory-Hard Function for Password Hashing and Proof-of-Work Applications”.

However, given that there are known attacks against #argon2i, it seems wise to use #argon2id instead. It is also what is recommended in the RFC.

As a #QubesOS user, I just checked the state of affairs there:

The cryptsetup that comes with QubesOS 3.x used #luks1, and those who did an in-place upgrade to 4.x still have that unless they converted to #luks2 manually (as detailed in the migration guide).

The cryptsetup in QubesOS 4.x uses #luks2, but it still defaults to #argon2i unfortunately.

KeePassXC 2.6.3 Password Manager Adds Support for Argon2id KDF and XMLv2 Key Files

https://9to5linux.com/keepassxc-2-6-3-password-manager-adds-support-for-argon2id-kdf-and-xmlv2-key-files

#KeePassXC #passwordmanager #Argon2id