<?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>gHacks Technology News &#124; Latest Tech News, Software And Tutorials &#187; trace</title> <atom:link href="http://www.ghacks.net/tag/trace/feed/" rel="self" type="application/rss+xml" /><link>http://www.ghacks.net</link> <description>A technology news blog covering software, mobile phones, gadgets, security, the Internet and other relevant areas.</description> <lastBuildDate>Sat, 11 Feb 2012 09:52:46 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <atom:link rel="hub" href="http://pubsubhubbub.appspot.com"/><atom:link rel="hub" href="http://superfeedr.com/hubbub"/> <item><title>Tracing a Hacker</title><link>http://www.ghacks.net/2006/04/15/tracing-a-hacker/</link> <comments>http://www.ghacks.net/2006/04/15/tracing-a-hacker/#comments</comments> <pubDate>Sat, 15 Apr 2006 15:12:50 +0000</pubDate> <dc:creator>Martin Brinkmann</dc:creator> <category><![CDATA[Hacking]]></category> <category><![CDATA[Security]]></category> <category><![CDATA[hacker]]></category> <category><![CDATA[trace]]></category> <guid
isPermaLink="false">http://www.ghacks.net/?p=408</guid> <description><![CDATA[Tracing a Hacker is a article aimed at beginners that want to learn the basics of finding out if there is someone connected to their system who should not be connected to it. It gives a rough introduction to some basic concepts like tcp/ip, ports and how hackers find their targets. This is a good read if you don´t know what they are about. After that Omar starts of by explaining the netstat command which lists all the sources that are connected or currently connecting to your computer. If you are running p2p software this can be a lot of connections. I suggest you start of by disabling most tools that you might be running while on the internet. So, no p2p, no messengers aso. ]]></description> <content:encoded><![CDATA[<p>Tracing a Hacker is a article aimed at beginners that want to learn the basics of finding out if there is someone connected to their system who should not be connected to it. It gives a rough introduction to some basic concepts like tcp/ip, ports and how hackers find their targets. This is a good read if you don´t know what they are about. After that Omar starts of by explaining the netstat command which lists all the sources that are connected or currently connecting to your computer. If you are running p2p software this can be a lot of connections. I suggest you start of by disabling most tools that you might be running while on the internet. So, no p2p, no messengers aso.</p><p>After explaining various netstat -commands ports are explained which might help you identify suspicious connections to your computer. It is a good idea to know the standard basic ports like 80 for a http connection and 21 for a ftp connection. This does not mean that every connection on port 80 for instance is harmless but it is a good indicator to leave those ports alone for the beginning and concentrate on more &#8220;suspicious ports first. Ok, so we know about netstat and ports, next in the line is tracert which lets you trace a connection to its beginning. If the hacker is not using a proxy to mask his real ip you find out about his internet service provider this way.</p><p><span
id="more-408"></span></p><p>After that reverse dns querries and dns are explained. The last chapter lists common ports that are often used by trojans and the like. All in all a very good article for everyone who wants to know more about his computer. This is of course aimed at beginners and a good starting point for them. Its easy to use google for further information.</p> ]]></content:encoded> <wfw:commentRss>http://www.ghacks.net/2006/04/15/tracing-a-hacker/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>how to trace a hacker</title><link>http://www.ghacks.net/2006/01/20/how-to-trace-a-hacker/</link> <comments>http://www.ghacks.net/2006/01/20/how-to-trace-a-hacker/#comments</comments> <pubDate>Fri, 20 Jan 2006 07:19:22 +0000</pubDate> <dc:creator>Martin Brinkmann</dc:creator> <category><![CDATA[Advice]]></category> <category><![CDATA[computer]]></category> <category><![CDATA[hacker]]></category> <category><![CDATA[Security]]></category> <category><![CDATA[trace]]></category> <guid
isPermaLink="false">http://www.ghacks.net/?p=287</guid> <description><![CDATA[This is a nice beginners tutorial that tells you how to trace people who try to break into your computer. It covers lots of explanations to questions like "How do these people find their victim?" and "What the phrases TCP/UDP actually mean".]]></description> <content:encoded><![CDATA[<p>This is a nice <a
href="http://forums.techarena.in/guides-tutorials/443453.htm" target="_Blank">beginners tutorial that tells you how to trace people</a> who try to break into your computer. It covers lots of explanations to questions like &#8220;How do these people find their victim?&#8221; and &#8220;What the phrases TCP/UDP actually mean&#8221;.</p><p>It explains the netstat command which shows all connections to your computer and how to interpretate them. After that the tracert command is explained which traces a connection. Finally it gives information on dns, how to lookup a ip and get the host of the connection.</p><p><span
id="more-287"></span></p><p>It´s a useful tutorial that everyone who does not understand this concepts should read. It does not explain proxies which most hackers nowadays use. A tracert would lead to the proxy but not to the hacker himself.</p> ]]></content:encoded> <wfw:commentRss>http://www.ghacks.net/2006/01/20/how-to-trace-a-hacker/feed/</wfw:commentRss> <slash:comments>14</slash:comments> </item> </channel> </rss>
