From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: Keir Fraser <keir@xensource.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] Fix CVE-2007-1320, CVE-2007-1321 , CVE-2007-1322, CVE-2007-1323 and CVE-2007-1366
Date: Tue, 1 May 2007 21:56:03 +0300 [thread overview]
Message-ID: <200705012156.06210.caglar@pardus.org.tr> (raw)
In-Reply-To: <C25D10F4.E361%keir@xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 1739 bytes --]
01 May 2007 Sal tarihinde, Keir Fraser şunları yazmıştı:
> On 1/5/07 15:15, "S.Çağlar Onur" <caglar@pardus.org.tr> wrote:
> > P.S: while i get your attention :) is it possible to push both 3.0.4 and
> > 3.0.5 CVEish patches into trees, we have 15 pending patch in our package
> > which submitted to list and xen-bugzilla long before?
>
> I don't believe I have any outstanding patches for 3.0.5. Please send any
> that you think are critical. There's no plan to do a 3.0.4-2 in the
> immediate future.
Hmm i think there are some :)
I have following patches on top of current 3.0.5-testing tree, this series
contains all released CVE's from 2.6.18 to up until now (linus's current
git), only CVE-2007-2242 ( IPV6: Disallow RH0 by default.) is missing...
[caglar@zangetsu][~/buildbox/xen/linux-2.6.18/patches]> quilt series
linux-2.6-xen.patch <-- "make mkpatches" of current tree
CVE-2005-4352.patch
CVE-2006-4814.patch
CVE-2006-5619.patch
CVE-2006-5749.patch
CVE-2006-5751.patch
CVE-2006-5753.patch
CVE-2006-5757-CVE-2006-6060.patch
CVE-2006-5823.patch
CVE-2006-6053.patch
CVE-2006-6054.patch
CVE-2006-6056.patch
CVE-2006-6106.patch
CVE-2006-6333.patch
CVE-2007-0005.patch
CVE-2007-0006.patch
CVE-2007-0772.patch
CVE-2007-0958.patch
CVE-2007-1000.patch
CVE-2007-1217.patch
CVE-2007-1388.patch
CVE-2007-1497.patch
CVE-2007-1592.patch
CVE-2007-1861.patch
CVE-2007-2172.patch
Instead of submitting all these patches to mailing list i just upload to [1]
[1] http://cekirdek.pardus.org.tr/~caglar/patches/
Cheers
--
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/
Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2007-05-01 18:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 13:29 [PATCH] Fix CVE-2007-1320, CVE-2007-1321 , CVE-2007-1322, CVE-2007-1323 and CVE-2007-1366 S.Çağlar Onur
2007-05-01 13:44 ` Keir Fraser
2007-05-01 14:15 ` S.Çağlar Onur
2007-05-01 14:44 ` Keir Fraser
2007-05-01 18:56 ` S.Çağlar Onur [this message]
2007-05-01 20:12 ` Keir Fraser
2007-05-01 20:46 ` S.Çağlar Onur
2007-05-01 23:04 ` S.Çağlar Onur
2007-05-01 18:14 ` Christian Limpach
2007-05-01 19:21 ` S.Çağlar Onur
2007-09-25 22:45 ` Robert Buchholz
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=200705012156.06210.caglar@pardus.org.tr \
--to=caglar@pardus.org.tr \
--cc=keir@xensource.com \
--cc=xen-devel@lists.xensource.com \
/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.