<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Security Essentials on Windows Server</title>
	<atom:link href="http://migeel.sk/blog/2009/10/17/security-essentials-on-windows-server/feed/" rel="self" type="application/rss+xml" />
	<link>http://migeel.sk/blog/2009/10/17/security-essentials-on-windows-server/</link>
	<description>Windows development and other random stuff</description>
	<lastBuildDate>Fri, 30 Mar 2012 18:49:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Michal Strehovsky</title>
		<link>http://migeel.sk/blog/2009/10/17/security-essentials-on-windows-server/comment-page-1/#comment-153</link>
		<dc:creator>Michal Strehovsky</dc:creator>
		<pubDate>Thu, 12 Nov 2009 23:17:46 +0000</pubDate>
		<guid isPermaLink="false">http://migeel.sk/?p=98#comment-153</guid>
		<description>Pete,
if I remember correctly, there is a plugin for OllyDbg called Stealth64. Among other things, it fixes the incompatibility of OllyDbg with x64 versions of Windows. (Obviously, this will only work if the installer is 32bit. If it&#039;s 64bit, there is a debugger with similar UI to OllyDbg called fdbg, but not sure if that works.)

If that doesn&#039;t work, Microsoft&#039;s Debugging Tools for Windows are a safe bet. Setting a breakpoint on GetVersionEx and editing the OSVERSIONINFOEX field should be even more easy with them.</description>
		<content:encoded><![CDATA[<p>Pete,<br />
if I remember correctly, there is a plugin for OllyDbg called Stealth64. Among other things, it fixes the incompatibility of OllyDbg with x64 versions of Windows. (Obviously, this will only work if the installer is 32bit. If it&#8217;s 64bit, there is a debugger with similar UI to OllyDbg called fdbg, but not sure if that works.)</p>
<p>If that doesn&#8217;t work, Microsoft&#8217;s Debugging Tools for Windows are a safe bet. Setting a breakpoint on GetVersionEx and editing the OSVERSIONINFOEX field should be even more easy with them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pete Gomersall</title>
		<link>http://migeel.sk/blog/2009/10/17/security-essentials-on-windows-server/comment-page-1/#comment-152</link>
		<dc:creator>Pete Gomersall</dc:creator>
		<pubDate>Thu, 12 Nov 2009 22:58:50 +0000</pubDate>
		<guid isPermaLink="false">http://migeel.sk/?p=98#comment-152</guid>
		<description>Michael,
Do you know of any method with x64 version as I get a problem OllyDbg?
Pete</description>
		<content:encoded><![CDATA[<p>Michael,<br />
Do you know of any method with x64 version as I get a problem OllyDbg?<br />
Pete</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michal Strehovsky</title>
		<link>http://migeel.sk/blog/2009/10/17/security-essentials-on-windows-server/comment-page-1/#comment-146</link>
		<dc:creator>Michal Strehovsky</dc:creator>
		<pubDate>Tue, 03 Nov 2009 22:28:41 +0000</pubDate>
		<guid isPermaLink="false">http://migeel.sk/?p=98#comment-146</guid>
		<description>Yes, those are source-level constructs. But we only have a binary. If you know assembly language, you should be able to translate this to assembly. Instead of changing a structure field, you are changing a specific byte in memory.

Look up OSVERSIONINFOEX on MSDN and find out where is the wProductType field stored (hint: it will be somewhere after the szCSDVersion field, which is a long Utf-16 string with the text &quot;Service Pack 2&quot; or something similar). Then change the value of the byte from 0x03 to 0x01.</description>
		<content:encoded><![CDATA[<p>Yes, those are source-level constructs. But we only have a binary. If you know assembly language, you should be able to translate this to assembly. Instead of changing a structure field, you are changing a specific byte in memory.</p>
<p>Look up OSVERSIONINFOEX on MSDN and find out where is the wProductType field stored (hint: it will be somewhere after the szCSDVersion field, which is a long Utf-16 string with the text &#8220;Service Pack 2&#8243; or something similar). Then change the value of the byte from 0&#215;03 to 0&#215;01.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CJ</title>
		<link>http://migeel.sk/blog/2009/10/17/security-essentials-on-windows-server/comment-page-1/#comment-145</link>
		<dc:creator>CJ</dc:creator>
		<pubDate>Tue, 03 Nov 2009 22:18:29 +0000</pubDate>
		<guid isPermaLink="false">http://migeel.sk/?p=98#comment-145</guid>
		<description>Ok I understand. But at least, could explain &quot;wProductType field in the returned OSVERSIONINFOEX: from VER_NT_SERVER (3) to VER_NT_WORKSTATION (1)&quot;? These commands are not in &quot;C&quot;? The OllyDbg does not show the file in assembly?
PS.: My version of OllyDbg is 1.10.</description>
		<content:encoded><![CDATA[<p>Ok I understand. But at least, could explain &#8220;wProductType field in the returned OSVERSIONINFOEX: from VER_NT_SERVER (3) to VER_NT_WORKSTATION (1)&#8221;? These commands are not in &#8220;C&#8221;? The OllyDbg does not show the file in assembly?<br />
PS.: My version of OllyDbg is 1.10.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michal Strehovsky</title>
		<link>http://migeel.sk/blog/2009/10/17/security-essentials-on-windows-server/comment-page-1/#comment-144</link>
		<dc:creator>Michal Strehovsky</dc:creator>
		<pubDate>Tue, 03 Nov 2009 21:33:52 +0000</pubDate>
		<guid isPermaLink="false">http://migeel.sk/?p=98#comment-144</guid>
		<description>I discussed this with someone else by e-mail and this approach only worked with OllyDbg 1.10 for him. I used the old OllyDbg too. The new version probably misses one of the calls (well, it&#039;s still a beta). Never had a chance to look at what really happens there.

I won&#039;t write a step-by-step tutorial anytime soon, sorry. If you can&#039;t follow the steps above, you won&#039;t be able to resolve problems that might show up later (remember, Security Essentials on Windows Server is an unsupported and untested configuration). It&#039;s for your own good.</description>
		<content:encoded><![CDATA[<p>I discussed this with someone else by e-mail and this approach only worked with OllyDbg 1.10 for him. I used the old OllyDbg too. The new version probably misses one of the calls (well, it&#8217;s still a beta). Never had a chance to look at what really happens there.</p>
<p>I won&#8217;t write a step-by-step tutorial anytime soon, sorry. If you can&#8217;t follow the steps above, you won&#8217;t be able to resolve problems that might show up later (remember, Security Essentials on Windows Server is an unsupported and untested configuration). It&#8217;s for your own good.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CJ</title>
		<link>http://migeel.sk/blog/2009/10/17/security-essentials-on-windows-server/comment-page-1/#comment-143</link>
		<dc:creator>CJ</dc:creator>
		<pubDate>Tue, 03 Nov 2009 21:19:43 +0000</pubDate>
		<guid isPermaLink="false">http://migeel.sk/?p=98#comment-143</guid>
		<description>I try hard, believe me. But I could not. Would like to make a step by step? Sorry my bad English.</description>
		<content:encoded><![CDATA[<p>I try hard, believe me. But I could not. Would like to make a step by step? Sorry my bad English.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

