-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 .... and with bump we can see: https://i1.someimage.com/dG6Y2S9.png :) Secure, heh? :) 10.05.16 18:17, Matus UHLAR - fantomas пишет: >>> * alesironi <alesironi@xxxxxxxx>: >>> > The problem is that on Squid log file (ACCESS.LOG) the URL I see is >>> > similar to this: >>> > >>> > r10---sn-4g57knd7.googlevideo.com:443 > >> Ralf Hildebrandt <Ralf.Hildebrandt@xxxxxxxxxx> schrieb am Di., 10. Mai 2016 >> um 11:10 Uhr: >>> 443 = https = encrypted >>> >>> meaning: You cannot know. > > On 10.05.16 09:16, Bjoern Meier wrote: >> Wait. Since when track Squid data? Squid only track connections in the >> access.log (that's why it is called access.log). >> So, it is not importent if the data is encrypted, the connection data can't >> be encrypted. > > how did you get this? > The data _are_ encrypted. SQUID only sees host:port, nothing more. > >> Why shouldn't he see the URL in the access.log? > > because the URL is encrypted in the stream. > > the "s" in https stands for "secure", which means encrypted and > authenticated (at least with working certs). > > That means, the data are encrypted between browser and remote (youtube) server > so the others only see which host and port the connection goes to, but no > details like the URL. > > Once again, browser and server know the URL, but nobody between. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXMdVJAAoJENNXIZxhPexGKSkH/RcZMe4IHFc8Mqk/FGbpVqWY O4mGWQTXD5O5FwpTJaM3SA0laQ22RzmE8WVTIQ9SyBaH8sk6UmARnO2IVxKlMtm1 AvczwEUmll//L3kCrDKPkIdf7Ei5KAELGm/BJjRVgSK69m2KpUekVBUNgUWryCCw GFoduh3G9Y/wsMSwsSA++6zCGaYHiLy07tkv0r8peCqVyWJr4jNXgcpoxKewmsWI sKja8dIzWTcjZ7JzvHxmzBeT2GdJiayj8v5SMdzNE9wVYJlm8efMiLfj7U12P3fX XlmiNRrycGQcW4xsF0mOZB5fG2xeN0u02MhUyGsNNtcUH5c5UOW/0pSSzZiqEpQ= =bc0C -----END PGP SIGNATURE-----
Attachment:
0x613DEC46.asc
Description: application/pgp-keys
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
