Bug#401447: lynx doesn't accept wildcard certificates

2008-07-19 Thread Joey Schulze
Andreas Metzler wrote: > This is supposed to be fixed in 2.8.7dev9-1.2 (lynx-cur codebase). > Since I do not know a site using a wildcard certificate, I cannot > verify this. Good to know! Thanks. Regards, Joey -- MIME - broken solution for a broken design. -- Ralf Baechle Please al

Bug#401447: lynx doesn't accept wildcard certificates

2008-07-18 Thread Andreas Metzler
This is supposed to be fixed in 2.8.7dev9-1.2 (lynx-cur codebase). Since I do not know a site using a wildcard certificate, I cannot verify this. cu andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'

Bug#401447: lynx doesn't accept wildcard certificates

2006-12-04 Thread Thomas Dickey
On Mon, Dec 04, 2006 at 08:38:17AM +0100, Martin Schulze wrote: > Thomas Dickey wrote: > > On Sun, Dec 03, 2006 at 06:40:08PM +0100, Martin Schulze wrote: > > > Martin Schulze wrote: > > > > Package: lynx > > > > Version: 2.8.5-2sarge2.2 > > > > btw, lynx-cur contains something analogous. > > You

Bug#401447: lynx doesn't accept wildcard certificates

2006-12-03 Thread Martin Schulze
Thomas Dickey wrote: > On Sun, Dec 03, 2006 at 06:40:08PM +0100, Martin Schulze wrote: > > Martin Schulze wrote: > > > Package: lynx > > > Version: 2.8.5-2sarge2.2 > > btw, lynx-cur contains something analogous. You mean, lynx-cur has this fixed? Or that it suffers from the same problem? Regard

Bug#401447: lynx doesn't accept wildcard certificates

2006-12-03 Thread Thomas Dickey
On Sun, Dec 03, 2006 at 06:40:08PM +0100, Martin Schulze wrote: > Martin Schulze wrote: > > Package: lynx > > Version: 2.8.5-2sarge2.2 btw, lynx-cur contains something analogous. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgpoxWy86USBF.pgp Description: PGP signa

Bug#401447: lynx doesn't accept wildcard certificates

2006-12-03 Thread Martin Schulze
Martin Schulze wrote: > > According to RFC 2818 Section 3.1 certificates may contain the wildcard > > character * which is considered to match any single domain name component > > or component fragment. E.g., *.a.com matches foo.a.com but not > > bar.foo.a.com. f*.com matches foo.com but not bar.co

Bug#401447: lynx doesn't accept wildcard certificates

2006-12-03 Thread Martin Schulze
Martin Schulze wrote: > Package: lynx > Version: 2.8.5-2sarge2.2 > Severity: important > > According to RFC 2818 Section 3.1 certificates may contain the wildcard > character * which is considered to match any single domain name component > or component fragment. E.g., *.a.com matches foo.a.com bu

Bug#401447: lynx doesn't accept wildcard certificates

2006-12-03 Thread Martin Schulze
Package: lynx Version: 2.8.5-2sarge2.2 Severity: important According to RFC 2818 Section 3.1 certificates may contain the wildcard character * which is considered to match any single domain name component or component fragment. E.g., *.a.com matches foo.a.com but not bar.foo.a.com. f*.com matches