Re: [Lynx-dev] Lynx does NOT default to https support[SOLVED]

[LarryL]

On Wed, 23 May 2018 02:46:02 -0500, Larry Hynes   
wrote:



LL wrote:


Hi,
Brew uninstalled openssl@1.1, BUT could not uninstall openssl@1.0:

lynx2.8.9dev.19 $ brew uninstall openssl@1.0
Error: Refusing to uninstall /usr/local/Cellar/openssl/1.0.2n
because it is required by lftp, libssh2, midnight-commander, pyenv,  
which

are currently installed.
You can override this and force removal with:
   brew uninstall --ignore-dependencies openssl@1.0
lynx2.8.9dev.19 $

Therefore, my OS X output as requested:


And what about

lynx2.8.9dev.19 $ ./lynx https://news.google.com

__^^^_^_^^_^^^
SOLVED!
Thanks for replying to my post.
LL
PS. trick in everything

___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev

Re: [Lynx-dev] Lynx does NOT default to https support

[LarryL]

Hi,
Brew uninstalled openssl@1.1, BUT could not uninstall openssl@1.0:

lynx2.8.9dev.19 $ brew uninstall openssl@1.0
Error: Refusing to uninstall /usr/local/Cellar/openssl/1.0.2n
because it is required by lftp, libssh2, midnight-commander, pyenv, which
are currently installed.
You can override this and force removal with:
brew uninstall --ignore-dependencies openssl@1.0
lynx2.8.9dev.19 $

Therefore, my OS X output as requested:

