Best settings to filter https ?

[JJoe]

(Oct. 24, 2009 04:15 PM)leecovuk Wrote:  I've just looked more closely and can see there is more than one ssl related header filter in Sidki's config, so to clarify then, assuming at this stage I'm not using or have merged in your YLogin filters;

The filter I was originally enquiring about / noticed was:
! |||||||||||| 2.2 Use Half-SSL 5.01.12 [jjoe] (o.2) (Out)
under Header Filters, which is off by default.
Are you saying that enabling that just achieves the same result as enabling
<*>: Half-SSL 8.03.06 (cch! multi) [sd jjoe] (d.2)
and
JS CSS: Half-SSL 7.11.02 (cch! multi) [jjoe sd] (d.2)
under Web Page filters, which are both enabled by default.

No.
The set uses a variable to control all the Half-SSL related processes.
The header filter '2.2 Use Half-SSL' can create that variable.
'<*>: Half-SSL' and 'JS CSS: Half-SSL' are on by default but require the variable to work.
So, '2.2 Use Half-SSL' is a 'trigger' or 'toggle' filter that starts the Half-SSL process.

The user only enables/disables one filter instead of 4 or more.
Seemed like a user friendly feature.

(Oct. 24, 2009 04:15 PM)leecovuk Wrote:  Then, regarding how to set up the browser proxy settings;
should we/are you suggesting, JJoe, we should route both http and https through localhost/127.0.0.1:[Prox's listening port]?

I do. I route http and https through 127.0.0.1:8080.
I see warnings from the browser about the Proxomitron and site.
I see warnings and errors from the Proxomitron.

I know somebody who only filters Half-SSLed pages.
He sees warnings from the browser about the site.
He see warnings and errors from the Proxomitron.
He sees less warnings and errors and more unwanted content than I do.
He does more https than I do and has https bookmarks.

(Oct. 24, 2009 04:15 PM)leecovuk Wrote:  Then finally, if I/we use your YLogin filters, just do the config merge and we're done?
(By 'done' I mean theoretically set up for filtering all secure pages/sites, along with using your YLogin filters, with the lowest probability of getting certificate security warnings)

YLogin requires a choice, https or http://https.

Code:

# Remove one of the # from the two lines below.

#$SET(YLaction=https://)(^)
#$SET(YLaction=http://https.)(^)

#  Removing the # from the #$SET(YLaction=https://)(^) line above
#   provides a secure (https) connection between the browser and the
#   Proxomitron. The browser may complain about the Proxomitron.
#  Removing the # from the #$SET(YLaction=http://https.)(^) line above
#   provides a 'HalfSSL' connection. The browser will not see the
#   secure (https) connection and should not complain about the
#   Proxomitron.
(^$TST(YLaction=?*))$ALERT(YLaction not set!\r\nEdit line 13 or 14 of YLogin.txt)

So to filter all secure pages/sites, use YLogin, and see the least alerts and warnings:
Route both http and https through localhost/127.0.0.1:[Prox's listening port]
Enable the header filter ! |||||||||||| 2.2 Use Half-SSL 5.01.12 [jjoe] (o.2) (Out) or equivalent.
Add YLogin and edit line 14 of YLogin.txt.

I think, Sidki's Half-SSL option will hide the https connection regardless.

Again tho, no mistakes may require a direct connection with https and http.

HTH