linux-kernel - Re: [PATCH] Undo some of the pseudo-security madness

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: <87mz4bvp3x.wl@betelheise.deep.net>
Date:	Mon, 22 Jan 2007 04:15:14 +0300
From:	Samium Gromoff <_deepfire@...lingofgreen.ru>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	Samium Gromoff <_deepfire@...lingofgreen.ru>,
	linux-kernel@...r.kernel.org, David Wagner <daw@...berkeley.edu>
Subject: Re: [PATCH] Undo some of the pseudo-security madness

At Mon, 22 Jan 2007 01:35:46 +0100,
Arjan van de Ven wrote:
> > the core of the problem are the cores which are customarily
> > dumped by lisps during the environment generation (or modification) stage,
> > and then mapped back, every time the environment is invoked.
> 
> > 
> > at the current step of evolution, those core files are not relocatable
> > in certain natively compiling lisp systems.
> 
> nor will they work if the sysadmin applies a security update and glibc
> or another library changes one page in size. Or changes the stack rlimit
> or .. or ..

At this point i should just step down and declare incompetence --
SBCL works around shlib size variance, somehow, and /yet/ the whole
turn-off-AS-randomisation-and-reexec-self thing is still present in the source,
for some reason.

I should let more competent people (read, the actual SBCL developers)
take the way from now...

(I could have digged the source myself, but it is way too late today.
However, if nobody from the development team answers by tomorrow`s evening (gmt+3),
i should see into the thing for myself).

> -- 
> if you want to mail me at work (you don't), use arjan (at) linux.intel.com
> Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org

regards, Samium Gromoff
-
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/