HTTP shimmed to HTTPS; was Re: stunnel as transparent proxy.

From	peter@easthope.ca
Newsgroups	linux.debian.user
Subject	HTTP shimmed to HTTPS; was Re: stunnel as transparent proxy.
Date	2019-07-18 00:20 +0200
Message-ID	<yl0rf-2xo-3@gated-at.bofh.it> (permalink)
References	<yl0rf-2xo-5@gated-at.bofh.it> <yl0rf-2xo-7@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

Jul 16 11:25:16 joule stunnel: LOG5[4]: Service [https] accepted connection from 127.0.0.1:36140

*	From: Reco recoverym4n@enotuniq.net
*	Date: Wed, 17 Jul 2019 11:01:32 +0300
> No, you're incorrect. A client application has connected to
> localhost:443 using source IP 127.0.0.1 and a destination port 36140.

OK, thanks.  Can you tell me how "36140" originates?  Not immediately 
obvious that this application produces it.  Also not listed here.
https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers

> stunnel(1) mentions helpfully that you're required to have  a certain
> netfilter setup (mainly involving DNAT in your case), ... 
> If you need to transform outbound HTTP requests to HTTPS to multiple
> hosts ...

Yes, I have a Web browser capable of HTTP and not HTTPS. The immediate 
objective is that the browser requests 
https://en.wikipedia.org/wiki/Network_socket , for example, the 
communication is TLS encrypted and issued to the original address.  
The returned packets should be decrypted.  Should work for any address 
of course but no address translation.  Shim might describe the action 
better than proxy.
                                                                                                                                                       
> you'll probably need squid/haproxy/nginx/whatever.

Never used any of these.  "/" means "or"?  Shorewall is working here.  
If that can apply TLS, good.  What is the simplest package that can 
provide this?

Thanks,              ... Peter E.
                               




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

Back to linux.debian.user | Previous | Next — Next in thread | Find similar | Unroll thread

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