Hi Martjin,
maybe you can help me with the following issues:
On incoming signed E-Mails, Djigzo puts the CN of the sender's
intermediate CA next to the "X-Djigzo-Info-Signer-ID-0-1"-header.
Shouldn't it be the CN of the sender's user certificate which is displayed?
Same thing happens with the "
X-Djigzo-Info-Encryption-Recipient-0-0"-Header in incoming encrypted
E-Mails.
Is there a way to use the value of the FROM-header instead of the
default CN ("persona non-validated" by default) for automatically
generated certificates?
As long as outgoing emails have their source in my trusted environment,
this would make things easier without representing a security issue.
Is it possible to use end-to-end encryption for specific users, so that
a specific user has it's own private key stored on his client and djigzo
only passes through the encrypted email?
I tried to do so. But as I don't have any CA except Djigzo's built-in
CA, i created the internal user and its certificate with the built-in
CA, exported the key to the client, deleted the user, but Djigzo still
decrypts incoming E-Mail for this user before. Is this a bug or working
as intended?
Kind regards,
Bernhard
_______________________________________________
Users mailing list
[email protected]
http://lists.djigzo.com/lists/listinfo/users
