Bądźmy szczerzy. Byłem zwolennikiem #OpenPGP (czy ogólniej #PGP) przez długi czas. I w sumie nadal nie jestem w stanie wskazać żadnej sensownej alternatywy. I wierzyłem, że PGP nie jest "tak trudne" — ale wcale nie staje się łatwiejsze. A wielkim problemem z tego typu standardami są narzędzia.

#WebOfTrust jest trudne, i dla wielu ludzi niepraktyczne. I nie pomaga tu to, w jaki sposób wiele programów decyduje się obsługiwać kwestie zaufania kluczy. Czasem dostaję zaszyfrowaną pocztę — i #EvolutionMail znacznie utrudnia mi jednorazową odpowiedź z szyfrowaniem, o ile nie zdecyduję się *permanentnie* zaufać nadawcy.

Bajzel z serwerami kluczy SKS nie pomógł. Dziś znaleźć czyjś klucz to szukanie igły w stogu siana. Jeżeli mamy szczęście, wystarczy WKD. Jeżeli nie, to możemy przeszukać serię różnych serwerów kluczy, GitHuba, strony internetowe. I czasem po drodze znajdziemy klucze już nieważne, bo ludzie aktualizują tylko w niektórych miejscach, albo w ogóle zapominają wysłać aktualne.

No i wchodzi problem niezgodności programów. Nie świadczy to dobrze o PGP, że GnuPG nie jest w stanie zaimportować kluczy z popularnych serwerów, bo nie mają identyfikatorów użytkownika. A to tylko czubek góry lodowej.

Za rogiem czeka rozbieżność standardów OpenPGP, która dopiero przyniesie prawdziwe problemy. Wyobraźcie sobie, że przekonaliście kogoś do OpenPGP, i za chwilę musicie tej osobie wyjaśniać, że użyła nieprzenośnego narzędzia albo niewłaściwych ustawień, i stworzyła klucz, którego nie jesteście w stanie użyć.

Nie tak zachęca się ludzi do szyfrowania.

#szyfrowanie

Let's be honest. I've been a strong supporter of #OpenPGP (or #PGP in general) for a long time. And I still can't think of any real alternative that exists right now. And I kept believing it's not "that hard" — but it doesn't seem like it's getting any easier. The big problem with standards like that are tools.

#WebOfTrust is hard, and impractical for a lot of people. It doesn't really help how many tools implement trust. I mean, I sometimes receive encrypted mail via #EvolutionMail — and Evolution makes it really hard for me to reply encrypted without permanently trusting the sender!

The whole SKS keyserver mess doesn't help PGP at all. Nowadays finding someone's key is often hard. If you're lucky, WKD will work. If you're not, you're up for searching a bunch of keyservers, GitHub, or perhaps random websites. And it definitely doesn't help that some of these may hold expired keys, with people uploading their new key only to a subset of them or forgetting to do it.

On top of that, we have interoperability issues. Definitely doesn't speak well when GnuPG can't import keys from popular keyservers over lack of UIDs. And that's just the tip of the iceberg.

Now with diverging OpenPGP standards around the corner, we're a step ahead from true interoperability problems. Just imagine convincing someone to use OpenPGP, only to tell them afterwards that they've used non-portable tool / settings, and their key doesn't work for you.

That's really not how you advocate for #encryption.

@padraig Currently, I'm using #Xfce. Before that, I was on #KDE. I've dabbled in #MATE and #Budgie, but I'm most comfortable back on Xfce, especially since I found out that #EvolutionMail works with my employer's Exchange server.
😂🎉 BREAKING: Evolution Mail users are as easily trackable as a toddler in a tutu trying to sneak past bedtime. The "privacy protection feature" is about as effective as a chocolate teapot, and the developers seem to think fixing it is like trying to find a unicorn. 🦄🔍
https://www.grepular.com/Evolution_Mail_Users_Easily_Trackable #EvolutionMail #PrivacyFail #TrackableUsers #ChocolateTeapot #UnicornHunt #HackerNews #ngated
Evolution Mail Users Easily Trackable - Grepular

Mike Cardwell's Tech Blog. Security, privacy, and technology

Evolution Mail Users Easily Trackable - Grepular

Mike Cardwell's Tech Blog. Security, privacy, and technology

Hey #Evolution mail users, does anyone know how to make folders with new messages change color to make it more obvious where you new messages are, like how #Thunderbird does it? That's the one big QOL improvement Thunderbird has, for my use case.

#Linux #EvolutionMail

I think I finally fixed, at least for now, my problem with #EvolutionMail

I ended up re-installing the package via Synaptic, after a few rounds of cancelling its attempts to load the list of messages it was supposed to have already deleted. They must have been stored somewhere that wasn't being updated properly, but I haven't a clue where. And then that would propagate back to the server, and so on.

It's not getting caught in an update loop either, which is nice.

I think what's happening with my junk folder in #EvolutionMail is that when I delete it, the messages get moved over to the trash folder, but then marked as junk and moved *back* to the junk folder, somehow getting duplicated in the process.

I have no idea why it's doing this, or how to stop it.

I have what seems to be a serious bug with the #Gnome #EvolutionMail client, and I really don't know how to get help.

I have a bunch of spam messages in the spam folder. When I try to delete them, they get transferred to the trash, as they should. But when I try to empty the trash, they get flagged as junk and returned to the junk folder AND duplicated.

After a few tries to solve this I have OVER 750 MESSAGES in my junk folder that I can't get rid of.

HELP!

#Linux

@twilliability @birb Fun protocol demonstration. Has anybody built loops yet or do you white list? As an application, it feels backwards to me, because it centralizes feed aggregation that can easily be done on the client, where I believe it belongs. I.e. I am reading a bunch of feeds including Mastodon with #evolutionMail 's RSS integration.