From: "Kirill A. Shutemov" <k.shutemov@velesys.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU Various Vulnerabilities
Date: Thu, 3 May 2007 11:14:54 +0300 [thread overview]
Message-ID: <20070503081454.GA17577@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0705021821200.2810@linmac.oyster.ru>
[-- Attachment #1: Type: text/plain, Size: 443 bytes --]
On [Wed, 02.05.2007 18:21], malc wrote:
> On Wed, 2 May 2007, Kirill A. Shutemov wrote:
>
> >http://secunia.com/advisories/25073/
> >
> >Any comments ?
>
> AAM - http://lists.gnu.org/archive/html/qemu-devel/2007-04/msg00650.html
> SB16/DMA - in attachment
Thanks. Other Vulnerabilities?
--
Regards, Kirill A. Shutemov
+ Belarus, Minsk
+ Velesys LLC, http://www.velesys.com/
+ ALT Linux Team, http://www.altlinux.com/
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-05-03 8:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 12:51 [Qemu-devel] QEMU Various Vulnerabilities Kirill A. Shutemov
2007-05-02 14:22 ` malc
2007-05-03 8:14 ` Kirill A. Shutemov [this message]
2007-05-03 19:22 ` Juergen Lock
2007-05-03 21:13 ` malc
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=20070503081454.GA17577@localhost.localdomain \
--to=k.shutemov@velesys.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).