@aGeekhere said in Squid's new SslBump Peek and Splice for https caching?:
maybe QoS3
If the server, some proxy device and the client (browser) all install the needed modules ....
It would become one hack of a standard before such a thing gets implemented.
Typically, this will be needing 3 admins implementing software on their side,as end users often don't know what a 'proxy' is.
@High_Voltage said in Squid's new SslBump Peek and Splice for https caching?:
to scan with clamav the data in the ssl transmission, NOT just to cache it.
That would be my main reason to centralize (== cache ?) downstream data. As far as I know, only 'mails' are handled like this these days. That is, if you run your own mail server (like running some proxy). This takes down a huge security issue already.
Btw : You're happy, you control all your devices.
Those you don't : they go into the non trusted network. When these need access to local trusted resources like NAS : it will be a case by case consideration.