troet.cafe ist Teil eines dezentralisierten sozialen Netzwerks, angetrieben von Mastodon.
Hallo im troet.cafe! Dies ist die derzeit größte deutschsprachige Mastodon Instanz zum tröten, neue Leute kennenlernen, sich auszutauschen und Spaß zu haben.

Verwaltet von:

Serverstatistik:

7,3 Tsd.
aktive Profile

Mehr erfahren

#smime

1 Beitrag1 Beteiligte*r0 Beiträge heute

Does anybody have a good link for a „How to create detailed logs“? I don’t really get how to do it.

I need detailed information what decisions Thunderbird „makes“ in terms of /signatures/verification when opening a mail.



Hands down the best part about switching away from #Microsoft #Windows and onto #LinuxMint is #Evolution.

Evolution blows
#Thunderbird completely out of the water in just about every imaginable sense. If #GNU came out with a native Windows version of Evolution they would blow both #Outlook and Thunderbird out of the water.

There simply is no comparison.

And the best part?
#PGP/ #GnuPG and #SMIME support built-in and out-of-the-box! No add-ons or plugins required.

I mean,
#Kmail is nice, but it doesn't even come close.

https://en.wikipedia.org/wiki/GNOME_Evolution

en.wikipedia.orgGNOME Evolution - Wikipedia

After some #Thunderbird update, I've started to get notices about incorrect S/MIME signatures in emails which was previously marked as correct. The error message was obscure - something about an unknown issue.

No quick solution was found. After some time, I've tried again to figure out what is the problem, and this Czech article solved it: postsignum.cz/files/navody/thu

Shortly - Thunderbird dropped support of #SHA1 #checksum in #SMIME signatures and failed to provide any human-readable error message in that regard.

I believe it is a suboptimal behavior for a number of reasons:

1. I can't avoid getting emails from this source and can't make them upgrade their certificate, really. I have only a choice either to drop the signature check completely or rely on the substandard check. Obviously, in this situation I prefer rather to see the results of the check and probably some info that it is, actually, substandard.

2. Solving the problem needs to realize it first. An obscure error message is not too helpful.

3. Such incidents actually undermine the opinion about #cryptographic #signature check. If you see some error, your first though is not "it is probably a #MITM attack" but "probably something is broken in the signature check".

The possibility to fix everything is, however, good.

www.postsignum.czThunderbird - Nastavení ověření S/MIME

Have you ever wondered what it means when you get an email that is encrypted but not signed? At the very least, it's better than being completely unencrypted, isn't it?

It turns out that's not necessarily the case. I've looked at S/MIME and found that it is possible to construct messages that, when sent to multiple recipients, are decrypted into completely different messages:

lutrasecurity.com/en/articles/

lutrasecurity.com Salamander/MIME – Lutra SecurityIf you remember kobold letters, you already know not to blindly trust emails. But it’s not just HTML emails that can be deceiving. In this article, we’ll take a look at S/MIME and how we can use the concept of invisible salamanders to craft messages that tell each recipient a different story. Let’s talk about Salamander/MIME.

uh oh my second ever support ticket at fastmail has been opened. but i think it's actually a bug in #ios18_1.

mail.app imap server settings don't allow me to use my fastmail username of emory at kvet dot ch. straight up says it's invalid. sending relay configuration (submission 587/tcp) is accepting that username fine so idk. i am going to see if i can force it with a profile.

i have a new #sMIME cert for my email addresses anyway!

I am disappointed that on #iOS 18 I still cannot add an S/MIME certificate from another person except when they send me an eMail first. My use case is that I download the vCard, .pem or .cer (or whatever) from site like globaltrustpoint.com #smime #email #encryption
support.apple.com/en-us/102245

Apple SupportUse S/MIME to send and receive encrypted messages in the Mail app in iOS - Apple SupportiOS supports S/MIME so that you can send encrypted email messages. 

EN:
Unfortunately, I can't find a good entry point for this topic:
How do you implement server-side mail encryption and decryption for s/mime? I use Postfix+Cyrus.

DE:
Ich finde für das Thema leider keinen guten Einstieg:
Wie realisiert ihr serverseitige Mailver- und entschlüsselung für s/mime? Ich nutze Postfix+Cyrus.

#linux#foss#cyrus