"Could not identify PKCS#7 type" error

"Could not identify PKCS#7 type" error

[Vladimir Volovich]

Hi,

when viewing s/mime encoded messages, i (still) get an error
"Could not identify PKCS#7 type". i traced the function
mm-view-pkcs7-get-type and it appears that it looks for the regexp

"0┌..\x06	\\*├H├В\x01\a\x03"

but the buffer " *temp*" begins with

"0─\x06	*├H├В\x01\a\x03"

(sorry for binary data)

does this mean that the contents of the encrypted part is invalid, or
the regexp is buggy?

note that these encrypted s/mime messages are viewed fine with
e.g. netscape, so it looks like a bug in gnus.

Best,
v.

Re: "Could not identify PKCS#7 type" error

[Simon Josefsson]

Vladimir Volovich <vvv@vsu.ru> writes:

> Hi,
> 
> when viewing s/mime encoded messages, i (still) get an error
> "Could not identify PKCS#7 type". i traced the function
> mm-view-pkcs7-get-type and it appears that it looks for the regexp
> 
> "0‚..\x06	\\*†H†В\x01\a\x03"
> 
> but the buffer " *temp*" begins with
> 
> "0€\x06	*†H†В\x01\a\x03"

Ah, of course, the regexp should cater for various BER length fields.
Does it work now?

> does this mean that the contents of the encrypted part is invalid, or
> the regexp is buggy?
> 
> note that these encrypted s/mime messages are viewed fine with
> e.g. netscape, so it looks like a bug in gnus.

Yes, assume Gnus is buggy when S/MIME doesn't work (and please send a
bug report).  It hasn't been tested much.

Re: "Could not identify PKCS#7 type" error

[Vladimir Volovich]

"SJ" == Simon Josefsson writes:

 SJ> Ah, of course, the regexp should cater for various BER length
 SJ> fields.  Does it work now?

finally, it mostly works, thanks! :)

"mostly" means that after decrypting i see a few headers (generated by
openssl) inside the body of the message:

From: Andy Igoshin <ai@vsu.ru>
Subject: test
To: vvv@vsu.ru
Date: Sun, 05 Aug 2001 16:00:40 +0400

Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 8bit

Hi!

[skipped]

Best,
v.

Re: "Could not identify PKCS#7 type" error

[David S. Goldberg]

