#gnupg — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #gnupg, aggregated by home.social.
-
Как шифровать сообщения в любом мессенджере и соцсети
В нынешних условиях многим пользователям приходится по принуждению использовать незащищённые мессенджеры и социальные сети, то есть скомпрометированные каналы связи. К счастью, есть возможность передавать секретные зашифрованные сообщения по публичным открытым каналам. Это стандартная задача, которая давно решена в криптографии. Более того, зашифрованное сообщение можно сделать похожим на обычный текст или даже скрыть в обычном контенте — видео, звуковых файлах и тексте, который не вызовет подозрений у «цензора». Это область стеганографии Но прямо сейчас людям нужен простой и практичный способ шифровать сообщения, максимально удобным способом. Рассмотрим самые простые онлайновые утилиты, которые позволяют это делать.
https://habr.com/ru/companies/globalsign/articles/1030886/
#шифрование #Paranoia_Text_Encryption #LOCKPUB #GCHQ_CyberChef #AES_Utils #GnuPG #OpenSSL #ccrypt #VeraCrypt #Cryptomator
-
No to poprawcie mnie, jeżeli się mylę, co do aktualnego stanu #OpenPGP.
Po pierwsze, jest dawne #RFC4880bis, aktualnie przepychane jako "#LibrePGP", używane przez #GnuPG (i #rnp?), z formatem kluczy "v5" — i zdaje się, że każdy inny projekt spogląda na to z politowaniem.
Po drugie, jest #RFC9580 z formatem kluczy "v6", używany przez #OpenPGPjs, #SequoiaPGP (i inne narzędzia), ale odrzucony przez GnuPG. I wygląda na to, że jest przepychane z założeniem, że GnuPG ugnie się pod presją.
Więc mamy dwa niezgodne ze sobą standardy, ze "wspólnym mianownikiem" w postaci zabytkowego #RFC4880; jedne narzędzia przepychają jeden standard i ignorują drugi, a inne decydują się wspierać oba, by pomóc swoim użytkownikom. A #Gentoo ostatecznie utknie z tym, co wspierać będzie GnuPG, bo potrzebujemy kryptografii, która działa na wszystkich wspieranych platformach, a nie tylko tam, gdzie Rust.
-
Okay, so please correct me if I'm wrong about the state of #OpenPGP right now.
So first there's the former #RFC4880bis which is now pursued as "#LibrePGP", used by #GnuPG (and #rnp?), with a "v5" key format, that everyone else seem to looks "politely" at.
Then there's #RFC9580 with a "v6" key format, used by #OpenPGPjs, #SequoiaPGP (and more) but explicitly rejected by GnuPG. However, it seems to be pushed forward under the assumption that GnuPG will yield to pressure.
So we effectively have two incompatible standards, with a "common denominator" of ancient #RFC4880, some tools pursuing one of them with disregard for the other, and a few supporting both for the sake of the users. And #Gentoo is effectively stuck with whatever GnuPG supports, because we need working crypto on all supported platforms, not just the "Rust subset".
-
It's been a while since I've last used #crypto (and by that I don't mean coins but oldschool #cryptography : encrypting and signing mails, etc.), and lately I've only used #gpg to encrypt my #pass vault.
However, I wanted to up my game a little, so here it comes: For the first time I got myself a hardware token. I opted for #yubikey even though #nitrokey is probably the better option, because of #opensource. But I wanted my first steps to be smooth ones, and also try out all the different operational scenarios; and all research said that Yubikey is the better supported and the more versatile option (maybe I'll switch to a #nitrokey later on).
I went a bit overboard with the setup as well. I got myself some new USB drives, one flashed with #tails - a portable live #linux system by the @torproject developers, to boot with it a machine #offthegrid on which I'd create my keys. A #gnupg main key just for certification, and three subkeys for signing, encryption and authentication. The main key was moved to two backup USB drives, the subkeys on two Yubikeys (which as a bit of a hassle as usually you are only allowed to move them to one).
While the private main key will never see the light of day (i.e. just stay on the thumbdrives or be imported by the off-grid tails system), the subkeys will live on my tokens (which are not extractable as well).
They expire every year so I'd need to renew them (with the main key on tails), my identities are tied to the main key, and if any key is compromized I can easily create new ones with that main key.
To me that seems pretty sound, and a lot of overkill, tbh :D But it was also quite fun.
Next up: Switching my environment to use Yubikey and my new GPG keys instead of #ssh etc. And after that I'll give #2FA a try. And if I am not on the PC I'll guess I'll read some more about #EllipticCurveCryptography. First time I am using those algorithms. So long, #RSA, you've been a great companion, and hello #ed25519, nice to meet you.
