public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Testing squid 4.0.23 - grsec denied kernel module auto-load of nf_conntrack_netlink by uid 23
Date: Mon, 22 Jan 2018 13:30:43 +0000	[thread overview]
Message-ID: <1516627843.3647.173.camel@ipfire.org> (raw)
In-Reply-To: <855ef12e-8ea6-3411-f2f7-755736697861@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1980 bytes --]

Okay, please keep an eye on squid 4 for us then. I am not following this very
closely and have no idea what will change in squid 4.

Best,
-Michael

On Sun, 2018-01-21 at 21:35 +0100, Matthias Fischer wrote:
> On 21.01.2018 19:57, Michael Tremer wrote:
> > Hello,
> > 
> > yes this is correct.
> > 
> > We don't allow an unprivileged user to load any kernel modules.
> 
> Ok, then my suspicion was right.
> 
> > What does squid need this for? Why are you playing around with squid 4?
> 
> 1. I don't know. 3.5.27 doesn't do this.
> 2. As I wrote - just to keep in touch with their development. Once in a
> while, 'squid 3' will be deprecated and I wanted to see what comes next,
> even though this may take a long time. Just being curious and the
> 'Devel' was somehow bored. ;-)
> 
> > You should be able to load the module first and then start squid.
> 
> I'm not that curious - this was for testing and for testing only.
> 
> Best,
> Matthias
> 
> > Best,
> > -Michael
> > 
> > On Sun, 2018-01-21 at 01:50 +0100, Matthias Fischer wrote:
> > > Hi,
> > > 
> > > Just to keep in touch, I tested 'squid 4.0.23' yesterday - it seemed to
> > > run fine at first. But after a while I took a closer look at the logs
> > > and discovered a bunch of kernel messages within a few hours and I don't
> > > know what exactly triggered these messages:
> > > 
> > > ...
> > > 132 Time(s): grsec: denied kernel module auto-load of
> > > nf_conntrack_netlink by uid 23
> > > ...
> > > 
> > > As far as I found out: "uid 23" => squid-user, and the new squid tried
> > > to 'autoload' a module which 'grsec' didn't like. Is this a correct
> > > interpretation and has anyone some useable clue how to avoid this?
> > > 
> > > Besides, after going back to '3.5.27' the messages didn't came back
> > > again. '4.0.22' didn't throw these messages, too. They changed something
> > > and I don't know what it is...
> > > 
> > > Thanks for all tips!
> > > 
> > > Best,
> > > Matthias
> > > 
> > > 
> 
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-01-22 13:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-21  0:50 Matthias Fischer
2018-01-21 18:57 ` Michael Tremer
2018-01-21 20:35   ` Matthias Fischer
2018-01-22 13:30     ` Michael Tremer [this message]
2018-03-10 11:22       ` Matthias Fischer
2018-03-11 10:20         ` Testing 'squid 4.0.24' (was: Re: Testing squid 4.0.23 - grsec denied kernel module auto-load of nf_conntrack_netlink by uid 23) Matthias Fischer
2018-03-11 13:05           ` Michael Tremer
2018-03-11 14:44             ` Testing 'squid 4.0.24' Matthias Fischer
2018-03-10  8:12   ` Testing squid 4.0.23 - grsec denied kernel module auto-load of nf_conntrack_netlink by uid 23 Matthias Fischer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1516627843.3647.173.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox