Framapiaf

4 messages3 participants0 message aujourd’hui

daltux"The treta has been planted." @ :debian: Sid <pre>apt-listchanges: News --------------------- gnupg2 (2.4.7-4) experimental; urgency=medium The upstream GnuPG project now explicitly and deliberately diverges from the OpenPGP standard. Debian's own workflows rely heavily on OpenPGP, and we ship several different OpenPGP implementations, so interoperability via standardization is a priority for the project. While Debian still has significant dependencies on GnuPG, the version of GnuPG shipped in Debian will default to emitting only OpenPGP-compatible artifacts if at all possible. As of 2.4.7-4, the default is --compliance=openpgp, and we apply several patches to ensure that this mode is respected. If you observe GnuPG in Debian emitting a non-OpenPGP artifact in a scenario where a standard OpenPGP artifact is intended or expected, please open a critical bug report in the Debian BTS. If you want Debian's GnuPG to emit non-standardized artifacts, in line with upstream's deliberate divergence, you can explicitly pass --compliance=gnupg (or set the corresponding option in ~/.gnupg/gpg.conf). If you revert to compliance with upstream defaults, do not expect the material you produce to be interoperable with other OpenPGP implementations. -- Daniel Kahn Gillmor <dkg@fifthhorseman.net> Fri, 07 Feb 2025 23:35:29 -0500 </pre><a href="https://snac.daltux.net?t=debian" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Debian</a> <a href="https://snac.daltux.net?t=gnupg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GnuPG</a> <a href="https://snac.daltux.net?t=gpg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPG</a> <a href="https://snac.daltux.net?t=openpgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> <a href="https://snac.daltux.net?t=gnu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GNU</a>

Delta ChatSome of you may have heard of <a href="https://chaos.social/tags/simplex" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#simplex</a> which likes to elevate itself as "the first messenger without user-ids" ... a goal, similar to ours, of not letting the transport layer know about who talks. Only we are doing it in the email system, fully interoperable with tens of thousands of existing email servers and other <a href="https://chaos.social/tags/openpgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openpgp</a> endpoints. The email system is much more than SMTP/IMAP or even openpgp btw ... there is plenty of room for radical shifts and new takes. We are just starting :)

Delta Chat<a href="https://chaos.social/tags/openpgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openpgp</a> traditions and <a href="https://chaos.social/tags/signal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#signal</a> both bind a cleartext identifier, phone number or email address, to a cryptographic key. It opens up attack vectors as the servers/orgs controlling this binding can interfere.<a href="https://chaos.social/tags/deltachat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#deltachat</a> avoids such cleartext identity bindings by creating random <a href="https://chaos.social/tags/chatmail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chatmail</a> addresses, as transport only. The cryptographic key becomes the identifier and we want it hidden from the transport layer. Only people being in end-to-end encrypted chat need to identify each other, after all.

Karl Voit :emacs: :orgmode:If you need <a href="https://graz.social/tags/E2EE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#E2EE</a> via <a href="https://graz.social/tags/email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#email</a>, the only 2 valid standards are <a href="https://graz.social/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> and <a href="https://graz.social/tags/SMIME" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SMIME</a>. It's not that those are without issues but everything else is mediocre.Yes, you can switch to non-email-services as well such as <a href="https://graz.social/tags/Signal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Signal</a>. But that's a different island.<a href="https://graz.social/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a> <a href="https://graz.social/tags/encryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#encryption</a> <a href="https://graz.social/tags/mail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mail</a> <a href="https://graz.social/tags/GMail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GMail</a>

Debacle<a href="https://social.screamingatmyscreen.com/@fallenhitokiri" class="u-url mention">@fallenhitokiri</a> Most people seem to believe <a href="https://framapiaf.org/tags/email" class="mention hashtag" rel="tag">#email</a> were just a misspelling of gmail anyway 🤷<a href="https://framapiaf.org/tags/mu4e" class="mention hashtag" rel="tag">#mu4e</a> <a href="https://framapiaf.org/tags/OpenPGP" class="mention hashtag" rel="tag">#OpenPGP</a> <a href="https://framapiaf.org/tags/encryption" class="mention hashtag" rel="tag">#encryption</a> <a href="https://framapiaf.org/tags/e2ee" class="mention hashtag" rel="tag">#e2ee</a>

Ivan GJDelta Chat es demasiado buena 🔥 <a href="https://fediverse.tv/videos/watch/21b54e75-f8ae-4a61-919c-a7d264f67b57" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://fediverse.tv/videos/watch/21b54e75-f8ae-4a61-919c-a7d264f67b57</a>

Preston Maness ☭<a href="https://mastodon.ml/@Xeniax" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Xeniax</a> Totally nerdsniped :D I'd love to be a part of the study.I don't think that <a href="https://tenforward.social/tags/KeyServers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KeyServers</a> are dead. I think they evolved into Verifying Key Servers (VKS), like the one run by a few folks from the OpenPGP ecosystem at <a href="https://keys.openpgp.org/about" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://keys.openpgp.org/about</a> . More generally, I believe that <a href="https://tenforward.social/tags/PGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PGP</a> / <a href="https://tenforward.social/tags/GPG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPG</a> / <a href="https://tenforward.social/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> retains important use-cases where accountability is prioritized, as contrasted with ecosystems (like <a href="https://tenforward.social/tags/Matrix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Matrix</a>, <a href="https://tenforward.social/tags/SignalMessenger" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SignalMessenger</a>) where deniability (and Perfect Forward Secrecy generally) is prioritized. Further, PGP can still serve to bootstrap those other ecosystems by way of signature notations (see the <a href="https://tenforward.social/tags/KeyOxide" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KeyOxide</a> project).Ultimately, the needs of asynchronous and synchronous cryptographic systems are, at certain design points, mutually exclusive (in my amateur estimation, anyway). I don't think that implies that email encryption is somehow a dead-end or pointless. Email merely, by virtue of being an asynchronous protocol, cannot meaningfully offer PFS (or can it? Some smart people over at crypto.stackexchange.com seem to think there might be papers floating around that can get at it: <a href="https://crypto.stackexchange.com/questions/9268/is-asynchronous-perfect-forward-secrecy-possible" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://crypto.stackexchange.com/questions/9268/is-asynchronous-perfect-forward-secrecy-possible</a>).To me, the killer feature of PGP is actually not encryption per se. It's certification, signatures, and authentication/authorization. I'm more concerned with "so-and-so definitely said/attested to this" than "i need to keep what so-and-so said strictly private/confidential forever and ever." What smaller countries like Croatia have done with <a href="https://tenforward.social/tags/PKI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PKI</a> leaves me green with envy.

l<a href="https://mastodon.social/@eff" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@eff</a> <a href="https://hachyderm.io/@evacide" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@evacide</a> GnuPG is not the only way to encrypt email, I use <a href="https://fosstodon.org/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> with Thunderbird and <a href="https://chaos.social/@delta" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@delta</a>, both don't use GPG.Also pages <a href="https://ssd.eff.org/module/how-use-pgp-linux" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://ssd.eff.org/module/how-use-pgp-linux</a> and <a href="https://ssd.eff.org/module/how-use-pgp-windows" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://ssd.eff.org/module/how-use-pgp-windows</a> are outdated, Thunderbird now has built-in OpenPGP implementation and Enigmail does not work with the latest versions.

𝕂𝚞𝚋𝚒𝚔ℙ𝚒𝚡𝚎𝚕»Gmail Gets End-To-End Encryption From Google As 21'st Birthday Present: […] Google Claims To Have Invented An Entirely New Type Of Encryption For Gmail Users […]«This is not an April joke and yes Google offers OpenPGP for Gmail Accounts. This is not difficult to set up but too many people are too lazy in my opinion.📧 <a href="https://www.forbes.com/sites/daveywinder/2025/04/01/gmail-gets-end-to-end-encryption-from-google-as-21st-birthday-present/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.forbes.com/sites/daveywinder/2025/04/01/gmail-gets-end-to-end-encryption-from-google-as-21st-birthday-present/</a><a href="https://chaos.social/tags/e2ee" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#e2ee</a> <a href="https://chaos.social/tags/openpgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openpgp</a> <a href="https://chaos.social/tags/email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#email</a> <a href="https://chaos.social/tags/gmail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gmail</a> <a href="https://chaos.social/tags/mail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mail</a> <a href="https://chaos.social/tags/itsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#itsec</a> <a href="https://chaos.social/tags/encryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#encryption</a> <a href="https://chaos.social/tags/google" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#google</a> <a href="https://chaos.social/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a> <a href="https://chaos.social/tags/april" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#april</a> <a href="https://chaos.social/tags/endtoendencryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#endtoendencryption</a> <a href="https://chaos.social/tags/pgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pgp</a> <a href="https://chaos.social/tags/joke" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#joke</a> <a href="https://chaos.social/tags/birthday" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#birthday</a> <a href="https://chaos.social/tags/nojoke" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nojoke</a> <a href="https://chaos.social/tags/april" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#april</a> <a href="https://chaos.social/tags/ransomware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ransomware</a>

