Robert Relyea wrote:
> Now technically KMail MUST implement RC2-40 (is the implementers
> confusing RC2 with RC5?) according to the S/MIME spec (all
> implementations must support RC2-40.
I read the S/MIME spec differently. Quoting Section 2.7 from
http://www.apps.ietf.org/rfc/rfc3851.html#sec-2.
Robert Relyea wrote:
> Martin Hoefling wrote:
>> Just to reduce confusion about my mail: I am Martin Hoefling (using
>> KMail/Kontact), and Wurstsemmel is using Thunderbird. We encountered the
>> problems, while testing communication via S/Mime certificates.
>>
>> As far as we understood, this is
Martin Hoefling wrote:
Nelson B wrote:
Hi Nelson and others...
Nelson Bolyard wrote:
I will send an encrypted reply to the email I received. We'll see if
my correspondent can decrypt it.
Just to reduce confusion about my mail: I am Martin Hoefling (using
KMail/Kontact), and
Nelson B wrote:
Hi Nelson and others...
> Nelson Bolyard wrote:
>
>> I will send an encrypted reply to the email I received. We'll see if
>> my correspondent can decrypt it.
Just to reduce confusion about my mail: I am Martin Hoefling (using
KMail/Kontact), and Wurstsemmel is using Thunderbird
Nelson Bolyard wrote:
> I will send an encrypted reply to the email I received. We'll see if
> my correspondent can decrypt it.
I remembered that mozilla doesn't "import" (save) an encryption cert
from an email unless it can validate that cert. That means the cert
has to have been issued by a t
Previously, a user calling himself wurstsemmel and I had this discussion:
>>> There are several separate issues here:
>>>
>>> 1) NSS is not matching on AES. - This is the biggest issue.
>>> 2) For some reason NSS is not negotiating 3DES (is KMail sending 3DES
>>> in the profile. If not, that's a K
Nelson Bolyard wrote:
wurstsemmel wrote:
thanks for your fast reply. Before I can write the bug report, I should
somehow verify, that KMail is definitely requesting AES.
I should add, that MS OE shows 3DES as "preferred algorithm from the
sender" (sorry, this is translated from the German l
wurstsemmel wrote:
> thanks for your fast reply. Before I can write the bug report, I should
> somehow verify, that KMail is definitely requesting AES.
>
> I should add, that MS OE shows 3DES as "preferred algorithm from the
> sender" (sorry, this is translated from the German localized OE
> vers
Hi Bob,
thanks for your fast reply. Before I can write the bug report, I should
somehow verify, that KMail is definitely requesting AES.
I should add, that MS OE shows 3DES as "preferred algorithm from the
sender" (sorry, this is translated from the German localized OE
version), if you send an eM
wurstsemmel wrote:
The behavior of Tb arises from its handling of the S/MIME capabilities.
KMail requests an algorithm (I think AES), which Tb does not support. In
this case Tb seems to fall back to RC2.
please write a bug about this. https://bugzilla.mozilla.org
Product would be under 'Othe
Hello,
Mr. Rod Whiteley from the MozillaZine Thunderbird Forums gave me the
hint to bring up my questions in this newsgroup.
We experienced, that Tb uses the algorithm RC2 if you send a S/MIME
encrypted eMail to KMail. KMail (and Claws Mail) use gpgsm to handle the
S/MIME mails. In gpgsm the R
11 matches
Mail list logo
