Re: pine, and x509 certificates (fwd)

On Fri, 7 Apr 2006, Mark Crispin wrote:

> We agree, and alternative names will be supported in the next release of Pine.

Nice!

> If you like, you can get this support by rebuilding Pine 4.64, replacing the
> existing pine4.64/imap tree with the imap-2006 development snapshot on
> 	ftp://ftp.cac.washington.edu/mail/imap-2006.DEV.tar.Z

I'll give it a try next week. The name suggest it will onlybe for IMAP,
dont forget SMTP :)


> On Mon, 3 Apr 2006, Thorsten Glaser wrote:
> > Kolbj$Bx(Brn Barmen dixit:
> > > On Fri, 10 Mar 2006, Kolbj$Bx(Brn Barmen wrote:
> > > > It appears to me that pine doesnt respect DNS entries in "X509v3 Subject
> > > > Alternative Name" in certificates on validation, instead it just
> > > > complains that CN doesnt match.
> > > > Am I correct, and if so.. will it be fixed?
> > > I havent seen any reply on this, consider this a reminder :)
> > I haven't seen the original mail.
> > Well, I tried to implement it in Lynx, but adding support for
> > multiple CNs in the DN is *much* easier and works in more
> > places anyway so I suggest to use that in your certs instead.
> > Only they are not _my_ certificates, they are certificates that are
> > installed on various IMAP and SMTP servers that I use. Other clients have
> > no problems with them, so why should pine?

Uhm, what happened to the quote levels here?

And charset:
To: =?ISO-2022-JP?Q?Kolbj=F8rn_Barmen?= <[email protected]>
Message-ID: <[email protected]>
Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1; FORMAT=flowed

ISO-2022-JP sent as ISO-8859-1? No need to answer, just want to inform
that this ended up somewhat strange here, the iso-8859-1 ø in my name
ended up as "$Bx(B" ("<esc>$Bx<esc>(B") in your reply. But then I
understand it was forwarded to you as well.

-- 
Kolbjørn Barmen
UNINETT Driftsenter
_______________________________________________
Pine-info mailing list
[email protected]
http://mailman1.u.washington.edu/mailman/listinfo/pine-info