From: jhd <jan.h.d@swipnet.se>
Cc: Masatake YAMATO <jet@gyve.org>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Needed for the release
Date: Sat, 11 Jun 2005 07:50:05 +0200 [thread overview]
Message-ID: <AEB65B61-10F8-4219-81E5-F584F3A36227@swipnet.se> (raw)
In-Reply-To: <85is0lokfm.fsf@lola.goethe.zz>
11 jun 2005 kl. 01.34 skrev David Kastrup:
> Richard Stallman <rms@gnu.org> writes:
>
>
>> What I remember is that Red Hat enables a feature in Linux that (I
>> believe) uses the address space differently. unexelf.c doesn't
>> handle
>> it right.
>>
>> I don't remember the name of the feature, but I'm sure other people
>> on this list remember the name.
>>
>
> exec_shield is one such feature, and newer kernels use something like,
> uh, /proc/sys/vm/randomize_... (I don't remember the particular name
> right now and don't have a Fedora active). The latter loaded
> executables' memory segments into randomized locations to make buffer
> overflow attacks less predictable.
>
> exec_shield could be gotten around with using
> setarch i386 make
> and configure does that already IIRC. But the address space
> randomization was prohibiting the dumping even with the setarch
> command.
There is some info in etc/PROBLEMS, and some information here:
http://www.redhat.com/f/pdf/rhel/WHP0006US_Execshield.pdf
http://people.redhat.com/drepper/nonselsec.pdf
And if you search for Exec-shield here:
http://www.redhat.com/docs/manuals/enterprise/RHEL-3-Manual/release-
notes/as-x86/RELEASE-NOTES-U3-x86-en.html
They don't describe the new randomizing features though.
Jan D.
next prev parent reply other threads:[~2005-06-11 5:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 0:14 Needed for the release Richard Stallman
2005-06-10 10:40 ` Masatake YAMATO
2005-06-10 22:37 ` Richard Stallman
2005-06-10 23:34 ` David Kastrup
2005-06-11 5:50 ` jhd [this message]
2005-06-11 23:17 ` Richard Stallman
2005-06-16 4:29 ` Masatake YAMATO
2005-06-16 18:56 ` Michael Welsh Duggan
2005-06-16 4:22 ` Masatake YAMATO
2005-06-16 4:44 ` Masatake YAMATO
2005-06-16 7:53 ` David Kastrup
2005-06-16 15:01 ` jhd
2005-06-17 4:38 ` Richard Stallman
2005-06-16 16:48 ` Dan Nicolaescu
2005-06-16 16:52 ` Masatake YAMATO
2005-06-17 1:00 ` James Cloos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AEB65B61-10F8-4219-81E5-F584F3A36227@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=emacs-devel@gnu.org \
--cc=jet@gyve.org \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).