One issue that was raised in private email is that making lynx support HTTPS via linking against OpenSSL might not be a good idea since OpenSSL does have CA root certificates. This seems to be a known problem:
CR6661895: /etc/sfw/openssl/certs has no well known CA certificates. Does ARC have any comment or thoughts about this, or should this bug be given any higher priority? I just wanted to raise this issue before we decided to integrate so we can decide whether to add openSSL HTTPS support to lynx or not. Brian Brian Cameron wrote: > Template Version: @(#)onepager.txt 1.35 07/11/07 SMI > Copyright 2007 Sun Microsystems > > 1. Introduction > 1.1. Project/Component Working Name: > > lynx 2.8.6 > > 1.2. Name of Document Author/Supplier: > > Dermot McCluskey > > 1.3. Date of This Document: > > 07-Nov-2008 > > 1.3.1. Date this project was conceived: > > 01-Oct-2008 > > 1.4. Name of Major Document Customer(s)/Consumer(s): > > 1.4.1. The PAC or CPT you expect to review your project: > > Solaris PAC > > 1.4.2. The ARC(s) you expect to review your project: > > LSARC > > 1.4.3. The Director/VP who is "Sponsoring" this project: > > robert.odea at sun.com > > 1.4.4. The name of your business unit: > > OPG / OpenSource. > > 1.5. Email Aliases: > 1.5.1. Responsible Manager: > > tom.garland at sun.com > > 1.5.2. Responsible Engineer: > > dermot.mccluskey at sun.com > > 1.5.3. Marketing Manager: > > glynn.foster at sun.com > > 1.5.4. Interest List: > > desktop-discuss at opensolaris.org > > 4. Technical Description: > 4.1. Details: > > Lynx is an open-source text-only web browser. It is an > ncurses-based > app which allows users to browse web pages from non-GUI > environments > like a terminal or the console. > > Lynx is not intended to replace the Firefox web browser in > OpenSolaris, but does have advantages in certain scenarios. It is > useful where only a text-based environment is available and in > low-bandwidth setups. It may also be useful for some visually- > impared users. > > Lynx uses OpenSSL to access HTTPS encrypted URLs. This use is > covered by an existing contract (PSARC 2003/500 Contract 07). > > This proposal adds Lynx 2.8.6, the latest stable version, to > OpenSolaris. > > This proposal seeks Minor release binding. > > 4.2. Bug/RFE Number(s): > > None. > > 4.3. In Scope: > > See above. > > 4.4. Out of Scope: > > See above. > > 4.5. Interfaces: > > > -------------------------------------------------------------------- > Exported Stability Comments > > -------------------------------------------------------------------- > SUNWlynx Uncommitted > > /usr/bin/lynx Volatile Command > /usr/share/lynx/lynx.cfg Volatile General config file > /usr/share/lynx/lynx.lss Volatile Style sheet config > > lynx.1 Uncommitted > > > -------------------------------------------------------------------- > Imported Stability Comments > > -------------------------------------------------------------------- > ncurses Volatile LSARC 2008/524 > OpenSSL Volatile PSARC 2006/019 > > > 4.6. Doc Impact: > > A community provided man page is included. Help documentation in > HTML format is also included. Lynx is also configured to access > the User Guide online. > > 4.7. Admin/Config Impact: > > None. > > 4.8. HA Impact: > > None. > > 4.9. I18N/L10N Impact: > > The JDS and G11N teams are working together to evaluate and > provide I18N/L10N support. > > 4.10. Packaging & Delivery: > > Adds one new package, SUNWlynx. > > 4.11. Security Impact: > > None. > > 4.12. Dependencies: > > Lynx depends of the software listed in the Imported > Interfaces section. > > 5. Reference Documents: > Lynx manpage: lynx.1 (see case materials) > Output of "lynx --help": lynx-help-output.txt (see case materials) > > The Lynx homepage: http://lynx.isc.org/ > > LSARC 2008/524, ncurses for OpenSolaris > PSARC 2006/019, OpenSSL upgrade to 0.9.8a > PSARC 2003/500, OpenSSL in /usr/sfw > http://sac.sfbay.sun.com/arc/PSARC/2003/500/contracts/contract-07: > contract covering use of OpenSSL interfaces.