StefanEs werden ja immer wieder neue Schlüssel zur Kommunikation erstellt. Diese müssten ja auch irgendwann auslaufen / ausgetauscht werden. D.h. wenn der Client länger nicht online war, bekommt man keine neue Schlüssel mehr. Ich denke, dass dies dann ein paar Probleme machen wird. Beispiel: Dein Computer geht kaputt. Es dauert ein paar Tage bis du einen neuen besorgt hast und diesen wieder eingerichtet hast. In der Zeit hast du aber einige Nachrichten bekommen. Man hat zwar ein Backup, aber vielleicht nicht gerade ein tägliches. Mit <a href="https://devlug.de/social?t=openpgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> via <a href="https://devlug.de/social?t=xmpp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#XMPP</a> müsste man sich keinen Kopf machen. Die Nachricht kann man ohne Probleme lesen. Bei PFS könnte dies komplexer werden. Wenn Personen mehrere Geräte haben, dann haben diese Person auch mehrere Schlüsseln. Das kann dann zu einem kleinen Schlüssel Chaos führen. Es wird für den normalen User ggf. auf die Verwendung von "Blind Trust" hinauslaufen. Mal ein Beispiel, welches ich so nicht haben, mir aber vorstellen könnte. Man verwendet ein Theam-Chat. Vielleicht auch ein Chat mit Kunden. Der Chef selber ist zwar nicht im Chat oder vielleicht nicht immer alle Kollegen. Allerdings sollten bestimmte Personen im Fall von Krankheit / Urlaub Zugriff haben können. Das stelle ich mir mit PFS auch schwerer vor. Bei OpenPGP ist es bestimmt einfacher. CC: <a href="https://freie-re.de/users/qbi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@qbi@freie-re.de</a> <a href="https://gruene.social/users/Gerbsen" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Gerbsen@gruene.social</a> <a href="https://osna.social/users/ber" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ber@osna.social</a>

profanityMore information about <a href="https://devlug.de/social?t=openpgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> for <a href="https://devlug.de/social?t=xmpp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#XMPP</a> (<a href="https://devlug.de/social?t=ox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OX</a>) in <a href="https://devlug.de/social?t=profanity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#profanity</a>: <code>man 1 profanity-ox-setup</code>. <a href="https://devlug.de/social?t=gnupg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GnuPG</a> CC: <a href="https://social.mdosch.de/martin" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@martin@social.mdosch.de</a> <a href="https://mathstodon.xyz/users/caten" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@caten@mathstodon.xyz</a> <a href="https://mastodon.social/users/Goffi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Goffi@mastodon.social</a> <a href="https://fosstodon.org/users/gajim" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@gajim@fosstodon.org</a>

vanitasvitaeJust figured out, that the massive performance hit my <a href="https://fosstodon.org/tags/PGPainless" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PGPainless</a> test suite was suffering since I started to port to a newer BC version was caused by the default S2K iteration count being bumped to 0xff instead of 0x60. This had caused the runtime of the test suite to rise to 7 minutes compared to ~1 minute.I decided to dial down the default value again, but make it customizable :D<a href="https://fosstodon.org/tags/openpgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openpgp</a>

Delta ChatWe are not aware of other FOSS development teams that have as extensive knowledge, both theoretical and practical, about <a href="https://chaos.social/tags/email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#email</a> and <a href="https://chaos.social/tags/openpgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openpgp</a> and regularly release across all platforms for users world wide ... except for <a href="https://chaos.social/tags/protonmail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#protonmail</a> with whose technical and security experts we discuss regularly. They are the other major game in town doing pervasive email encryption after all. Did you know that Proton's and delta's VCards are compatible across ecosystems and establish immediate encryption?

Delta Chat<a href="https://jura.social/@mathilde" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mathilde</a> <a href="https://chaos.social/tags/chatmail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chatmail</a> server users don't have these problems because they don't even need to know their password or email address. Messages in delta chat are stored locally and the server only stores them for a limited time, up to 20 days by default, so all devices have a chance to download the message. Blocklists are also not used, the only requirements are <a href="https://chaos.social/tags/DKIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DKIM</a> signature and <a href="https://chaos.social/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> encryption.

Neustradamus :xmpp: :linux:<a href="https://mastodon.social/tags/GnuPG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GnuPG</a> 2.5.5 (dev) has been released (<a href="https://mastodon.social/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> / <a href="https://mastodon.social/tags/GPG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPG</a> / <a href="https://mastodon.social/tags/GNUPrivacyGuard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GNUPrivacyGuard</a> / <a href="https://mastodon.social/tags/PGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PGP</a> / <a href="https://mastodon.social/tags/PrettyGoodPrivacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PrettyGoodPrivacy</a> / <a href="https://mastodon.social/tags/Security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Security</a> / <a href="https://mastodon.social/tags/Gpg4win" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gpg4win</a>) <a href="https://gnupg.org/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://gnupg.org/</a>

Anthony AcciolyMy latest "Bringing PGP to the 21st Century" update: I’ve set up WKD for all my "public-facing" identities, with both direct and advanced methods working across the relevant domains. I’ve also uploaded all my keys to Keybase, OpenPGP, and Ubuntu keyservers. I even even generated a QR code with the openPGP4FPR URI scheme: <a href="https://openpgpkey.accioly.social/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://openpgpkey.accioly.social/</a>PGP experts, am I missing anything?<a href="https://accioly.social/tags/WKD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WKD</a> <a href="https://accioly.social/tags/PGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PGP</a> <a href="https://accioly.social/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> <a href="https://accioly.social/tags/EmailSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EmailSecurity</a> <a href="https://accioly.social/tags/DigitalSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DigitalSecurity</a> <a href="https://accioly.social/tags/Encryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Encryption</a> <a href="https://accioly.social/tags/Cryptography" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Cryptography</a>

Delta ChatThe downside of our project approach was that we often got experts being very dismissive on re-using email and <a href="https://chaos.social/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> ... and there still is some opposition which often subsides when actually trying <a href="https://chaos.social/tags/deltachat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#deltachat</a> and <a href="https://chaos.social/tags/chatmail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chatmail</a>, looking at security audits and our strong usable security focus. There may also be surprising upsides. The UK "Online Safety Bill" which attacks end-to-end encryption integrity seems to not apply for ... e-mail. Because everyone knows, e-mail is unencrypted, right? :)

Pirate PraveenHas anyone here on <a href="https://social.masto.host/tags/fedi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fedi</a> figured out the correct recipe for dealing with <a href="https://social.masto.host/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a>, <a href="https://social.masto.host/tags/DMARC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DMARC</a> and <a href="https://social.masto.host/tags/mailman" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mailman</a> ?The problem, by default mailman will modify messages and this will break the dkim signature. <a href="https://gitlab.com/mailman/mailman/-/issues/1079" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://gitlab.com/mailman/mailman/-/issues/1079</a>Mailman provides two DMARC mitigation options (other option is reject or discard which is not useful in this case).1. Replace the from address with list address 2. Wrap original message in an envelopethunderbird flags 1 and fails 2. <a href="https://social.masto.host/tags/askfedi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#askfedi</a> <a href="https://social.masto.host/tags/gnupg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gnupg</a> <a href="https://social.masto.host/tags/gpg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gpg</a> <a href="https://social.masto.host/tags/thunderbird" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#thunderbird</a>

Em :official_verified:New Privacy Guides article 🔑✨ by me: If you are using a YubiKey, you might get in some situations where you need to reset your key to factory default, and/or set up a backup of it on a spare key.This tutorial will guide you through each step to reset and back up your YubiKey successfully, with clear instructions and plenty of visual support.I hope you find it helpful!<a href="https://www.privacyguides.org/articles/2025/03/06/yubikey-reset-and-backup/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.privacyguides.org/articles/2025/03/06/yubikey-reset-and-backup/</a><a href="https://infosec.exchange/tags/PrivacyGuides" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PrivacyGuides</a> <a href="https://infosec.exchange/tags/Privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Privacy</a> <a href="https://infosec.exchange/tags/Yubico" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Yubico</a> <a href="https://infosec.exchange/tags/YubiKey" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#YubiKey</a> <a href="https://infosec.exchange/tags/Security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Security</a> <a href="https://infosec.exchange/tags/OTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OTP</a> <a href="https://infosec.exchange/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> <a href="https://infosec.exchange/tags/Encryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Encryption</a> <a href="https://infosec.exchange/tags/MFA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MFA</a>

Lars WirzeniusI've made release 0.3.0 of sopass, my command line password manager that uses a Stateless OpenPGP implementation for cryptography.* configuration file * add value from named file or stdin * default to rsop * manual page, built-in help<a href="https://sopass.liw.fi/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://sopass.liw.fi/</a><a href="https://toot.liw.fi/tags/sopass" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sopass</a> <a href="https://toot.liw.fi/tags/pass" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pass</a> <a href="https://toot.liw.fi/tags/passwordManager" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#passwordManager</a> <a href="https://toot.liw.fi/tags/commandLine" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#commandLine</a> <a href="https://toot.liw.fi/tags/cli" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cli</a> <a href="https://toot.liw.fi/tags/openpgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openpgp</a> <a href="https://toot.liw.fi/tags/statelessOpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#statelessOpenPGP</a> <a href="https://toot.liw.fi/tags/sop" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sop</a>

Recherches récentes

Options de recherche

Administré par :

Statistiques du serveur :

#openpgp