From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Executable stacks
Date: Mon, 02 Jan 2006 23:08:19 +0100 [thread overview]
Message-ID: <87irt2i8q4.fsf@xs4all.nl> (raw)
In-Reply-To: <43B9A209.1080601@gentoo.org> (Petteri Räty's message of "Mon, 02 Jan 2006 23:58:33 +0200")
Petteri Räty <betelgeuse@gentoo.org> writes:
> I am not an expert in this area. Our tools just automatically warn you
> about executable stacks so I reported it here.
Sure :)
> "Some operating systems and GNU/Linux distributions don't have an
> executable stack for security reasons. Sometimes it does not have an
> executable stack by default, but the executable stack can be enabled
> again by tagging the binary."
>
> Better wording would be that some distributions don't allow executable
> stacks for security reasons and I did this modification to the wiki.
I noticed that, we were editing the same page simultaneously. I hope
everything went right.
> "Another solution is enabling the executable stack again by calling some
> function."
>
> This is really vague. I think this should be dropped unless you can
> specify the name of the function but I leave the decision to you. I also
> had trouble understanding some of the stuff on the page but then again I
> am not an expert in these issues.
I changed the wording a bit. I hope it is clearer now. English is
not my native language and suggestions for improvements are more than
welcome. :-)
Thanks,
Marco
prev parent reply other threads:[~2006-01-02 22:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-31 17:05 Executable stacks Petteri Räty
2005-12-31 17:47 ` Marco Gerards
2006-01-02 20:59 ` Olaf Hering
2006-01-02 21:58 ` Petteri Räty
2006-01-02 22:08 ` Marco Gerards [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87irt2i8q4.fsf@xs4all.nl \
--to=mgerards@xs4all.nl \
--cc=grub-devel@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.