lynx2.8.9dev.19 $ make distclean
rm -f WWW/Library/*/*.[aoib]
rm -f WWW/Library/*/.created
cd ./WWW/Library/Implementation &&
/Applications/Xcode.app/Contents/Developer/usr/bin/make  DESTDIR=""
CC="gcc" clean
rm -f core *.core *.leaks *.[oi] *.bak tags TAGS
rm -f dtd_util
rm -f ./*.o
cd ./src && /Applications/Xcode.app/Contents/Developer/usr/bin/make
DESTDIR="" CC="gcc" clean
rm -f lynx core *.core *.leaks *.i *.o *.bak tags TAGS test_*
cd chrtrans && /Applications/Xcode.app/Contents/Developer/usr/bin/make
DESTDIR="" CC="gcc" clean
rm -f makeuctb *.o *uni.h *uni2.h *.i
rm -f *.b ./src/lynx *.leaks cfg_defs.h LYHelp.h lint.*
rm -f help_files.sed
rm -f core *.core
rm -f WWW/Library/*/*~
rm -f WWW/Library/*/*.bak
rm -rf ./src/obsolete
cd ./WWW/Library/Implementation &&
/Applications/Xcode.app/Contents/Developer/usr/bin/make  DESTDIR=""
CC="gcc" distclean
rm -f core *.core *.leaks *.[oi] *.bak tags TAGS
rm -f dtd_util
rm -f ./*.o
made distclean
cd ./src && /Applications/Xcode.app/Contents/Developer/usr/bin/make
DESTDIR="" CC="gcc" distclean
rm -f lynx core *.core *.leaks *.i *.o *.bak tags TAGS test_*
cd chrtrans && /Applications/Xcode.app/Contents/Developer/usr/bin/make
DESTDIR="" CC="gcc" clean
rm -f makeuctb *.o *uni.h *uni2.h *.i
cd ./src/chrtrans &&
/Applications/Xcode.app/Contents/Developer/usr/bin/make  DESTDIR=""
CC="gcc" distclean
rm -f makeuctb *.o *uni.h *uni2.h *.i
rm -rf obsolete
rm -f core *.bak *.sav *~ *.h_old
rm -f *~ *.bak *.sav tags TAGS
rm -f ./WWW/Library/Implementation/makefile ./src/makefile
./src/chrtrans/makefile
rm -f makefile lynx_cfg.h config.status config.log config.cache
rm -f lynx


lynx2.8.9dev.19 $ ./configure --with-ssl=/usr/local/opt/openssl
checking build system type... x86_64-apple-darwin13.4.0
checking host system type... x86_64-apple-darwin13.4.0
checking target system type... x86_64-apple-darwin13.4.0
Configuring for darwin13.4.0
checking for DESTDIR...
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for executable suffix...
checking for object suffix... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking version of gcc... 6.0
checking for gcc option to accept ANSI C... none needed
checking $CC variable... ok
checking how to run the C preprocessor... gcc -E
checking if preprocessor -C option works... yes
checking whether ln -s works... yes
checking whether make sets ${MAKE}... yes
checking for a BSD compatible install... /usr/bin/install -c
checking for bison... bison -y
checking for lint... no
checking for cppcheck... no
checking for splint... no
checking for makeflags variable...
checking if filesystem supports mixed-case filenames... no
checking for exctags... no
checking for ctags... ctags
checking for exetags... no
checking for etags... etags
checking for ctags... yes
checking for windres... none
checking for ranlib... ranlib
checking for ar... ar
checking for options to update archives... -curv
checking if you want to see long compiling messages... yes
checking if you want to check memory-leaks... no
checking if you want to enable debug-code... no
checking if you want to enable lynx trace code *recommended* ... yes
checking if you want verbose trace code... no
checking if you want to turn on gcc warnings... no
checking if you want to use dbmalloc for testing... no
checking if you want to use dmalloc for testing... no
checking $CC variable... ok
checking for gcc option to accept ANSI C... -DCC_HAS_PROTOS
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking for _LARGE_FILES value needed for large files... no
checking for _LARGEFILE_SOURCE value needed for large files... no
checking for fseeko... yes
checking whether to use struct dirent64... no
checking for PATH separator... :
checking for msginit... no
checking for ranlib... (cached) ranlib
checking for ANSI C header files... yes
checking for inline... inline
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for off_t... yes
checking for size_t... yes
checking for working alloca.h... yes
checking for alloca... yes
checking for stdlib.h... (cached) yes
checking for unistd.h... (cached) yes
checking 

Re: [Lynx-dev] Lynx does NOT default to https support

[LarryL]

Hi,
Apple must have OpenSSL blocked in firmware:

src$ ./lynx https://news.google.com

Alert!: This client does not contain support for HTTPS URLs.

lynx: Can't access startfile https://news.google.com/
src$
***
I'm stumped!
LL


On Tue, 22 May 2018 11:45:46 -0500, Larry Hynes   
wrote:



LL wrote:

On Tue, 22 May 2018 03:30:40, Larry Hynes  wrote:

> LL wrote:
>> Hi,
>> For compilers to find HomeBrew OpenSSL, it says you may need to set:
>>  LDFLAGS:  -L/usr/local/opt/openssl@1.1/lib
>>  CPPFLAGS: -I/usr/local/opt/openssl@1.1/include
>> Please confirm, for Lynx https support on OS X.
>> LL
>> PS. Real bear!
>
> /configure --with-ssl=/usr/local/opt/openssl@1.1

Hi,
I recompiled over Lynx defaults w/o uninstalling using:
./configure --with-ssl=/usr/local/opt/openssl@1.1
   make
 make install
***
Still NO https support for:

https://news.google.com

Q: Does it render above URL on OS X, for anyone else?
Kind Regards,
LL


What happens if you cd into the lynx src directory, the one in which you
built lynx, and try

/lynx https://news.google.com


___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev

Re: [Lynx-dev] Lynx does NOT default to https support

[David Woolley]

On 22/05/18 11:59, Halaasz Saandor wrote:

Google decides current best practice?


To the extent that people act on their advice, yes.

___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev

Re: [Lynx-dev] Lynx does NOT default to https support

[Halaasz Saandor]

2018/05/22 04:19 ... David Woolley:
It appears to be a policy pushed by Google, and it looks as though http 
sites will lose their position in Google's search results.


If you impose a no https policy on the internet, you will find that you 
can only access sites that don't know or care about current best practice.


Google decides current best practice?

___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev

Re: [Lynx-dev] Lynx does NOT default to https support

[Larry Hynes]

LarryL  wrote:
> Hi,
> For compilers to find HomeBrew OpenSSL, it says you may need to set:
>  LDFLAGS:  -L/usr/local/opt/openssl@1.1/lib
>  CPPFLAGS: -I/usr/local/opt/openssl@1.1/include
> Please confirm, for Lynx https support on OS X.
> LL
> PS. Real bear!

/configure --with-ssl=/usr/local/opt/openssl@1.1

___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev

Re: [Lynx-dev] Lynx does NOT default to https support

[David Woolley]

On 22/05/18 05:47, Mouse wrote:

PS. https support is essential now days


Perhaps for what you want to do.  I do just fine without it, and,
indeed, if lynx defaulted to HTTPS support on, I would disable it
before building - I neither have nor want HTTPS support.  (On my home
machines, that is.  At work, on work machines - I use lynx both at home
and at work - I build an HTTPS-capable version because that's what work
needs.)


The current advice to web site operators is that http sites should 
always redirect to https ones, and there is meta data on some sites that 
relates to this, although I forget the details.  It appears to be a 
policy pushed by Google, and it looks as though http sites will lose 
their position in Google's search results.


If you impose a no https policy on the internet, you will find that you 
can only access sites that don't know or care about current best practice.


___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev

Re: [Lynx-dev] Lynx does NOT default to https support

[Mouse]

> PS. https support is essential now days

Perhaps for what you want to do.  I do just fine without it, and,
indeed, if lynx defaulted to HTTPS support on, I would disable it
before building - I neither have nor want HTTPS support.  (On my home
machines, that is.  At work, on work machines - I use lynx both at home
and at work - I build an HTTPS-capable version because that's what work
needs.)

/~\ The ASCII Mouse
\ / Ribbon Campaign
 X  Against HTMLmo...@rodents-montreal.org
/ \ Email!   7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev

Re: [Lynx-dev] Lynx does NOT default to https support

[LarryL]

Hi,
For compilers to find HomeBrew OpenSSL, it says you may need to set:
LDFLAGS:  -L/usr/local/opt/openssl@1.1/lib
CPPFLAGS: -I/usr/local/opt/openssl@1.1/include
Please confirm, for Lynx https support on OS X.
LL
PS. Real bear!

==> Caveats
A CA file has been bootstrapped using certificates from the system
keychain. To add additional certificates, place .pem files in
  /usr/local/etc/openssl@1.1/certs

and run
  /usr/local/opt/openssl@1.1/bin/c_rehash

This formula is keg-only, which means it was not symlinked into /usr/local,
because this is an alternate version of another formula.

If you need to have this software first in your PATH run:
  echo 'export PATH="/usr/local/opt/openssl@1.1/bin:$PATH"' >>  
~/.bash_profile


For compilers to find this software you may need to set:
LDFLAGS:  -L/usr/local/opt/openssl@1.1/lib
CPPFLAGS: -I/usr/local/opt/openssl@1.1/include
For pkg-config to find this software you may need to set:
PKG_CONFIG_PATH: /usr/local/opt/openssl@1.1/lib/pkgconfig

==> Summary
  /usr/local/Cellar/openssl@1.1/1.1.0h: 6,583 files, 15.9MB, built in 4  
minutes 28 seconds

$

On Mon, 21 May 2018 03:35:17 -0500, Larry Hynes <la...@larryhynes.com>  
wrote:



Thomas Dickey <dic...@his.com> wrote:

- Original Message -
| From: russellb...@gmail.com
| To: lynx-dev@nongnu.org
| Sent: Sunday, May 20, 2018 11:44:24 PM
| Subject: [Lynx-dev]  Lynx does NOT default to https support
|
|
|   Asked LarryL: 'Q: How do I get Lynx to rely on external libraries
|   OpenSSL or  GnuTLS, when compiled on OS X?'
|./configure --with-ssl --with-gnutls --enable-gnutls-compat
|

MacOS doesn't have gnutls in its default configuration.
It's probably available as an add-on, but there's no interest.

MacOS does have openssl runtime libraries, but no development headers.
To get that, you would install an add-on (such as MacPorts), which has  
an "openssl" package.


Once you have the development package, "--with-ssl" should just work...


If using homebrew to install openssl on MacOS, note that you'll probably
have to specify the path with something like

./configure --with-ssl=/usr/local/opt/openssl

homebrew does not symlink the headers into /usr/local


___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev

Re: [Lynx-dev] Lynx does NOT default to https support

[LarryL]

Hi,
I just installed MacPorts and external libraries OpenSSL or GnuTLS are  
still foreign to Lynx.
Q1: Does Lynx need to be recompiled using './configure --with-ssl  
--with-gnutls --enable-gnutls-compat'?


Q2: What's the tried-n-true way to uninstall Lynx on OS X, then?
Wishing you a happy day!
LL

$ sudo port -v selfupdate
Password:
--->  Updating MacPorts base sources using rsync

Willkommen auf dem RSYNC-server auf ftp.fau.de.
Nicht all unsere Mirror sind per rsync verfuegbar.

Welcome to the RSYNC daemon on ftp.fau.de.
Not all of our mirrors are available through rsync.

receiving file list ... done

sent 16 bytes  received 55 bytes  28.40 bytes/sec
total size is 85774336  speedup is 1208089.24

Willkommen auf dem RSYNC-server auf ftp.fau.de.
Nicht all unsere Mirror sind per rsync verfuegbar.

Welcome to the RSYNC daemon on ftp.fau.de.
Not all of our mirrors are available through rsync.

receiving file list ... done

sent 16 bytes  received 62 bytes  31.20 bytes/sec
total size is 512  speedup is 6.56
MacPorts base version 2.4.4 installed,
MacPorts base version 2.4.4 downloaded.
--->  Updating the ports tree
Synchronizing local ports tree from  
rsync://rsync.macports.org/macports/release/tarballs/ports.tar


Willkommen auf dem RSYNC-server auf ftp.fau.de.
Nicht all unsere Mirror sind per rsync verfuegbar.

Welcome to the RSYNC daemon on ftp.fau.de.
Not all of our mirrors are available through rsync.

receiving file list ... done
./

sent 68 bytes  received 99 bytes  66.80 bytes/sec
total size is 63812096  speedup is 382108.36
Creating port index in  
/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports


Total number of ports parsed:   0
Ports successfully parsed:  0
Ports failed:   0
Up-to-date ports skipped:   19946

--->  MacPorts base is already the latest version

The ports tree has been updated. To upgrade your installed ports, you  
should run

  port upgrade outdated
$ sudo port upgrade outdated
Nothing to upgrade.


On Mon, 21 May 2018 03:35:17 -0500, Larry Hynes <la...@larryhynes.com>  
wrote:



Thomas Dickey <dic...@his.com> wrote:

- Original Message -
| From: russellb...@gmail.com
| To: lynx-dev@nongnu.org
| Sent: Sunday, May 20, 2018 11:44:24 PM
| Subject: [Lynx-dev]  Lynx does NOT default to https support
|
|
|   Asked LarryL: 'Q: How do I get Lynx to rely on external libraries
|   OpenSSL or  GnuTLS, when compiled on OS X?'
|./configure --with-ssl --with-gnutls --enable-gnutls-compat
|

MacOS doesn't have gnutls in its default configuration.
It's probably available as an add-on, but there's no interest.

MacOS does have openssl runtime libraries, but no development headers.
To get that, you would install an add-on (such as MacPorts), which has  
an "openssl" package.


Once you have the development package, "--with-ssl" should just work...


If using homebrew to install openssl on MacOS, note that you'll probably
have to specify the path with something like

./configure --with-ssl=/usr/local/opt/openssl

homebrew does not symlink the headers into /usr/local



___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev

Re: [Lynx-dev] Lynx does NOT default to https support

[Larry Hynes]

Thomas Dickey <dic...@his.com> wrote:
> - Original Message -
> | From: russellb...@gmail.com
> | To: lynx-dev@nongnu.org
> | Sent: Sunday, May 20, 2018 11:44:24 PM
> | Subject: [Lynx-dev]  Lynx does NOT default to https support
> | 
> | 
> | Asked LarryL: 'Q: How do I get Lynx to rely on external libraries
> | OpenSSL or  GnuTLS, when compiled on OS X?'
> |  ./configure --with-ssl --with-gnutls --enable-gnutls-compat
> | 
> 
> MacOS doesn't have gnutls in its default configuration.
> It's probably available as an add-on, but there's no interest.
> 
> MacOS does have openssl runtime libraries, but no development headers.
> To get that, you would install an add-on (such as MacPorts), which has an 
> "openssl" package.
> 
> Once you have the development package, "--with-ssl" should just work...

If using homebrew to install openssl on MacOS, note that you'll probably
have to specify the path with something like

./configure --with-ssl=/usr/local/opt/openssl

homebrew does not symlink the headers into /usr/local

___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev

Re: [Lynx-dev] Lynx does NOT default to https support

[Thomas Dickey]

- Original Message -
| From: russellb...@gmail.com
| To: lynx-dev@nongnu.org
| Sent: Sunday, May 20, 2018 11:44:24 PM
| Subject: [Lynx-dev]  Lynx does NOT default to https support
| 
| 
|   Asked LarryL: 'Q: How do I get Lynx to rely on external libraries
|   OpenSSL or  GnuTLS, when compiled on OS X?'
|./configure --with-ssl --with-gnutls --enable-gnutls-compat
| 

MacOS doesn't have gnutls in its default configuration.
It's probably available as an add-on, but there's no interest.

MacOS does have openssl runtime libraries, but no development headers.
To get that, you would install an add-on (such as MacPorts), which has an 
"openssl" package.

Once you have the development package, "--with-ssl" should just work...

-- 
Thomas E. Dickey <dic...@invisible-island.net>
http://invisible-island.net
ftp://ftp.invisible-island.net

___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev

[Lynx-dev] Lynx does NOT default to https support

[russellbell]

Asked LarryL: 'Q: How do I get Lynx to rely on external libraries 
OpenSSL or
GnuTLS, when compiled on OS X?'
 ./configure --with-ssl --with-gnutls --enable-gnutls-compat


russell bell

___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev

[Lynx-dev] Lynx does NOT default to https support

[LarryL]

Hi,
Q: How do I get Lynx to rely on external libraries OpenSSL or GnuTLS, when  
compiled on OS X?

Cheers!
LL
PS. https support is essential now days

___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev