Re: gpgsm 1.9.22 supports no RC2 Algorithm ?

On Mon, 16 Apr 2007 21:42, M_Hoellernurfuerspam.de said:

> hier sind noch ein paar Details, laut der thunderbird
entwicker liste 
> wird RC2 gar nicht mehr verwendet,,, aber das gpgsm log
sagt was 
> anderes. 

[ According to the TB dev ML, RC2 is not used...but the
gpgsm log tells
  something different]

> OpenPGP: id=BDD13B90; url=http://tinyurl.com/5d8mm

Cool feature: let TinyURL.com know whenever someone wants to
verify
that message for the first time.

> 4 - 2007-04-16 21:32:46 gpgsm[7623.0x8084a98] DBG:
<- DECRYPT
>   4 - 2007-04-16 21:32:46 gpgsm[7623]: unsupported
algorithm 
> `1.2.840.113549.3.2'
>   4 - 2007-04-16 21:32:46 gpgsm[7623]: (Dies ist der
RC-2 Algorithmus)

> demnach muss Thunderbird eine RC2 Verschlüsselung
geschickt haben. Wie 
> kann das sein wenn diese von TB gar nicht unterstützt
wird? Oder 
> kommt gpgsm durch was anderes aus dem Tritt?

[ so TB must have send a message using RC2.  How can that
happen if TB
  does not support RC2.  Or is it a gpgsm problem? ]

Look at the error handling code:

              rc = gpg_error
(GPG_ERR_UNSUPPORTED_ALGORITHM);
              log_error ("unsupported algorithm
`%s'n", algoid? algoid:"?");
              if (algoid && !strcmp (algoid,
"1.2.840.113549.3.2"))
                log_info (_("(this is the RC2
algorithm)n"));

RC2 has clearly been identified.  To get a second opinion,
you might
want to run dumpasn1 over the message (remove the base64
first) and
see that dumpasn1 will tell you the same.


Shalom-Salam,

   Werner


_______________________________________________
Gnupg-devel mailing list
Gnupg-develgnupg.org
h
ttp://lists.gnupg.org/mailman/listinfo/gnupg-devel

Hello,

I am sorry I am not an expert.., but how can I remove the
base64 
first? 

On Dienstag, 17. April 2007, Werner Koch wrote:
> RC2 has clearly been identified.  To get a second
opinion, you
> might want to run dumpasn1 over the message (remove the
base64
> first) and see that dumpasn1 will tell you the same.

I hope someone can help me: The mail I have at hand, which
is not 
encrypted, b/c the mail is detected as RC2 looks like this:

Thanks a lot 
Michael


Return-Path: <xxxx.yyyyweb.de>
X-Flags: 1001
Delivered-To: GMX delivery to zzzzzgmx.de
Received: (qmail invoked by alias); 16 Apr 2007 22:02:20
-0000
Received: from smtprelay03.ispgateway.de (EHLO 
smtprelay03.ispgateway.de) [80.67.18.15]
  by mx0.gmx.net (mx009) with SMTP; 17 Apr 2007 00:02:20
+0200
Received: (qmail 12481 invoked from network); 16 Apr 2007 
22:02:20 -0000
Received: from unknown (HELO [192.168.1.115]) (817251[85.176.97.251])
          (envelope-sender <andre.bacherweb.de>)
          by smtprelay03.ispgateway.de (qmail-ldap-1.03)
with SMTP
          for <zzzzzgmx.de>; 16 Apr 2007 22:02:20 -0000
Message-ID: <4623F24A.4060004web.de> 
(sfid-20070417_063847_591224_FAD1344B)
Date: Tue, 17 Apr 2007 00:01:46 +0200
From: =?ISO-8859-15?Q?yyyyyyweb.de>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; de;
rv:1.8.0.9) 
Gecko/20061207 Thunderbird/1.5.0.9 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Michael Hoeller <zzzzzzrgmx.de>
Subject: Re: crypto-test04 nur sig
References: <200704162347.35838.zzzzgmx.de>
In-Reply-To: <200704162347.35838.zzzzzgmx.de>
X-Enigmail-Version: 0.94.3.0
OpenPGP: id=3B56E5C4;
	
url=http://pgpkeys.pca.dfn.de/pks/lookup?op
=get&search=0xB397AEB03B56E5C4
Content-Type: application/x-pkcs7-mime;
  name="smime.p7m"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="smime.p7m"
Content-Description: S/MIME Encrypted Message
X-GMX-Antivirus: -1 (not scanned, may not use virus scanner)
X-GMX-Antispam: 4 (From mass domain over foreign mail
server)
X-GMX-UID: W8QQcpReTXs9HN8LSGY5HrBKRzdyMkOh
X-CRM114-Version: 20070301-BlameBaltar ( TRE 0.7.5 (LGPL) ) 
MR-BD9991E2 
X-CRM114-CacheID: sfid-20070417_063847_591224_FAD1344B 
X-CRM114-Status: GOOD (  19.98  )
X-UID: 
Status: R
X-Status: NC
X-KMail-EncryptionState:  
X-KMail-SignatureState:  
X-KMail-MDN-Sent:  

MIAGCSqGSIb3DQEHA6CAMIACAQAxggMTMIIBcgIBADBaMFQxFDASBgNVBAoT
C0NBY2VydCBJ
bmMuMR4wHAYDVQQLExVodHRwOi8vd3d3LkNBY2VydC5vcmcxHDAaBgNVBAMT
E0NBY2VydCBD
[...]
AMWCgKRGqlIzgjMIh6XbgCI6xLJ5p107aXb4ylA81oY1neZmdGU6pyQ7hh9B
AbmwOUnsDHNj
l0shKsDccPtpMnExtNhIUitHHXjpHAztvnetmZ1Lc2okMwZrkPZk9BCcmrjb
5PDBFUljKePG
OpyV01GGBLPUMLMHQLxn8CNn3iROhogWaW9KWd7GqMeZzuB/boIJgMbu0Mzp
4gg2Lc7oJ+jr
WCWtu1uubfnYv30XiA282P4IyA4Hc/Kb4ey+W800GJodCoQ0ErgQF21Qh9V0
tIlAJDK775dW
NxIygebEqlSPTxDwWs8zp807iimnFVpnW0cPH6avBYWnkCDbt2OHKGlLXQes
zo8cVXqpeLNE
zh7WndeOhNRpFO5mtVzFtMnpezgbW4rPZuD5t3Wnhb0ESJxh6uH4chl7kIB0
DnfQd80pB97s
J1umFJsHQ1nW/lMMTxJvEHvJ6T3YoZamV3QY5xKd1R4fqeY3QEQWrsmePD84
meG2tU3C9wQI
3nOxqQ+B/6sAAAAAAAAAAAAA

_______________________________________________
Gnupg-devel mailing list
Gnupg-develgnupg.org
h
ttp://lists.gnupg.org/mailman/listinfo/gnupg-devel