Patrick wrote: > > If I have a customized callback method in my NSS app, where I do some cert > checks, and I now have a new reason for rejecting the incoming peer cert, > but how can I make that new reason available to the peer on the other end > of the connection? As it stands now, the peer gets a rather generic > message: "(-12225) SSL peer does not support certificates of the type it > received"...
The error codes reported by peers are limited to the error codes defined in the SSL and TLS protocols, and those error codes are rather generic and limited. -- Nelson Bolyard Disclaimer: I speak for myself, not for Netscape
