John Gardiner Myers wrote:
Nelson B wrote:

Perhaps if people would file bugzilla bugs every time they get one of
those useless error messages, the PSM folks would begin to appreciate
the gravity of the issue.


Wouldn't be helpful. All such bugs are blocked on NSS bug 172051.

That's an interesting assertion. Bug 172051 does not implement a new API for PSM to call. The bugs currently marked as "blocked" by 172051 have no patches attached to them that are being held off by 172051.

In short, no work has apparently been done to address PSM's many error
message shortcomings.  For starters, PSM should have ONE function that
deals with error messages.  Instead it has many.  So an error code
that is handled properly in one place is not handled properly in any
other places.  THAT problem is in no way blocked by any non-PSM code.

At the very least PSM needs to be able to show the error code number
to the user when it has nothing more informative to say.  No message of
the "unknown error" or "invalid or corrupt" variety should fail to
report the underlying error code.

There's also the problem that nobody that I'm aware of is working on S/MIME.

AFAIK, all the present problems with S/MIME that come to mind have to do with the MIME part of SMIME. There are complaints, for example, that MIME messages with attachments that contain signatures are always treated as if they were signed S/MIME messages. But that's not an NSS problem. It's a problem in the MIME handling of the message. I don't know who owns that.

I don't recall any bugs with the processing of the CMS messages, (well,
except that we don't extract CRLs from them, which doesn't seem to be
hurting anyone)

But let's not deflect the issue.  There are lots of things that can and
do go wrong with SSL and SMIME, such as cert related problems, which are
not defects in SSL nor in SMIME, that currently cause useless dialogs
to be displayed.  The solutions to those problems require better error
handling in PSM, and nowhere else.

This isn't your fault, John.  You inherited this situation.  But as the
new PSM module owner, it's now on your plate, if I'm not mistaken.

--
Nelson B

_______________________________________________
mozilla-crypto mailing list
[EMAIL PROTECTED]
http://mail.mozilla.org/listinfo/mozilla-crypto

Reply via email to