ortenzia konyha wrote: > I have found some old mailiing (year 1998) and a newer one but does not seem > to find any solution > (http://comments.gmane.org/gmane.comp.web.lynx.devel/7483) about lynx not > supporting https, but I guess the problem is in my configuration.
When I was investigating openssl versus gnutls, I remember reading some archived e-mails about license issues with lynx and https support. The GNU GPL license used by Lynx is not compatible with the OpenSSL (4 clause) license (at least when it comes to distributing). The lynx developers list mentioned looking into gnutls as an alternative, but the license on the gnutls OpenSSL compatibility layer (GPLv3) was also not compatible with the lynx license (GPLv2). According to the thread, the developers were looking into using nss and it appears there is support for nss in more recent versions of lynx. The developers considered the possibility of changing the lynx license to add an exception for OpenSSL, but they would be unable to contact everyone who contributed in order to get the lynx license change approved. If anyone's interested, you can check the lynx-dev archives for further discussions on the topic. Was thinking nss was probably the best way to go for lynx and SSL support. BLFS users typically aren't going to be distributing their systems. However, if some distributions are switching to nss to avoid copyright conflicts when distributing, it's probably better debugged with lynx than some of the other options. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
