Date: Thu, 9 Sep 2010 16:33:57 +0200 From: Kurt Jaeger <pi@opsec.eu> To: Gareth de Vaux <bsd@lordcow.org> Cc: stable@freebsd.org Subject: Re: MSIX failure Message-ID: <20100909143357.GG34314@home.opsec.eu> In-Reply-To: <20100909142928.GA25877@lordcow.org> References: <AANLkTikdGGgpGhy4MJF_K-ttLvjQOBj%2BAb5r-a2uhJ_Y@mail.gmail.com> <20100908094050.GA73841@lordcow.org> <AANLkTikvd09fw3fUhxsXDhMoWE-kvMoPjXPSTfzYY73T@mail.gmail.com> <20100909125400.GA18723@lordcow.org> <20100909131340.GA75829@icarus.home.lan> <20100909132519.GB21535@lordcow.org> <20100909140224.GA76889@icarus.home.lan> <20100909142226.GA25370@lordcow.org> <20100909142455.GA77677@icarus.home.lan> <20100909142928.GA25877@lordcow.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! > > Is this within a jail or something else along those lines? I can't > > reproduce the problem otherwise. Frustrating! Someone else on the list > > might have ideas as to what could cause this. > > Nope, this's a normal host. I've got securelevel on 1, but doubt that > would affect this? I assume it affects it. http://www.freebsd.org/doc/en/books/faq/security.html#SECURELEVEL Basically, when the securelevel is positive, the kernel restricts certain tasks; not even the superuser (i.e., root) is allowed to do them. There: # Write to kernel memory via /dev/mem and /dev/kmem. So I assume it also restricts reading /dev/kmem ? -- pi@opsec.eu +49 171 3101372 10 years to go !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100909143357.GG34314>