[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lynx-dev] can't connect to

From: miro . rovis
Subject: Re: [Lynx-dev] can't connect to
Date: Mon, 16 Nov 2015 16:02:45 +0100
User-agent: Mutt/1.5.23+116 (55ea6e829b46) (2014-03-12)

On 151108-21:24+0000, Thorsten Glaser wrote:
> address@hidden dixit:
> >Nov  7 19:22:12 g0n kernel: [293205.943757] grsec:
>                                            ^^^^^
> Disable that.
Nope! Fixes lots of the holes that SELinux lovers like even Linus
introduced. My strong opinion.

> >(miro:U:/usr/bin/lynx) exec of /usr/bin/lynx (lynx
> > ) by /usr/bin/lynx[bash:12765]
Can I replace your quoting of my text above with the full quote of that
> >Nov  7 19:22:12 g0n kernel: [293205.943757] grsec:
> >(miro:U:/usr/bin/lynx) exec of /usr/bin/lynx (lynx
> > ) by /usr/bin/lynx[bash:12765]
> >uid/euid:1000/1000 gid/egid:1000/1000, parent /bin/bash[bash:19928]
> >uid/euid:1000/1000 gid/egid:1000/1000
> >
> This means lynx calls itself as subprocess (likely nsl fork)
> and is part of the normal operation.
Don't know what nsl fork means.

I haven't attained full command of how grsec reports things, but I think
that means only that executable being run regularly. No errors. How
grsec reports can be found aplenty on, esp. on my
very verbose topics in RBAC policy section.
> bye,
> //mirabilos
> -- 
But anyway, nice to meet you again! I remember I was able to get dbus
out from my Debian, thanx to you! And there is now a pretty strong
direction in among many users of Devuan to go without dbus. Some merit
surely from your previous work, as well.

I'll try and sort this issue as soon as I find time (maybe not soon ;-(
). Have to go now!


Miroslav Rovis
Zagreb, Croatia

Attachment: signature.asc
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]