Your message dated Sat, 29 Aug 2009 10:34:46 -0400
with message-id <[email protected]>
and subject line re: #401447 lynx doesn't accept wildcard certificates
has caused the Debian Bug report #401447,
regarding lynx doesn't accept wildcard certificates
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
401447: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=401447
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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 foo.com but not bar.com.
Lynx in its current implementation in Debian sid does not understand this.
Since the misdetection of SSL certificates is of severity important I
assume that this is as well as it renders valid certificates sort of
invalid.
Regards,
Joey
--
Have you ever noticed that "General Public Licence" contains the word "Pub"?
Please always Cc to me when replying to me on the lists.
--- End Message ---
--- Begin Message ---
--
Thomas E. Dickey <[email protected]>
http://invisible-island.net
ftp://invisible-island.net
signature.asc
Description: Digital signature
--- End Message ---
