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

2019-07-18 Thread Reco
On Wed, Jul 17, 2019 at 02:32:28PM -0700, pe...@easthope.ca wrote: > > 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

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

2019-07-17 Thread D. R. Evans
pe...@easthope.ca wrote on 7/17/19 3:32 PM: > Jul 16 11:25:16 joule stunnel: LOG5[4]: Service [https] accepted connection > from 127.0.0.1:36140 > > * From: Reco recovery...@enotuniq.net > * Date: Wed, 17 Jul 2019 11:01:32 +0300 >> No, you're incorrect. A client application has connecte

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

2019-07-17 Thread peter
Jul 16 11:25:16 joule stunnel: LOG5[4]: Service [https] accepted connection from 127.0.0.1:36140 * From: Reco ... Peter E. -- https://en.wikibooks.org/wiki/Oberon Tel: +1 604 670 0140Bcc: peter at easthope. ca

Re: stunnel as transparent proxy.

2019-07-17 Thread Reco
Hi. On Tue, Jul 16, 2019 at 11:48:55AM -0700, pe...@easthope.ca wrote: > An attempt to open a page via HTTPS gives this report in the log. > Jul 16 11:25:16 joule stunnel: LOG5[4]: Service [https] accepted connection > from 127.0.0.1:36140 > Jul 16 11:25:16 joule stunnel: LOG3[4]: getsock

stunnel as transparent proxy.

2019-07-16 Thread peter
Hi, stunnel is installed here with this configuration. "server" has been substituted for the real name of course. peter@joule:~$ cat /etc/stunnel/stunnel.conf # joule:/etc/stunnel/stunnel.conf [pop3] client = yes accept = localhost:110 connect = server:995 [https] client = yes accept = localhost