<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>GL.IB.LY &#187; swiss file knife</title>
	<atom:link href="http://gl.ib.ly/tag/swiss-file-knife/feed/" rel="self" type="application/rss+xml" />
	<link>http://gl.ib.ly</link>
	<description>Thoughts on security, computing, business and stuff!</description>
	<lastBuildDate>Sun, 18 May 2014 11:51:56 +0000</lastBuildDate>
	<language>en-US</language>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.9.1</generator>
	<item>
		<title>The command prompt has been disabled by your administrator?</title>
		<link>http://gl.ib.ly/stuff/2009/02/05/command-prompt-disabled-administrator/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=command-prompt-disabled-administrator</link>
		<comments>http://gl.ib.ly/stuff/2009/02/05/command-prompt-disabled-administrator/#comments</comments>
		<pubDate>Thu, 05 Feb 2009 06:32:03 +0000</pubDate>
		<dc:creator><![CDATA[tariq]]></dc:creator>
				<category><![CDATA[Stuff]]></category>
		<category><![CDATA[cmd.exe]]></category>
		<category><![CDATA[gpo]]></category>
		<category><![CDATA[one liners]]></category>
		<category><![CDATA[patch]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[sfk]]></category>
		<category><![CDATA[swiss file knife]]></category>
		<category><![CDATA[windows]]></category>
		<category><![CDATA[xxd]]></category>

		<guid isPermaLink="false">http://gl.ib.ly/?p=39</guid>
		<description><![CDATA[<p>I came across an old enough post on Didier&#8217;s blog about Group policies that have disabled cmd.exe from running. Didier mentions a few ways to get cmd.exe to run. The suggestion I like the most is to find the DisableCMD string in cmd.exe<span class="ellipsis">&#8230;</span><div class="read-more"><a href="http://gl.ib.ly/stuff/2009/02/05/command-prompt-disabled-administrator/">Read more &#8250;</a></div><!-- end of .read-more --></p><p>The post <a href="http://gl.ib.ly/stuff/2009/02/05/command-prompt-disabled-administrator/">The command prompt has been disabled by your administrator?</a> appeared first on <a href="http://gl.ib.ly">GL.IB.LY</a>.</p>]]></description>
				<content:encoded><![CDATA[<p>I came across an old enough post on Didier&#8217;s blog about <a title="http://blog.didierstevens.com/2007/11/28/quickpost-disableamd-disableregistryfools/trackback/" href="http://web.archive.org/web/20090703174900/http://gl.ib.ly/exit.php?url_id=46&amp;entry_id=22">Group policies that have disabled cmd.exe from running</a>. Didier mentions a few ways to get cmd.exe to run. The suggestion I like the most is to find the <i>DisableCMD</i> string in cmd.exe and change it to <i>DisableAMD</i> using a hex editor. Thankfully there is a tool which will allow us to patch cmd.exe in one tiny line.</p>
<div>The tool is <a title="http://stahlforce.com/dev/swiss-file-knife.html" href="http://web.archive.org/web/20090703174900/http://gl.ib.ly/exit.php?url_id=47&amp;entry_id=22">Swiss File Knife</a> and it is fantabulous. Luckily it is available on Windows as well as Linux. Oh yeah, the command!Well first make a copy of your cmd.exe (%SYSTEMROOT%\System32\cmd.exe) file, mine is called cmd2.exe.</p>
<pre>sfk replace cmd2.exe -binary /440069007300610062006c00650043004D004400/440069007300610062006c00650041004D004400/</pre>
<p>A quick explanation of what is being changed</p>
<pre>  D   i   s   a   b   l   e   C   M  D           ... to...
 440069007300610062006c00650043004D004400
  D   i   s   a   b   l   e   A   M  D    
 440069007300610062006c00650043004D004400</pre>
<p>You can check your changes are all right if you see the following.</p>
<div>xxd cmd2.exe | egrep  -A1 &#8220;D.i.s.a&#8221;</div>
<pre>00040d0: 4400 6900 7300 6100 6200 6c00 6500 5500  D.i.s.a.b.l.e.U.
00040e0: 4e00 4300 4300 6800 6500 6300 6b00 0000  N.C.C.h.e.c.k...
--
0013d40: 7e05 ffff 4400 6900 7300 6100 6200 6c00  ~...D.i.s.a.b.l.
0013d50: 6500 4100 4d00 4400 0000 6689 18e9 def4  e.A.M.D...f.....
--
004a400: 2000 2000 2000 4400 6900 7300 6100 6200   . . .D.i.s.a.b.
004a410: 6c00 6500 2000 6500 7800 6500 6300 7500  l.e. .e.x.e.c.u.
--
004aad0: 2000 4400 6900 7300 6100 6200 6c00 6500   .D.i.s.a.b.l.e.
004aae0: 2000 6400 6500 6c00 6100 7900 6500 6400   .d.e.l.a.y.e.d.</pre>
</div>
<p>The post <a href="http://gl.ib.ly/stuff/2009/02/05/command-prompt-disabled-administrator/">The command prompt has been disabled by your administrator?</a> appeared first on <a href="http://gl.ib.ly">GL.IB.LY</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://gl.ib.ly/stuff/2009/02/05/command-prompt-disabled-administrator/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
