From: Pavel Machek <pavel@suse.cz>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [BROKEN PATCH] syscalls leak data via registers?
Date: Thu, 7 Aug 2003 22:31:14 +0200 [thread overview]
Message-ID: <20030807203113.GA414@elf.ucw.cz> (raw)
In-Reply-To: <1060269116.20515.14.camel@ixodes.goop.org>
Hi!
> > I believe userspace depends on registers to be preserved over system
> > call, except for eax.
>
> That's what I was wondering. Does it? Is that a documented part of the
> syscall interface?
>
> > So what you found is not only security problem,
> > but also crasher bug.
>
> In these sense that it crashes userspace?
Yes. But I was probably wrong. gcc has to preserve callee saved
registers, and that should be enough.
Information leak looks very much real, through.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
prev parent reply other threads:[~2003-08-07 20:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-02 9:06 Jeremy Fitzhardinge
2003-08-07 10:30 ` Pavel Machek
2003-08-07 15:11 ` Jeremy Fitzhardinge
2003-08-07 15:55 ` Richard B. Johnson
2003-08-07 20:31 ` Pavel Machek [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=20030807203113.GA414@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®