<?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>Zero Intellect &#187; hexadecimal</title>
	<atom:link href="http://www.zerointellect.com/tag/hexadecimal/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.zerointellect.com</link>
	<description>Technology Blog requiring Zero Intellect to follow !!!</description>
	<lastBuildDate>Mon, 28 Jun 2010 14:09:18 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Securing your URL with Hexadecimal codes</title>
		<link>http://www.zerointellect.com/security/securing-your-url-with-hexadecimal-codes/</link>
		<comments>http://www.zerointellect.com/security/securing-your-url-with-hexadecimal-codes/#comments</comments>
		<pubDate>Mon, 30 Nov 2009 03:22:25 +0000</pubDate>
		<dc:creator>zrydento</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[ascii]]></category>
		<category><![CDATA[ascii table]]></category>
		<category><![CDATA[hexadecimal]]></category>
		<category><![CDATA[url security]]></category>

		<guid isPermaLink="false">http://www.zerointellect.com/?p=158</guid>
		<description><![CDATA[<p> </p>
<p>Hexadecimal equivalent codes of ASCII characters can be used to represent characters of a URL&#8217;s path and filename.</p>
<p>Each hex number is preceded by a &#8220;%&#8221; symbol to identify the following two numbers/letters as a hexadecimal representation of the character</p>
<p>An ASCII chart can be used for the conversion from ASCII to Hex or vice versa</p>
<p>One good source <p>Continue reading <a href="http://www.zerointellect.com/security/securing-your-url-with-hexadecimal-codes/">Securing your URL with Hexadecimal codes</a></p>]]></description>
			<content:encoded><![CDATA[<p> </p>
<p>Hexadecimal equivalent codes of ASCII characters can be used to represent characters of a URL&#8217;s path and filename.</p>
<p>Each hex number is preceded by a &#8220;%&#8221; symbol to identify the following two numbers/letters as a hexadecimal representation of the character</p>
<p>An ASCII chart can be used for the conversion from ASCII to Hex or vice versa</p>
<p>One good source for ASCII to Hex charts is <a href="http://en.wikipedia.org/wiki/ASCII" target="_self">http://en.wikipedia.org/wiki/ASCII</a> (both the tables below have been taken from this URL)</p>
<p> </p>
<p><img class="aligncenter" src="http://www.zerointellect.com/uploads/30112009-diagram-1.png" alt="" width="494" height="860" /></p>
<p> </p>
<p><img class="aligncenter" src="http://www.zerointellect.com/uploads/30112009-diagram-2.png" alt="" width="614" height="859" /></p>
<p> </p>
<p>The need for typing in Hex codes into a URL is to make it possible to include special characters in a URL which would otherwise be wrongly interpreted or not allowed. A good example is SPACE which would not be able to fit into a URL in its original form and hence is represented by the Hex code 20 (prefixed by % in a URL making it %20)</p>
<p> </p>
<p>For example, if we were to visit the URL <a href="http://www.bing.com" target="_blank">www.bing.com</a> , it could be written as</p>
<p> </p>
<blockquote><p><strong>B =  %42</strong></p>
<p><strong>I = %49</strong></p>
<p><strong>N = %4e</strong></p>
<p><strong>G = %47</strong></p></blockquote>
<p> </p>
<p>Hence, <a href="http://www.bing.com" target="_blank">www.bing.com</a> could be written as <a href="http://www.%42%49%4e%47.com" target="_blank">www.%42%49%4e%47.com</a></p>
<p> </p>
<p>Note: The &#8220;slashes&#8221; in the address cannot be represented in hex; nor can the IP address be rendered using this logic (the %XX way) but the rest of the URL can be manipulated</p>
]]></content:encoded>
			<wfw:commentRss>http://www.zerointellect.com/security/securing-your-url-with-hexadecimal-codes/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>IP Address and URL obscuring</title>
		<link>http://www.zerointellect.com/networking/ip-address-and-url-obscuring/</link>
		<comments>http://www.zerointellect.com/networking/ip-address-and-url-obscuring/#comments</comments>
		<pubDate>Sun, 29 Nov 2009 16:27:15 +0000</pubDate>
		<dc:creator>zrydento</dc:creator>
				<category><![CDATA[Networking]]></category>
		<category><![CDATA[cross breed ip address]]></category>
		<category><![CDATA[decimal]]></category>
		<category><![CDATA[dns]]></category>
		<category><![CDATA[domain name system]]></category>
		<category><![CDATA[dword]]></category>
		<category><![CDATA[hex]]></category>
		<category><![CDATA[hexadecimal]]></category>
		<category><![CDATA[hybrid ip address]]></category>
		<category><![CDATA[ip address format]]></category>
		<category><![CDATA[obscure ip address]]></category>
		<category><![CDATA[octal]]></category>

		<guid isPermaLink="false">http://www.zerointellect.com/?p=147</guid>
		<description><![CDATA[<p> </p>
<p>We all know IP addresses to be of the form XX.XX.XX.XX where XX is an octet ranging from 1 to 255 (Although other rules apply as to what the value of XX could be depending on either of the four octets)</p>
<p> </p>
<p>However, for users who want to obscure the actual IP address can do so by representing them in <p>Continue reading <a href="http://www.zerointellect.com/networking/ip-address-and-url-obscuring/">IP Address and URL obscuring</a></p>]]></description>
			<content:encoded><![CDATA[<p> </p>
<p>We all know IP addresses to be of the form XX.XX.XX.XX where XX is an octet ranging from 1 to 255 (Although other rules apply as to what the value of XX could be depending on either of the four octets)</p>
<p> </p>
<p>However, for users who want to obscure the actual IP address can do so by representing them in serveral other formats. Some of the formats are:</p>
<p> </p>
<p><strong>1. Decimal System</strong></p>
<p>The traditional format that we know of is 192.168.1.1 where 4 decimal numbers are seperated by dots (.)</p>
<p>I will practically demonstrate converting between the different formats with a live example <a href="http://www.bing.com" target="_blank">www.bing.com</a></p>
<p> </p>
<blockquote><p><strong>C:\&gt;ping bing.com</strong></p>
<p><strong>Pinging bing.com [64.4.8.147] with 32 bytes of data:</strong></p>
<p><strong>Request timed out.<br />
Request timed out.<br />
Request timed out.<br />
Request timed out.</strong></p>
<p><strong>Ping statistics for 64.4.8.147:<br />
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),</strong></p></blockquote>
<p> </p>
<p>Here the Decimal System version of the IP address <strong>64.4.8.147</strong> , this is represented in the base 10 system. Typing <a href="http://64.4.8.147" target="_blank">http://64.4.8.147</a> in the browser would also take you to <a href="http://www.bing.com" target="_blank">www.bing.com</a></p>
<p>  </p>
<p><strong>2. Octal System</strong></p>
<p>An IP address represented in the octal system is basically in the base-8 system</p>
<p>64.4.8.147  would be broken down into</p>
<p>64 = 100 (octal)</p>
<p>4 = 4 (octal)</p>
<p>8 = 10 (octal)</p>
<p>147 = 223 (octal)</p>
<p>Hence the IP address in Octal format would be 0100.04.010.0223 (for those people who hate 0&#8242;s and 1&#8242;s, the same conversion can be easily done using the Windows Calculator)</p>
<p> </p>
<p>Note: A single leading zero has been added to every octal number above, however any number of leading zeroes can be added (there is however a limit, some browsers won&#8217;t accept lots of zeroes)</p>
<p>Hence, 0100.04.010.0223 is the same as 00100.004.0010.00223 and <a href="http://www.bing.com" target="_blank">www.bing.com</a> can also be written as <a href="http://0100.04.010.0223" target="_blank">http://0100.04.010.0223</a></p>
<p> </p>
<p><strong>3. Domain Name System</strong></p>
<p>Here the IP address is represented in its equivalent domain name using human recognizable characters. In our example, the DNS equivalent would be <a href="http://www.bing.com" target="_blank">www.bing.com</a></p>
<p><strong> </strong> </p>
<p><strong>4. Hexadecimal System</strong></p>
<p>To convert a decimal IP address into its hexadecimal equivalent, break the ip address into its individual octets. Let us take out example above 64.4.8.147</p>
<p>64 = 40 (hex)</p>
<p>4 = 04 (hex)</p>
<p>8 = 08 (hex)</p>
<p>147 = 93 (hex)</p>
<p>Hence, <strong>64.4.8.147</strong> is equivalent to <strong>0&#215;40040893</strong>, the 0x is prefixed to indicate hexadecimal. Typing <a href="http://ox40040893" target="_blank">http://ox40040893</a> into the browser would take you to the bing website also</p>
<p> </p>
<p><strong>5. Double Word (DWORD)</strong></p>
<p>To understand this format, we first need to understand what a double word is. A word consists of 16 binary digits (bits) and a double word consists of 32 bits</p>
<p> To convert a decimal IP address into DWORD format, we first need to convert it into Hexadecimal and then convert the hexadecimal number to base 10</p>
<p>From point 4 (decimal to hex conversion) above we can see that the Hex equivalent of our sample IP address, <strong>64.4.8.147</strong> is <strong>0&#215;40040893</strong></p>
<p>Now to convert this Hexadecimal number to DWORD, one of the easiest ways is to use the Windows Calculator</p>
<p>Click on Start &gt; Programs &gt; Accessories &gt; Calculator<br />
Click on View &gt; Scientific<br />
Now, select ‘Hex’ from the left top corner and type in the hex value in the field<br />
Then click on Dec (Decimal). You will find that the value that you typed in would have changed to the corresponding value</p>
<p> </p>
<p><img src="http://www.zerointellect.com/uploads/29112009-diagram-1.png" alt="" width="480" height="316" /></p>
<p><img src="http://www.zerointellect.com/uploads/29112009-diagram-2.png" alt="" width="480" height="316" /></p>
<p> </p>
<p>Hence the equivalent DWORD value as per the diagram is 1074006163 and entering <a href="http://1074006163" target="_blank">http://1074006163</a> into the browser would also take you to <a href="http://www.bing.com" target="_blank">www.bing.com</a></p>
<p> </p>
<p><strong>6. Hybrid/Mixed</strong></p>
<p>Last but not least, we have another format that is a continental cocktail of two or more of the formats above. In other words, we can mix decimal and hex in one ip address or anything that you can think of</p>
<p>For example, IP address formats</p>
<p>Decimal   <strong>64.4.8.147</strong></p>
<p>Hexadecimal   <strong>0&#215;40040893</strong></p>
<p>DWORD   <strong>1074006163</strong></p>
<p>I can mix the decimal and the hexadecimal as in <a href="http://64.0x04.0x08.147/" target="_blank">http://64.0&#215;04.0&#215;08.147/</a></p>
<p>I can also mix and match more than 2 formats (hex, decimal, octal) as in <a href="http://64.0x04.8.0223" target="_blank">http://64.0&#215;04.8.0223</a></p>
<p> </p>
<p><strong>Expressing characters in the URL in Hexadecimal format</strong></p>
<p>An ASCII to Hex Chart can be used to represent letters in the URL in Hex format</p>
<p>For the complete chart and more information, an excellent resource is</p>
<blockquote><p><a href="http://en.wikipedia.org/wiki/ASCII" target="_blank"><strong>http://en.wikipedia.org/wiki/ASCII</strong></a></p></blockquote>
<p> </p>
<blockquote><p><strong>WARNING: The obscured URL&#8217;s do not work in all browsers of all types and versions, internet explorer is pretty flexible, however netscape and firefox are crancky from my experience with URL&#8217;s in different formats</strong></p></blockquote>
<p> </p>
<p>To summarize, URL&#8217;s can be obscured by converting IP address from the traditional decimal format to any of the other formats mentioned like DWORD, Octal, Hexadecimal, etc. In addition, characters in a URL can be expressed as numbers in hexadecimal format</p>
]]></content:encoded>
			<wfw:commentRss>http://www.zerointellect.com/networking/ip-address-and-url-obscuring/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

