linux-kernel - Re: [PATCH] Kconfig: Make config Filter access to /dev/mem default y

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LRH.2.00.1004151233010.28179@twin.jikos.cz>
Date:	Thu, 15 Apr 2010 12:43:09 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Michal Svoboda <michal.svoboda@...nts.felk.cvut.cz>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Kconfig: Make config Filter access to /dev/mem default
 y

On Thu, 15 Apr 2010, Michal Svoboda wrote:

> > Have you ever successfully attack by this way? If CONFIG_STRICT_DEVMEM
> > is not set, the /dev/mem access is filtered in pat code.
> 
> If that option doesn't add any protection, what's it good for?

Access to /dev/mem being filtered in PAT obviously applies only to x86. 

Architectures which don't do such filtering in their respective 
phys_mem_access_prot_allowed() still need this option.

-- 
Jiri Kosina
SUSE Labs, Novell Inc.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/