Re: [squid-users] SSL/SSH/SFTP/FTPS to alternate ports

2014-10-12 Thread Sergey Tsabolov ( aka linuxman )
Hello, About ports for SSH I think the best way add SSH server running on or ports and not need to change the https 443 ports with ssh ports. Is the simple way and not need the change the https way. On 12/10/2014 02:48 πμ, Timothy Spear wrote: Hello, Here is the issue: I can proxy t

Re: [squid-users] SSL/SSH/SFTP/FTPS to alternate ports

2014-10-12 Thread Timothy Spear
Here is the access log. I should have included it in the original post. This is accessing a test machine I setup to hit SSH on 22 and 443. I can also hit HTTPS on multiple other ports. 1413125068.706 87 10.110.98.21 TCP_MISS/503 0 CONNECT XXX..com:22 - HIER_NONE/- - 1413125086.496 806

Re: [squid-users] SSL/SSH/SFTP/FTPS to alternate ports

2014-10-12 Thread Timothy Spear
Sergey, I do not control the destination ports, my servers communicate to servers at other companies. In some cases, there are SFTP communications I must perform on 443. Tim On Oct 12, 2014, at 8:08 AM, Sergey Tsabolov ( aka linuxman ) wrote: > Hello, > About ports for SSH I think the best

Re: [squid-users] SSL/SSH/SFTP/FTPS to alternate ports

2014-10-12 Thread crazy world
Do you have the log for the connection when you can't access? Other than 22 and 443 as you said. Thanks, -B Subject: Re: [squid-users] SSL/SSH/SFTP/FTPS to alternate ports From: n61...@gmail.com Date: Sun, 12 Oct 2014 10:49:05 -0400 CC: n61...@gmail.com; squid-users@lists.squid-cache.org To: cr

Re: [squid-users] SSL/SSH/SFTP/FTPS to alternate ports

2014-10-12 Thread Timothy Spear
B, I was going to attach the logs, but I now feel like an idiot. :D The jump box I am running Squid on, currently only allows 80 and 443 outbound. I recalled this when I went to scp the log files and the connection was refused I detest overlooking things like this. Sometimes, you really need

Re: [squid-users] SSL/SSH/SFTP/FTPS to alternate ports

2014-10-12 Thread Ron Wheeler
On 12/10/2014 11:33 AM, Timothy Spear wrote: B, I was going to attach the logs, but I now feel like an idiot. :D The jump box I am running Squid on, currently only allows 80 and 443 outbound. I recalled this when I went to scp the log files and the connection was refused I detest overlooki

[squid-users] Forwarding loop again

2014-10-12 Thread orientalsniper
Hello all, I'm having forwarding loops again, this time however it's different. With Squid alone it works, however if I use it with Dansguardian, I'm getting forwarding loops. This is the most relevant message from the logs: X-Forwarded-For: 10.1.0.3, 10.2.0.4 10.1.0.3 is the client requesting the

[squid-users] cygwin (running on Win2K3 and 2K8) + squid 3.3.3 + negotiate_kerberos_auth

2014-10-12 Thread Mirza Dedic
I've got a Squid 3.3.3 running on Windows 2003 (and 2008) box via CYGWIN, works with the basic config. My next step is to put in some authentication in place, in this case Kerberos using.. auth_param negotiate program /usr/lib/squid/negotiate_kerberos_auth -d -s HTTP/vis-squid.VAND1.OPPY.CO

Re: [squid-users] blockVirgin Works for CONNECT but Custom Response does not work

2014-10-12 Thread Jatin Bhasin
Hi Alex, I think I have found the reason that why the annotation from eCap adapter NOT being passed to NoteData.cc. But I still need your suggestion to fix this. So here is my analysis: 1) In src/acl/NoteData.cc function ACLNoteData::match(HttpRequest *request) if (request->notes != NULL &&

Re: [squid-users] Forwarding loop again

2014-10-12 Thread Amos Jeffries
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 13/10/2014 11:28 a.m., orientalsniper wrote: > Hello all, I'm having forwarding loops again, this time however > it's different. With Squid alone it works, however if I use it > with Dansguardian, I'm getting forwarding loops. > You seem to have f

Re: [squid-users] cygwin (running on Win2K3 and 2K8) + squid 3.3.3 + negotiate_kerberos_auth

2014-10-12 Thread Amos Jeffries
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks for the details on where to find Cygwin builds of Squid. I have updated our wiki entry for Windows to include that. As for the mskutil problems, you should not have to be patching at all. Please contact the mskutil developers / support about th

Re: [squid-users] TCP_DENIED/403 after Upgrading from 3.4.4 to 3.4.7 (ssl_bump enabled)

2014-10-12 Thread Tom Tom
Hi Does anyone have some ideas/hints concerning this problem? Many thanks. Tom On Wed, Oct 8, 2014 at 8:16 PM, Tom Tom wrote: > I still get a TCP_DENIED/403 while accessing a bumped https-site after > putting a "-" or even "^root$" in /etc/squid/DENY_USERS_LOCAL. The > cache.log with "debug_opt

Re: [squid-users] TCP_DENIED/403 after Upgrading from 3.4.4 to 3.4.7 (ssl_bump enabled)

2014-10-12 Thread Amos Jeffries
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 13/10/2014 6:26 p.m., Tom Tom wrote: > Hi > > Does anyone have some ideas/hints concerning this problem? I am looking into it and fairly sure its a bug in how the ACL result is returning 1 == ALLOWED. But that was done to solve another bug in auth