Google host means that the host that squid couldn't connect ie :
>>> connection on conn2195 local=216.58.198.67:443
>>> remote=192.168.189.94:41724 FD 104 flags=33: 0x55cf6a6debe0*1
>>>
216.58.198.67:443
The issue can be teste against this host.( the above)
There is an issue with ssl bump and
Hello squid users.
I have configured squid's option SSL_ports to include
smtps(465) imaps(993) pop3s(995) nntps(563)
What requirements are needed for smtps imaps pop3s nntps client programs
to tunnel thru squid proxy?
--
kevin
___
squid-users
On 16/02/21 4:16 am, Yanko Hernández Álvarez wrote:
> On Fri, Feb 12, 2021 at 5:36 PM Amos Jeffries wrote:
>>
>> On 13/02/21 9:29 am, Yanko Hernández Álvarez wrote:
>>> Hello :-)
>>>
>>> How is it possible that some user tried to log in with the correct
>>> password and squid response was a
Hello,
most probably the problem is on the server side:
openssl s_client -connect www.p-mat.sk:443 -tls1
CONNECTED(0003)
depth=2 O = Digital Signature Trust Co., CN = DST Root CA X3
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = R3
verify return:1
depth=0 CN = p-mat.sk
verify
On 2/15/21 6:32 AM, Eliezer Croitoru wrote:
> Where exactly do you see Host Header Forgery in my last email?
Your last email says "google hosts". The previous email from you (in the
same thread) said "Most of the issues I see are related to Host header
forgery detection" and then named "google
Hello,
I am struggling with "ERROR: negotiating TLS on FD 53:
error:141A318A:SSL routines:tls_process_ske_dhe:dh key too small
(1/-1/0)" error when ssl bumping.
I cannot find out where the problem liesand why is the key too small.
I regenerated my dhparams with openssl dhparam -outform PEM -out
Hey Alex,
Where exactly do you see Host Header Forgery in my last email?
Eliezer
* I wrote my own proxy for now.
Eliezer Croitoru
Tech Support
Mobile: +972-5-28704261
Email: ngtech1...@gmail.com
Zoom: Coming soon
-Original Message-
From: Alex Rousskov
Sent: Thursday, February
