Hi Andre,
I did not receive your new reply, but I did find it in the mailing
list archives in time to download the logs. Thank you for sharing them!
FWIW, you may want to CC me in future emails (but I do not know whether
that will help).
Something really strange is going on. Squid
On 4/18/24 2:46 PM, Albert Shih wrote:
So what I'm trying to do is to use ACL according to the user who make
the ssh connection, I don't want «another» authentication.
About the only thing that comes to mind is RFC 931 (?) ident (might be
okay on the same system) or something that matches the
On 2024-04-18 04:13, Rauch, Mario wrote:
We have created a DER version of the PEM certificate which Squid uses
and imported this into client certificate store using script like this:
certmgr /add DN_SIGNATOR_CA.der /r localMachine /s root
DN_SIGNATOR_CA.der is the self signed certificate
Le 18/04/2024 à 18:13:41+0100, Francesco Chemolli a écrit
Hi,
> Sure, of course. It will work just as normal.
> The only type of ACLs that would need to be considered is source-based
Ok, thanks, but just to be sure, because re-reading myself I was not very clear
about my question.
So what I'm
Sure, of course. It will work just as normal.
The only type of ACLs that would need to be considered is source-based
@mobile
On Thu, 18 Apr 2024 at 18:09, Albert Shih wrote:
> Hi everyone
>
> If a user use a ssh tunnel to access to squid like
>
> ssh -L 3128:squid_server:3128 ssh-portal
>
Hi everyone
If a user use a ssh tunnel to access to squid like
ssh -L 3128:squid_server:3128 ssh-portal
then configure his browser to use 127.0.0.1:3128 to access the squid proxy
is they are a way to use «acl by user» in the squid configuration ?
Thanks
--
Albert SHIH 嶺
France
Heure
Hello,
We have created a DER version of the PEM certificate which Squid uses and
imported this into client certificate store using script like this:
certmgr /add DN_SIGNATOR_CA.der /r localMachine /s root
DN_SIGNATOR_CA.der is the self signed certificate
Maybe there must be some additional or
