Michael Tokarev m...@tls.msk.ru writes:
I haven't noticed this email - which is almost a month old now - until today.
So replying now...
30.07.2014 21:43, Aneesh Kumar K.V wrote:
Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com writes:
Michael Tokarev m...@tls.msk.ru writes:
Apparently
I haven't noticed this email - which is almost a month old now - until today.
So replying now...
30.07.2014 21:43, Aneesh Kumar K.V wrote:
Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com writes:
Michael Tokarev m...@tls.msk.ru writes:
Apparently the the mapped-* security models results in
Apparently the the mapped-* security models results in a raw bytes
being dumped to host without any architecture normalization (in
host byte order). This may even lead to security issues in guest
when the same files are served from another host for example.
This bug has been initially submitted
Michael Tokarev m...@tls.msk.ru writes:
Apparently the the mapped-* security models results in a raw bytes
being dumped to host without any architecture normalization (in
host byte order). This may even lead to security issues in guest
when the same files are served from another host for
Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com writes:
Michael Tokarev m...@tls.msk.ru writes:
Apparently the the mapped-* security models results in a raw bytes
being dumped to host without any architecture normalization (in
host byte order). This may even lead to security issues in
