linux-kernel - Re: Dynamic linking in the kernel

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] [day] [month] [year] [list]

Date:	Sun, 21 Feb 2010 22:21:22 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	weigelt@...ux.de
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Dynamic linking in the kernel

From: Enrico Weigelt <weigelt@...ux.de>
Date: Mon, 22 Feb 2010 06:43:27 +0100

> David Miller wrote:
> 
>> In order to implement this the kernel would have to also save a copy
>> of all pieces of the processes's environment and compare all of the
>> environment variable settings on every execution.  This would be
>> needed to handle things like LD_PRELOAD, LD_LIBRARY_PATH, and LD_DEBUG
>> as just three examples.
> 
> Fairly simple:
> 
> * parsed per-module data is cached by its inode id
> * cached data that can be influenced by LD_PRELOAD/LD_LIBRARY_PATH
>   (eg. mapping of library names to actual filenames or inode-id's)
>   is cached on hash of these variables plus inode-id

Feel free to implement this and show us the numbers.

I am not as confident as you :-)
--
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/