Subject: [sup-talk] Unnecessary warning: "multipart/signed with signature content type application/pkcs7-signature

From: [email-masked] (Alan De Smet)
Date: Wed, 12 Dec 2007 17:12:20 -0600

I'm trying out sup 0.3, installed via "gem install sup".  I was
importing a bunch of mboxes using "sup-add mbox:/path/to/mbox ;
sup-sync".  I got the following warning repeatedly:

[Wed Dec 12 16:49:32 -0600 2007] warning: multipart/signed with signature content type application/pkcs7-signature

Scanning the code, it looks like this is being generated by
message.rb line 296, which is only prepared to accept
application/pgp-signature.  I'm guessing sup isn't currently
prepared to handle this type of signature.  While validating it
would be a nice touch, I can live without it, since mutt doesn't
check it either.  But emitting warnings doesn't seem helpful.
The warnings just add noise, especially since I have a fair
number of such messages in my archives.  The warning also doesn't
specify why the situation is bad, and what the ramifications are.
If the warning is kept, perhaps it should say something like "sup
cannot currently validate this type of signature and will ignore
it."

For reference, I've attached an example I found in the real
world.  I've tested it and it generates the warning in question.
For more examples, check out this mailing list archive (from
which I originally got the message):
https://lists.cs.wisc.edu/archive/condor-users/2006-October.txt

-- 
Alan De Smet                              Condor Project Research
adesmet at cs.wisc.edu                http://www.cs.wisc.edu/condor/
-------------- next part --------------
>From condor-users-bounces at cs.wisc.edu  Thu Oct  5 20:03:11 2006
To: Condor-Users Mail List <condor-users at cs.wisc.edu>
From: Jens-Soenke Voeckler <voeckler at isi.edu>
Date: Thu, 5 Oct 2006 17:56:55 -0700
Subject: [Condor-users] symlinks, local and NFS disks, and DAGMan
Reply-To: Condor-Users Mail List <condor-users at cs.wisc.edu>
Sender: condor-users-bounces at cs.wisc.edu
Status: RO
Content-Length: 5725
Lines: 114

--===============1917438543==
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-13--747094070;
	protocol="application/pkcs7-signature"

--Apple-Mail-13--747094070
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=ISO-8859-1;
	delsp=yes;
	format=flowed

Hi,

with 6.8.1, DAGMan refuses to start a workflow that has the Condor =20
common user log on an NFS disk. So I leave a symlink to a local disk, =20=

to satisfy it. Unfortunately, DAGMan has developed a habit of =20
removing the common log when it finds one (without backups, mind =20
you!), eliminating my symlink, and then dies complaining again. It is =20=

virtually impossible to run anything until I move manually the whole =20
workflow to a local disk - I am against hard-coding an absolute path =20
to my log file. I do understand that Linux NFS cannot be trusted =20
(I've been burned myself often enough on it), so I see why it =20
complains. However, the removal of prior logs screws my work-around =20
symlink, never mind my post mortem processing of data should I =20
restart a workflow. Do you think this feature (I am talking about the =20=

log removal) of DAGMan is fixable?

Aloha,
Dipl.-Ing. Jens-S. V=F6ckler   voeckler at isi dot edu
University of Southern California Viterbi School of Engineering
Information Sciences Institute; 4676 Admiralty Way Ste 1001
Marina Del Rey, CA 90292-6611; USA; +1 310 448 8427
* You can rely on any shared filesystems for only one thing - don't! *

--Apple-Mail-13--747094070
Content-Transfer-Encoding: base64
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s

--Apple-Mail-13--747094070--

--===============1917438543==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to condor-users-request at cs.wisc.edu with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users

The archives can be found at either
https://lists.cs.wisc.edu/archive/condor-users/
http://www.opencondor.org/spaces/viewmailarchive.action?key=CONDOR
--===============1917438543==--

---

From: [email-masked] (Alan De Smet)
Date: Wed, 12 Dec 2007 17:48:28 -0600

I've also see the variant "application/x-pkcs7-signature", so:
> [Wed Dec 12 17:46:43 -0600 2007] warning: multipart/signed with signature content type application/x-pkcs7-signature

---

From: [email-masked] (William Morgan)
Date: Thu, 13 Dec 2007 17:13:05 -0800

> [Wed Dec 12 16:49:32 -0600 2007] warning: multipart/signed with signature content type application/pkcs7-signature

I've removed the warning in SVN. Thanks for the report. One day we'll
support that...

-- 
William <wmorgan-sup at masanjin.net>