[-- Attachment #1: Type: text/plain, Size: 568 bytes --]

After watching this conversation go on for a bit, I finally decided to
try again to read an encrypted message with gnus.  First I updated to
the latest CVS (as of about 20010806 0900 EDT).  I opened the message,
ran W s and was prompted for my key file and then the passphrase for
it.  So far so good.  But then came the attached backtrace.  Is this a
result of my running an older XEmacs?  Is there some package I can
update?  Upgrading XEmacs is non-trivial for me at work, at least on
the machine I want to use for mail

Thanks,
-- 
Dave Goldberg
dsg@world.std.com

[-- Attachment #2: Type: text/plain, Size: 2188 bytes --]

Signaling: (void-function make-temp-file)
  make-temp-file("smime")
  smime-decrypt-region(1 13258 nil)
  mm-view-pkcs7-decrypt((#<buffer " *mm*"> ("application/x-pkcs7-mime" (name . "smime.p7m")) base64 nil ("attachment" (filename . "smime.p7m")) "S/MIME Encrypted Message" nil nil))
  mm-view-pkcs7((#<buffer " *mm*"> ("application/x-pkcs7-mime" (name . "smime.p7m")) base64 nil ("attachment" (filename . "smime.p7m")) "S/MIME Encrypted Message" nil nil))
  mm-display-inline((#<buffer " *mm*"> ("application/x-pkcs7-mime" (name . "smime.p7m")) base64 nil ("attachment" (filename . "smime.p7m")) "S/MIME Encrypted Message" nil nil))
  mm-display-part((#<buffer " *mm*"> ("application/x-pkcs7-mime" (name . "smime.p7m")) base64 nil ("attachment" (filename . "smime.p7m")) "S/MIME Encrypted Message" nil nil) t)
  byte-code("..." [ignored string-match type throw nil mm-inline-override-p handle 4 "inline" mm-attachment-override-p not-attachment mm-automatic-display-p mm-inlinable-p mm-inlined-p mm-automatic-external-display-p t display split-string mm-handle-media-type "/" "text" text gnus-article-mime-handle-alist beg id gnus-unbuttonized-mime-type-p gnus-insert-mime-button gnus-article-insert-newline move -1 gnus-newsgroup-charset (set-buffer gnus-summary-buffer) ((error)) gnus-newsgroup-ignored-charsets mail-parse-ignored-charsets mail-parse-charset mm-display-part mm-insert-inline mm-get-part gnus-treat-article bufferp gnus-article-mime-handles 1] 7)
  gnus-mime-display-single((#<buffer " *mm*"> ("application/x-pkcs7-mime" (name . "smime.p7m")) base64 nil ("attachment" (filename . "smime.p7m")) "S/MIME Encrypted Message" nil nil))
  gnus-mime-display-part((#<buffer " *mm*"> ("application/x-pkcs7-mime" (name . "smime.p7m")) base64 nil ("attachment" (filename . "smime.p7m")) "S/MIME Encrypted Message" nil nil))
  gnus-display-mime()
  gnus-article-prepare-display()
  gnus-article-prepare(64 nil)
  gnus-summary-display-article(64 nil)
  gnus-summary-select-article(nil force)
  #<compiled-function nil "...(10)" [known mm-decrypt-option mm-verify-option gnus-summary-select-article nil force] 3 nil nil>()
  call-interactively(gnus-summary-force-verify-and-decrypt)

Re: "Could not identify PKCS#7 type" error

[Simon Josefsson]

dsg@world.std.com (David S. Goldberg) writes:

> After watching this conversation go on for a bit, I finally decided to
> try again to read an encrypted message with gnus.  First I updated to
> the latest CVS (as of about 20010806 0900 EDT).  I opened the message,
> ran W s and was prompted for my key file and then the passphrase for
> it.  So far so good.  But then came the attached backtrace.  Is this a
> result of my running an older XEmacs?  Is there some package I can
> update?  Upgrading XEmacs is non-trivial for me at work, at least on
> the machine I want to use for mail

It is my fault.  I will try to fix this soon, meanwhile:

(defun make-temp-file (prefix) (make-temp-name prefix))

Re: "Could not identify PKCS#7 type" error

[David S. Goldberg]

> (defun make-temp-file (prefix) (make-temp-name prefix))

Works great now.  Thanks!

-- 
Dave Goldberg
dsg@world.std.com

Re: "Could not identify PKCS#7 type" error

[Simon Josefsson]

Vladimir Volovich <vvv@vsu.ru> writes:

> "mostly" means that after decrypting i see a few headers (generated by
> openssl) inside the body of the message:

Fixed.

"Could not identify PKCS#7 type" error

[Vladimir Volovich]

Hi,

> when viewing s/mime encoded messages, i (still) get an error
> "Could not identify PKCS#7 type". i traced the function
> mm-view-pkcs7-get-type and it appears that it looks for the regexp
> 
> "0┌..\x06	\\*├H├В\x01\a\x03"
> 
> but the buffer " *temp*" begins with
> 
> "0─\x06	*├H├В\x01\a\x03"

namely, the raw message contains:

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

MIAGCSqGSIb3DQEHA6CAMIACAQAxggWyMIIC1QIBADCBvDCBtjELMAkGA1UEBhMCUlUxGjAY
BgNVBAgTEUJsYWNrIFNvaWwgUmVnaW9uMREwDwYDVQQHEwhWb3JvbmV6aDEiMCAGA1UEChMZ
Vm9yb25lemggU3RhdGUgVW5pdmVyc2l0eTEoMCYGA1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2
aWNlcyBEaXZpc2lvbjEPMA0GA1UEAxMGdnN1LnJ1MRkwFwYJKoZIhvcNAQkBFgpub2NAdnN1
LnJ1AgEBMA0GCSqGSIb3DQEBAQUABIICALZwbBJ+ebt/fCwmxpX4AsvQV5lwBpYS34aH7qKe
4IIypVSsk6suyGXXm+dKVkxFIQRm/hOyf3H15rw4NazN22Oj0Y8fAeZK8xQPH6UCkBuYZUMa

[skipped]

FiWH7P9TS2XNh1/pw5aCZdAEQBts/A92+w2eUyJZUPDYpS4/4PJXcfrMVL/+AiRRHIYxcw6j
KjeXVWaQt3IdT8jo4FqddauEUcHr2hQ/7gRp4ogECBY0YNL77sCZBDCtvqSn3JWYMttPp4RI
5LklXuSia2am69SIthMYqo9tatu/qkQE44sq5A6R1xLmKEIECBPwC4bo6FHUAAAAAAAAAAAA
AA==

if you base64-decode it, you will see the starting string.
it does not match 0\202, so the regexp is buggy.

Best,
v.