On Sun, Apr 10, 2011 at 12:19:32PM -0400, J. Bruce Fields wrote:
> On Sun, Mar 27, 2011 at 03:09:37PM -0600, dann frazier wrote:
> > Mi,
> > We were wondering if you could help us define the security impact (if
> > any) of your fix for nfsd4_op_flags, commit 5ece3ca upstream. If it
> > does have a
On Sun, Mar 27, 2011 at 03:09:37PM -0600, dann frazier wrote:
> Mi,
> We were wondering if you could help us define the security impact (if
> any) of your fix for nfsd4_op_flags, commit 5ece3ca upstream. If it
> does have a security impact, we can work with MITRE to get a CVE ID
> assigned.
Apolo
On Mon, 2011-03-28 at 17:36 +0800, Mi Jinlong wrote:
>
> dann frazier:
> > Mi,
> > We were wondering if you could help us define the security impact (if
> > any) of your fix for nfsd4_op_flags, commit 5ece3ca upstream. If it
> > does have a security impact, we can work with MITRE to get a CVE ID
dann frazier:
> Mi,
> We were wondering if you could help us define the security impact (if
> any) of your fix for nfsd4_op_flags, commit 5ece3ca upstream. If it
> does have a security impact, we can work with MITRE to get a CVE ID
> assigned.
>
The problem just affect NFS4.1, I can't meet some
Mi,
We were wondering if you could help us define the security impact (if
any) of your fix for nfsd4_op_flags, commit 5ece3ca upstream. If it
does have a security impact, we can work with MITRE to get a CVE ID
assigned.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a s
5 matches
Mail list logo