From: David Kastrup <dak@gnu.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Needed for the release
Date: Thu, 16 Jun 2005 09:53:05 +0200 [thread overview]
Message-ID: <85aclq4u1q.fsf@lola.goethe.zz> (raw)
In-Reply-To: <20050616.132230.213364433.jet@gyve.org> (Masatake YAMATO's message of "Thu, 16 Jun 2005 13:22:30 +0900 (JST)")
Masatake YAMATO <jet@gyve.org> writes:
> Sorry to be late.
>
>> 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.
>
> Could you tell me the kernel version or the OS version?
>
> I'm using Fedora core 1 and Fedora core 3.
> I cannot reproduce the problem on the platforms.
It was introduced some time after Fedora core 3 in their development
sources. I switched to Ubuntu a short time after that. It is
possible that the feature did not make it switched on by default into
the final FC4 release, but I can't tell since I stopped updating it
after that.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2005-06-16 7:53 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
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 [this message]
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=85aclq4u1q.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.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).