Windows and non-page memory - WAS: Minister promises that Part III is coming

John Brazier ukcrypto at chiark.greenend.org.uk
Wed, 17 May 2006 22:49:16 +0100 

This is a multi-part message in MIME format.

------=_NextPart_000_03B4_01C67A04.20546EE0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Perhaps so, but am I completely wrong in my insistence that what has been
touted as a definitive Windows 32 memory architecture paper seems to be
inaccurate, and thus MS are wrong to tout it as accurate?
 
Analagously, if someone finds a set of AES keys - say a few hundred - that
are incredibly weak, we'll all be satisfied with the statement that 'well,
it's not very many, and they are obscure anyway' ?
 
JB

  _____  

From: ukcrypto-admin@chiark.greenend.org.uk
[mailto:ukcrypto-admin@chiark.greenend.org.uk] On Behalf Of David Biggins
Sent: 17 May 2006 09:47
To: ukcrypto@chiark.greenend.org.uk
Subject: Windows and non-page memory - WAS: Minister promises that Part III
is coming



The documentation on memory management refer in general to the Win32
functions that are accessible from Ring3 Application-level code.

 

The only functions that allow allocation of non-paged pool are the ones like
ExAllocatePoolWithTag, which are not Ring3 API functions, but device driver
functions.

 

These are documented separately, and not callable by Ring3 application code.

 

Dave.

 

 


------=_NextPart_000_03B4_01C67A04.20546EE0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2873" name=3DGENERATOR>
<STYLE>@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal
}
SPAN.EmailStyle18 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US=20
style=3D"WORD-WRAP: break-word; khtml-nbsp-mode: space; =
khtml-line-break: after-white-space"=20
vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D062244421-17052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Perhaps so, but am I completely wrong in my =
insistence that=20
what has been touted as a definitive Windows 32 memory architecture =
paper seems=20
to be inaccurate, and thus MS are wrong to tout it as=20
accurate?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D062244421-17052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D062244421-17052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Analagously, if someone finds a set of AES keys =
- say a few=20
hundred - that are incredibly weak, we'll all be satisfied with the =
statement=20
that 'well, it's not very many, and they are obscure anyway'=20
?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D062244421-17052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D062244421-17052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>JB</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> =
ukcrypto-admin@chiark.greenend.org.uk=20
[mailto:ukcrypto-admin@chiark.greenend.org.uk] <B>On Behalf Of </B>David =

Biggins<BR><B>Sent:</B> 17 May 2006 09:47<BR><B>To:</B>=20
ukcrypto@chiark.greenend.org.uk<BR><B>Subject:</B> Windows and non-page =
memory -=20
WAS: Minister promises that Part III is coming<BR></FONT><BR></DIV>
<DIV></DIV>
<P class=3DMsoNormal dir=3Dltr><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><SPAN=20
class=3D390395716-16052006><SPAN =
class=3D426543608-17052006>The&nbsp;documentation=20
on memory management refer in general to the Win32 functions that are =
accessible=20
from Ring3 Application-level code.</SPAN></SPAN></SPAN></P>
<P class=3DMsoNormal dir=3Dltr><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><SPAN=20
class=3D390395716-16052006><SPAN=20
class=3D426543608-17052006></SPAN></SPAN></SPAN>&nbsp;</P>
<P class=3DMsoNormal dir=3Dltr><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><SPAN=20
class=3D390395716-16052006><SPAN class=3D426543608-17052006>The only =
functions that=20
allow allocation of non-paged pool are the ones like <FONT =
face=3D"Courier New"=20
color=3D#000000 size=3D3><FONT face=3DCourier color=3D#000080=20
size=3D2>ExAllocatePoolWithTag,</FONT><FONT face=3DArial color=3D#000080 =
size=3D2> which=20
are not Ring3 API functions, but device driver=20
functions.</FONT></FONT></SPAN></SPAN></SPAN></P>
<P class=3DMsoNormal dir=3Dltr><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><SPAN=20
class=3D390395716-16052006><SPAN class=3D426543608-17052006><FONT =
face=3D"Courier New"=20
color=3D#000000 size=3D3><FONT face=3DArial color=3D#000080=20
size=3D2></FONT></FONT></SPAN></SPAN></SPAN>&nbsp;</P>
<P class=3DMsoNormal dir=3Dltr><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><SPAN=20
class=3D390395716-16052006><SPAN class=3D426543608-17052006><FONT =
face=3D"Courier New"=20
color=3D#000000 size=3D3><FONT face=3DArial color=3D#000080 =
size=3D2>These=20
are&nbsp;documented separately, and not callable by Ring3 application=20
code.</FONT></FONT></SPAN></SPAN></SPAN></P>
<P class=3DMsoNormal dir=3Dltr><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><SPAN=20
class=3D390395716-16052006><SPAN=20
class=3D426543608-17052006></SPAN></SPAN></SPAN>&nbsp;</P>
<P class=3DMsoNormal dir=3Dltr><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><SPAN=20
class=3D390395716-16052006><SPAN=20
class=3D426543608-17052006>Dave.</SPAN></SPAN></SPAN></P>
<P class=3DMsoNormal dir=3Dltr><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><SPAN=20
class=3D390395716-16052006><SPAN=20
class=3D426543608-17052006></SPAN></SPAN></SPAN>&nbsp;</P>
<P class=3DMsoNormal dir=3Dltr><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><SPAN=20
class=3D390395716-16052006><SPAN=20
class=3D426543608-17052006></SPAN></SPAN></SPAN>&nbsp;</P></BODY></HTML>

------=_NextPart_000_03B4_01C67A04.20546EE0--