Re: Shimming HTTP to HTTPS.

From	peter@easthope.ca
Newsgroups	linux.debian.user
Subject	Re: Shimming HTTP to HTTPS.
Date	2019-08-22 18:10 +0200
Message-ID	<yxXOW-8fR-15@gated-at.bofh.it> (permalink)
References	<yl0rf-2xo-3@gated-at.bofh.it> <yl8RR-86l-15@gated-at.bofh.it> <yoUng-2YL-7@gated-at.bofh.it> <yoUGB-36x-5@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

*	From: Reco 
*	Date: Sun, 28 Jul 2019 19:57:19 +0300
> ... NSS is not the best TLS implementation. There's some hope for 
> dillo depending on if it uses openssl or gnutls.

How do you evaluate these?  Published review?  Study of sources?

> Have you meant "Oberon sends HTTP request that should be transformed to
> HTTPS"? That's where that hypothetical proxy comes in.

OK, yes.  If http://en.wikipedia.org/wiki/Linux is put in the URL bar 
of dillo, it opens https://en.wikipedia.org/wiki/Linux. If 
https://en.wikipedia.org/wiki/Linux is put in the URL bar,  dillo 
opens it.  I imagine similar behaviour in Oberon.

> Oberon browser sends HTTP request, but gets HTTPS redirect (301/302) in
> result.

Yes; ideally, redirection is handled gracefully.

> Oberon browser sends HTTP request, proxy transforms it into HTTPS, gets
> HTTPS reply, transforms it back into HTTP reply ... only to send Oberon
> browser a huge pile of HTTPS links to pictures, css, js and whatnot.

For now I'd be happy if Oberon could open the text in a 
simple page.  https://en.wikibooks.org/wiki/Oberon/S3/2003-01-05/Mail.Mod
for example.

> [1] https://github.com/tenox7/wrp

Appears that a X86-64 or ARM system is required.  Or possibly compile 
the source for the old 32 system here; athough, if this could work the 
binary would probably be available.

Probably better to forget this approach and work on SSL/TLS for 
Oberon. Dillo works quite well.  No reason Oberon can't.

Thanks,                                     ... P.

-- 
https://en.wikibooks.org/wiki/Oberon
Tel: +1 604 670 0140            Bcc: peter at easthope. ca

Thread

HTTP shimmed to HTTPS; was Re: stunnel as transparent proxy. peter@easthope.ca - 2019-07-18 00:20 +0200
  Re: HTTP shimmed to HTTPS; was Re: stunnel as transparent proxy. Reco <recoverym4n@enotuniq.net> - 2019-07-18 09:20 +0200
    Re: Shimming HTTP to HTTPS. peter@easthope.ca - 2019-07-28 18:40 +0200
      Re: Shimming HTTP to HTTPS. Reco <recoverym4n@enotuniq.net> - 2019-07-28 19:00 +0200
        Re: Shimming HTTP to HTTPS. David Wright <deblis@lionunicorn.co.uk> - 2019-07-29 02:50 +0200
        Re: Shimming HTTP to HTTPS. peter@easthope.ca - 2019-08-22 18:10 +0200
          Re: Shimming HTTP to HTTPS. Reco <recoverym4n@enotuniq.net> - 2019-08-22 19:40 +0200
        Re: Shimming HTTP to HTTPS. peter@easthope.ca - 2019-08-23 19:30 +0200
      Re: Shimming HTTP to HTTPS. David Wright <deblis@lionunicorn.co.uk> - 2019-07-29 02:50 +0200
        Re: Shimming HTTP to HTTPS. Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-29 08:30 +0200
          Re: Shimming HTTP to HTTPS. David Wright <deblis@lionunicorn.co.uk> - 2019-07-29 18:50 +0200
        Re: Shimming HTTP to HTTPS. peter@easthope.ca - 2019-08-14 05:10 +0200
          Re: Shimming HTTP to HTTPS. David Wright <deblis@lionunicorn.co.uk> - 2019-08-15 00:10 +0200

csiph-web