pouet.chapril.org est l'un des nombreux serveurs Mastodon indépendants que vous pouvez utiliser pour participer au fédiverse.
Chapril https://www.chapril.org est un projet de l'April https://www.april.org

Administré par :

Statistiques du serveur :

1,1K
comptes actifs

#gpg

5 messages4 participants0 message aujourd’hui

Made a few updates and released a new version of #calliope , a #bash script based utility to write a journal using #LaTeX. Since it's #LaTeX based, you can pretty much add whatever you wish to your journal---images, other PDFs, beautiful maths, and of course, you can customise it as you wish to suit your needs. It's all managed by #Git and if you'd like you can encrypt your journal entries using #gpg

Check it out on #GitHub : github.com/sanjayankur31/calli

Simple script for journal writing using LaTeX. Contribute to sanjayankur31/calliope development by creating an account on GitHub.
GitHubGitHub - sanjayankur31/calliope: Simple script for journal writing using LaTeXSimple script for journal writing using LaTeX. Contribute to sanjayankur31/calliope development by creating an account on GitHub.
A répondu dans un fil de discussion

@Xeniax Totally nerdsniped :D I'd love to be a part of the study.

I don't think that #KeyServers are dead. I think they evolved into Verifying Key Servers (VKS), like the one run by a few folks from the OpenPGP ecosystem at keys.openpgp.org/about . More generally, I believe that #PGP / #GPG / #OpenPGP retains important use-cases where accountability is prioritized, as contrasted with ecosystems (like #Matrix, #SignalMessenger) 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 #KeyOxide 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: crypto.stackexchange.com/quest).

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 #PKI leaves me green with envy.

keys.openpgp.orgkeys.openpgp.org

#GitHub "enterprise" has some very weird properties:
* commits made with my email address not from the organization are not counted in statistics (oh how I despise these stats...)
* my #gpg signed commits are shown as unverified even though gh has my public key on my personal profile
* I can not add my public key nor my well known email address to my enterprise profile

All of this "enterprise"-junk just puts me off. No, #GitHub is not #git.

#Gwit est un protocole de publication de contenus textuels (sites, documentation, etc) simplissime, pensé pour fonctionner essentiellement hors-ligne. Il est basé sur #Git et #PGP. Il permet de repartager des sites (même hors ligne) sans risque que le contenu ait été modifié

Pour le moment, seuls deux sites existent à ma connaissance ^^. Mais n'importe quel site statique léger peut facilement être "hébergé" sur Gwit.

gwit : sr.ht/~ivilata/gwit/

#gpg #offline

1/2

sr.htgwit: gwit - Web sites over Git
A répondu dans un fil de discussion

Has anyone here on #fedi figured out the correct recipe for dealing with #OpenPGP, #DMARC and #mailman ?

The problem, by default mailman will modify messages and this will break the dkim signature.
gitlab.com/mailman/mailman/-/i

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 envelope

thunderbird flags 1 and fails 2.
#askfedi #gnupg #gpg #thunderbird

GitLabAdd DMARC conformity mode (do not modify DKIM signed headers and body) (#1079) · Tickets · GNU Mailman / Mailman Core · GitLabCRITICAL I deployed mm3 to my e-mail server working with the large Linux developer community and we are facing DMARC issues [1]. It seems that...
A répondu dans un fil de discussion

#FOSDEM 2025 - anyone interested into #GPG key signing?

If you're interested:
* Provide a printed snippet of your fingerprint (gpg-key2ps)
* I will send you the signing to your email (instead of uploading them to key servers [gpg-mailkeys])
* You can find my key at gpg.gyptazy.com and you're allowed to upload them to key servers.
* Have you passport / ID card with you to validate your identity
* I'll probably be mostly in the #BSDDevroom but you can also ping me on Matrix

Happy key signing!

gpg.gyptazy.comgyptazy | GPG Key
#encryption#freebsd#bsd

My $.02 - any service that claims to make your E-mail secure or private is utterly, completely, irretrievably bogus.

E-mail is a store and forward protocol where any given hop on the E-mail's potentially multi-hop journey may well be and probably is "en claire" the cryptographers might say.

You want secure email? Treat it like something shouted into a crowded room and encrypt it at before it even gets into the pipeline.

Yes, #GPG is a pain but honestly? If you want fully private encrypted yada why not just use #Signal and call it a day? :)

Has anbody a clue why #pass tells me "gpg: decryption failed: No secret key" but when I use plain gpg --decrypt bla.gpg it shows me its contents without problems? I had an expired gpg key and created a new one, but meanwhile already imported my old one. My feeling is that pass is using the wrong GPG key, but I have no clue where to configure it which one to use. Any help appreciated #encryption #gpg #linux #terminal

I haven't adopted #PassKeys for my accounts because, as far as I can tell, there aren't really any options that let me own my private key and store it myself; they all depend on trusting somebody like Google, Meta or Apple to handle it for you, which completely defeats the purpose in my opinion. Like #PGP / #GPG, I want to own the private key so I can manage it myself. Trusting your PassKey to a third party app that's only on your phone introduces a single point of failure.