Friday, August 22, 2008
Make Web Pages Available for Offline Viewing
With Internet Explorer 6 in Windows XP, you can make a Web page available offline and view it when your computer is not connected to the Internet—for example on your laptop during a flight. This feature is also handy for viewing Web pages at home without tying up a phone line if you have a dial–up Internet connection.
To make the current Web page available offline
On the Favorites menu, click Add to Favorites.
Select the Make available offline check box.
To specify a schedule for updating that page, and how much content to download, click Customize.
Follow the instructions on your screen.
To make an existing favorite item available offline
On the Favorites menu, click Organize Favorites.
Click the page you want to make available offline.
Select the Make available offline check box.
To specify a schedule for updating that page, and how much content to download, click Properties.
To view Web pages without being connected to the Internet
After you mark your favorite pages for viewing offline, you can view them offline by following these steps
Before you disconnect from the Internet, on the Tools menu, click Synchronize.
When you're ready to work offline, on the File menu, click Work Offline. Internet Explorer will always start in Offline mode until you click Work Offline again to clear the check mark.
In your Favorites list, click the item you want to view.
You can also make Web pages available offline without adding them to your Favorites list, by saving the pages on your computer.
Follow these steps
On the File menu, click Save As.
Double–click the folder you want to save the page in.
In the File name box, type a name for the page.
In the Save as type box, select a file type.
Do one of the following:
To save all of the files needed to display this page, including graphics, frames, and style sheets, click Web Page, complete. This option saves each file in its original format.
To save all of the information needed to display this page in a single MIME–encoded file, click Web Archive. This option saves a snapshot of the current Web page. This option is available only if you have installed Outlook Express 5 or later. When you choose Web Page, complete, only the current page is saved. With Web Page, complete and Web Archive, you can view all of the Web page offline, without adding the page to your Favorites list and marking it for offline viewing.
To save just the current HTML page, click Web Page, HTML only. This option saves the information on the Web page, but it does not save the graphics, sounds, or other files.
To save just the text from the current Web page, click Text Only. This option saves the information on the Web page in straight text format.
Thursday, August 21, 2008
Speed Up Browsing
When you connect to a web site your computer sends information back and forth. Some of this information deals with resolving the site name to an IP address, the stuff that TCP/IP really deals with, not words. This is DNS information and is used so that you will not need to ask for the site location each and every time you visit the site. Although Windows XP and Windows XP have a pretty efficient DNS cache, you can increase its overall performance by increasing its size. You can do this with the registry entries below:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters]
"CacheHashTableBucketSize"=dword:00000001
"CacheHashTableSize"=dword:00000180
"MaxCacheEntryTtlLimit"=dword:0000fa00
"MaxSOACacheEntryTtlLimit"=dword:0000012d
Make a new text file and rename it to dnscache.reg. Then copy and paste the above into it and save it. Merge it into the registry.
Tuesday, August 19, 2008
Reduce Temporary Internet F ile Space
The temporary internet files clutter your hard drive with copies of each page visited. These can build up over time and take up disk space. Even more bothersome is that instead of getting new pages each time IE often takes the page out the temp internet files. This can be a problem if you are viewing a website that is updated all the time. If you are on a slow connection such as a 56K or lower then this can be good but if you are on a fast broadband connection, like me, then you can get away with decreasing the size of your temp internet files to just one meg without any performance decrease.
Launch Internet Explorer.
Select the Tools from the menu bar.
Then select Internet Options... from the drop down menu.
Once the internet options has loaded click on the general tab.
Under the temporary internet files section click the settings button.
A settings window will load. Slide the slider all the way to the left so the size indicated in the text box on the right is one.
Click OK
Click Ok
XP to directly access WebDAV "internet disks"
Windows XP can directly access WebDAV "internet disks" such as Apple's iDisk.
In Internet Explorer, use the "Open..." command, type the name of the WebDAV server you want to access (e.g., http://idisk.mac.com/username) and select the "Open as Web Folder" checkbox. Enter the password when prompted and you're in!
This trick also works on Windows Me and Windows 2000. Interestingly, Windows XP doesn't seem to support iDisk via the "Add a Network Place" command, possible with these other operating systems.
Once set up using the "Open" command, however, the idisk can be accessed by simply double-clicking its icon in the Network Places folder.
Tuesday, November 20, 2007
Change Drive Icon..!!!
Changing drives icon First of all copy a icon file to the root of the drive.example: c:\icon.ico Then create a file called: autorun.inf in c:\autorun.infthen open that file and type the following:[autorun]icon=icon.ico save and close the file. Now open my computer and refresh.. and woh! icon changed....you can apply to other drives too.be careful:"autorun.inf" and "ico.ico" must be in the root of the drive.example: c:\autorun.inf and c:\icon.ico.same on the root.
Tips to create a Strong Password easily..!!!
How to create a Strong Password.
This lead me to explain the method I follow to set a password - A Strong Password indeed by all standards.
You must follow the following criteria while creating a Strong Password:
* The password must be a minimum of 8+ characters.
* The password must have 1 number , 1 special character, 1 Upper Case character.
A very simple example that I use to explain my friends and colleages is : P@ssw0rd. It fullfills all the criteria's. The 'a' is replaced by a special character @. The 'P' is of upper case. The 'o' is replaced by the numeral 0.
Well, you can now convert your regular password into a Strong Password by following a few changes like the example I have mentioned above for the simple password - P@ssw0rd.
* Make the first character Upper Case.
* Change all 'a' in the password to the special character @.
* Change all 's' in the password to the special character $.* Change all 'l' in the password to the special character !.
* Change all 'o' in the password to the numerical 0.
* Change all 'i' in the password to the numerical 1.
How to Stop Hackers (How To Catch A Hacker)
Some one wrote this great Post at orkut about Catching Hackers
I don't know who exactly the writer of this great post is...
Here is what he had to write :
"just wrote this guide to give you some tips of which you may not have heard yet. Hopefully, it won't come to a hacker getting in, but if it does...
Tip 1: Hackers cover their tracks. Experienced hackers cover them more thorougly, but amateur hackers sometimes leave things behind. Don't expect them to leave any really big evidence behind; expect more of little things here and there you might find surprising. For example, if you're writing a term paper and a black hat hacker accidently saved it when he took a paragraph out- that's suspicious. Where did that paragraph go? Well, for one thing, now you know he was in that area. Check the folders surrounding the file- you might find something.
Tip 2: Decipher between the type of hackers that are attacking you. Experienced hackers will have a more in depth look around when they penetrate your system. They won't touch much because they know that that won't add too much to their knowledge. But if you know a hacker's been in, and some files are messed with, and you have a log of someone guessing passwords to a file or something of that sort, its probably some newbie who's just starting out. These are the easiest hackers to catch. They usually get so caught up in thoughts like "I'm in!" that they forget the basics, such as work behind a proxy.
Tip to protect yourself
My friend was setting up a webserver once. His first time too, and he wasn't to anxious to set up some good software to protect against hackers and viruses. He didn't put up one IDS, and before you know it, the obvious happened. But this time, a newbie had struck. The nice log files showed, bluntly across the screen, multiple instances of a foreign IP address that stood out. Some stupid newbie had tried to login as "uucp" on my friend's XP computer, with a password of "uucp." Well, that's great, but he also had tried the same user/pass combination three times, enough to get himself logged nicely. Even a semi-brainless user with some form of neurological system knows that uucp isn't a default XP account. Again, excitement toiled this hacker's brain, and maybe if he hadn't done that, along with a few other stupid things, he wouldn't have gotten caught. What other things did he do? Well, lets see. He openned 35 instances of MS-DOS. He tried to clean the printer's heads, and he edited a .gif in notepad. Then he uninstalled a few programs and installed some html editor, and replaced four files with the words "14P." he might as well have posted his phone number. In a few days, we had tracked him down to a
suburban town in Ohio. We let him go, not pressing any charges, because he had done nothing really damaging and had provided me with an example of a moron for this guide.
Tip 3: Don't go crazy if you lose data. Chances are, if it was that important, you would have backed it up anyway. Most hackers nowadays wish they were back in 1989 when they could use a Black Box and having a Rainbow Book actually meant something. Most hackers aren't blackhat, they are whitehat, and some even greyhat. But in the end, most hackers that are in systems aren't satisfied by looking around. From past experiences, I have concluded that many hackers like to remember where've they been. So, what do they do? They either press delete here and there, or copy some files onto their systems. Stupid hackers (yes, there are plenty of stupid hackers) send files to e-mail addresses. Some free email companies will give you the IP of a certain e-mail address's user if you can prove that user has been notoriously hacking you. But most of the time, by the time you get the e-mail addy it's been unused for weeks if not months or years, and services like hotmail have already deleted it.
Tip 4: Save information! Any information that you get from a log file (proxy server IP, things like "14P", e-mail addresses that things were sent to, etc.) should be saved to a floppy disk (they're not floppy anymore, I wish I could get out of the habit of calling them that) incase there's a next time. If you get another attack, from the same proxy, or with similar e-mail addresses (e.g: one says Blackjack 123@something.whatever and the other says Black_jack_45@something.znn.com) you can make an assumption that these hackers are the same people. In that case, it would probably be worth the effort to resolve the IP using the proxy and do a traceroute. Pressing charges is recommended if this is a repeat offender.
Tip 5: Don't be stupid. If you've been hacked, take security to the next level. Hackers do talk about people they've hacked and they do post IPs and e-mail addresses. Proof? Take a look at Defcon Conventions. I've never gone to one, but I've seen the photos. The "Wall of Shame"-type of boards I've seen have IPs and e-mail addresses written all over them in fat red, dry-erase ink. Don't be the one to go searching the Defcon website and find your e-mail address posted on the Wall of Shame board!
Tip 6: Don't rely on luck. Chances are, sometime or another, you're going to be targeted for an attack. Here you can rely on luck. Maybe they'll forget? Maybe they don't know how to do it? If you think this way, a surprise is going to hit your face very hard. Another way you could stupidly rely on luck is by saying this: It's probably just a whitehat. On the contrary, my friend, it's probably just a blackhat. A blackhat with knowledge stored in his head, ready to be used as an ax. It's your data. You take the chance.
How Internet Cookies Work
Internet cookies are incredibly simple, but they are one of those things that have taken on a life of their own. Cookies started receiving tremendous media attention starting in February 2000 because of Internet privacy concerns, and the debate still rages.
On the other hand, cookies provide capabilities that make the Web much easier to navigate. The designers of almost every major site use them because they provide a better user experience and make it much easier to gather accurate information about the site's visitors.
We will take a look at the basic technology behind cookies, as well as some of the features they enable. You will also have the opportunity to see a real-world example of what cookies can and cannot do using a sample page.
Cookie Basics
In April of 2000 I read an in-depth article on Internet privacy in a large, respected newspaper, and that article contained a definition of cookies. Paraphrasing, the definition went like this:
Cookies are programs that web sites put on your hard disk. They sit on your computer gathering information about you and everything you do on the Internet, and whenever the web site wants to it can download all of the information the cookie has collected.
Definitions like that are fairly common in the press. The problem is, none of that information is correct. Cookies are not programs, and they cannot run like a program does. Therefore they cannot gather any information on their own. Nor can they collect any personal information about you from your machine.
Here is a valid definition of a cookie:
A cookie is a piece of text that a web server can store on a user's hard disk. Cookies allow a web site to store information on a user's machine and later retrieve it. The pieces of information are stored as name-value pairs.
For example, a web site might generate a unique ID number for each visitor and store the ID number on each user's machine using a cookie file.
If you use Microsoft's Internet Explorer to browse the web, you can see all of the cookies that are stored on your machine. The most common place for them to reside is in a directory called c:\windows\cookies. When I look in that directory on my machine, I find 165 files. Each file is a text file that contains name-value pairs, and there is one file for each web site that has placed cookies on my machine.
You can see in the directory that each of these files is a simple, normal text file. You can see which web site placed the file on your machine by looking at the file name (the information is also stored inside the file). You can open each file up by clicking on it.
For example, I have visited goto.com, and the site has placed a cookie on my machine. The cookie file for goto.com contains the following information:
UserID A9A3BECE0563982D www.goto.com/
What goto.com has done is stored on my machine a single name-value pair. The name of the pair is UserID,and the value is A9A3BECE0563982D. The first time I visited goto.com, the site assigned me a unique ID value and stored it on my machine.
[Note that there probably are several other values stored in the file after the three shown above. That is housekeeping information for the browser.]
The vast majority of sites store just one piece of information -- a user ID -- on your machine. But there really is no limit -- a site can store as many name-value pairs as it likes.
A name-value pair is simply a named piece of data. It is not a program, and it cannot "do" anything. A web site can retrieve only the information that it has placed on your machine. It cannot retrieve information from other cookie files, nor any other information from your machine.
How Does Cookie Data Move?
As you saw in the previous section, cookie data is simply name-value pairs stored on your hard disk by a web site. That is all that cookie data is. The web site can store the data, and later it receives it back. A web site can only receive the data it has stored on your machine. It cannot look at any other cookie, nor can it look at anything else on your machine.
The data moves in the following manner:
If you type the URL of a web site into your browser, your browser sends a request to the web site for the page. For example, if you type the URL http://www.netcrackers.blogspot.com into your browser, your browser will contact Blogger's server and request its home page.
When the browser does this, it will look on your machine for a cookie file that Blogger has set. If it finds a Blogger cookie file, your browser will send all of the name-value pairs in the file to Blogger's server along with the URL. If it finds no cookie file, it will send no cookie data.
Blogger's web server receives the cookie data and the request for a page. If name-value pairs are received, Blogger can use them.
If no name-value pairs are received, Blogger knows that you have not visited before. The server creates a new ID for you in Blogger's database and then sends name-value pairs to your machine in the header for the web page it sends. Your machine stores the name-value pairs on your hard disk.
The web server can change name-value pairs or add new pairs whenever you visit the site and request a page.
There are other pieces of information that the server can send with the name-value pair. One of these is an expiration date. Another is a path (so that the site can associate different cookie values with different parts of the site). You have control over this process. You can set an option in your browser so that the browser informs you every time a site sends name-value pairs to you. You can then accept or deny the values.
How Do Web Sites Use Cookies?
Cookies evolved because they solve a big problem for the people who implement web sites. In the broadest sense, a cookie allows a site to store state information on your machine. This information lets a web site remember what state your browser is in. An ID is one simple piece of state information -- if an ID exists on your machine, the site knows that you have visited before. The state is, "Your browser has visited the site at least one time", and the site knows your ID from that visit.
Web sites use cookies in many different ways. Here are some of the most common examples:
Sites can accurately determine how many readers actually visit the site. It turns out that because of proxy servers, caching, concentrators and so on, the only way for a site to accurately count visitors is to set a cookie with a unique ID for each visitor. Using cookies, sites can:
->Determine how many visitors arrive
->Determine how many are new vs. repeat visitors
->Determine how often a visitor has visited
The way the site does this is by using a database. The first time a visitor arrives, the site creates a new ID in the database and sends the ID as a cookie. The next time the user comes back, the site can increment a counter associated with that ID in the database and know how many times that visitor returns.
Sites can store user preferences so that the site can look different for each visitor (often referred to as customization). For example, some sites offer you the ability to change content/layout/color. It or allows you to enter your zip code and get customized weather information.
Most sites seem to store preferences like this in the site's database and store nothing but an ID as a cookie, but storing the actual values in name-value pairs is another way to do it.
Ecommerce sites can implement things like shopping carts and "quick checkout" options. The cookie contains an ID and lets the site keep track of you as you add different things to your cart. Each item you add to your shopping cart is stored in the site's database along with your ID value. When you check out, the site knows what is in your cart by retrieving all of your selections from the database. It would be impossible to implement a convenient shopping mechanism without cookies or something like it.
In all of these examples, note that what the database is able to store is things you have selected from the site, pages you have viewed from the site, information you give to the site in online forms, etc. All of the information is stored in the site's database, and a cookie containing your unique ID is all that is stored on your computer in most cases.
An Example
To give you a simple example of what cookies and a database can do, We can take the example of Verizon.com They have created a simple history and statistics system for there articles. There system runs on the Verizon servers and lets you view your activity on the Verizon site. Here's how it works:
When you visit Verizon for the first time, the server creates a unique ID number for you and stores a cookie on your machine containing that ID. For example, on the machine I am using now, this is what I see in the Verizon cookie file:
user 35005 www.verizon.com/
There is nothing magic about the number 35,005 -- it is simply an integer that they increment each time a new visitor arrives. I was user number 35,005 to come to the Verizon site since this cookie system was installed. We could make the ID value as elaborate as we desire -- many sites use IDs containing 20 digits or more.
Now, whenever you visit any page on Verizon, your browser sends your cookie containing the ID value back to the server. The server then saves a record in the database that contains the time that you downloaded the page and the URL, along with your ID.
To see the history of your activity on Verizon, you can go to this URL on the site:
http://www.verizon.com/history.php
Your browser sends your ID value from the cookie file to the server along with the URL. The history.php page runs a piece of code that queries the database and retrieves your history on the site. It also calculates a couple of interesting statistics. Then it creates a page and sends it to your browser.
Try the URL for the history page now:
http://www.verizon.com/history.php
Then go view a couple of other pages on Verizon and try it again. You will see that the statistics change and so does the list of files.
Problems with Cookies
Cookies are not a perfect state mechanism, but they certainly make a lot of things possible that would be impossible otherwise. Here are several of the things that make cookies imperfect.
People often share machines -- Any machine that is used in a public area, and many machines used in an office environment or at home, are shared by multiple people. Let's say that you use a public machine (in a library, for example) to purchase something from an on-line store. The store will leave a cookie on the machine, and someone could later try to purchase something from the store using your account. Stores usually post large warnings about this problem, and that is why. Even so, mistakes can happen.
On something like a Windows NT machine or a UNIX machine that uses accounts properly, this is not a problem. The accounts separate all of the users' cookies. Accounts are much more relaxed in other operating systems, and it is a problem.
If you try the example above on a public machine (in a library or school, for example), and if other people using the machine have visited Verizon, then the history URL may show a very long list of files.
Cookies get erased -- If you have a problem with your browser and call tech support, probably the first thing that tech support will ask you to do is to erase all of the temporary Internet files on your machine. When you do that you lose all of your cookie files. Now when you visit a site again, that site will think you are a new user and assign you a new cookie. This tends to skew the site's record of new versus return visitors, and it also can make it hard for you to recover previously stored preferences. This is why sites ask you to register in some cases -- if you register with a user name and a password, you can re-login even if you lose your cookie file and restore your preferences. If preference values are stored directly on the machine then recovery is impossible. That is why many sites now store all user information in a central database and store only an ID value on the user's machine.
If you erase your cookie file for Verizon and then revisit the history URL in the previous section, you will find that Verizon has no history for you. The site has to create a new ID and cookie file for you, and that new ID has no data stored against it in the database.
Multiple machines -- People often use more than one machine during the day. For example a machine in the office, a machine at home and a laptop for the road. Unless the site is specifically engineered to solve the problem, the result will be three unique cookie files on all three machines. Any site that I visit from all three machines will track me as three separate users. It can be annoying to set preferences three times. Again, a site that allows registration and stores preferences centrally may make it easy for me to have the same account on three machines, but the site developers must plan for this when designing the site.If you visit the history URL demonstrated in the previous section from one machine and then try it again from another, you will find that your history lists are different. This is because the server created two IDs for you on the two machines.
There are probably not any easy solutions to these problems, short of asking users to register and storing everything in a central database.
Why the Fury around Cookies?
If you have read the article to this point, you may be wondering why there has been such an uproar in the media about cookies and Internet privacy. You have seen in this article that cookies are benign text files, and you have also seen that they provide lots of useful capabilities on the web.
There are two things that have caused the strong reaction around cookies:
The first is something that has plagued consumers for decades but is now getting out of hand. Let's say that you purchase something from a traditional mail order catalog. The catalog company has your name, address and phone number from your order, and it also knows what items you have purchased. It can sell your information to others who might want to sell similar products to you. That is the fuel that makes telemarketing and junk mail possible.
On a web site, the site can track not only your purchases, but also the pages that you read, the ads that you click on, etc. If you then purchase something and enter your name and address, the site potentially knows much more about you than a traditional mail order company does. This makes targeting much more precise, and that makes a lot of people uncomfortable.
Different sites have different policies. Many companies have strict privacy policies and do not sell or share any personal information about customers with any third party except in cases where you specifically allow them to do so. Other companies aggregate information together and distribute it.
The second is new. There are certain infrastructure providers that can actually create cookies that are visible on multiple sites. Many firms use these companies to serve ad banners on their sites. These companies place small (1x1 pixels) GIF files on the site that allow them to load cookies on your machine. The companies can then track your movements across multiple sites. It can potentially see the search strings that you type into search engines (due more to the way some search engines implement their systems, not because anything sinister is intended). Because it can gather so much information about you from multiple sites, the companies can form very rich profiles. These are still anonymous, but they are rich.
One company then went one step further by acquiring another firm, it threatened to link these rich anonymous profiles back to name and address information -- it threatened to personalize them, and then sell the data. That began to look very much like spying to most people, and that is what caused the uproar. Some companies are in a unique position to do this sort of thing, because they serve ads on so many sites. Cross-site profiling is not a capability available to individual sites, because cookies are site specific.
Everything You wanted to know about FIREWALLS..!!
A firewall is basically something that protects the network from the Internet. It is derived from the concept of firewalls used in vehicles which is a barrier made of fire resistant material protecting the vehicle in case of fire. Anyway a firewall is best described as a software or hardware or both Hardware and Software packet filter that allows only selected packets to pass through from the Internet to your private internal network. A firewall is a system or a group of systems which guard a trusted network( The Internal Private Network from the untrusted network (the Internet.) To understand how a firewall works, firstly we need to understand how exactly data is transferred on the Internet.
The TCP\IP suite is responsible for successful transfer of data across a network both the Internet and the Intranet. The TCP\IP suite is a collection of protocols which are inter-related and interdependent and act as a set of rules according to which data is transferred across the network. A protocol can be defined as a language or a standard which is followed while transfer of data takes place.
A firewall relies on the source and destination IP and also the ports to control the packet transfer between the untrusted network and the trusted network. Firewalls can be classified into 3 types:
1. Packet Filter Firewalls
2. Application proxy Firewalls
3. Packet Inspection Firewalls
Packet Filter Firewalls
They are the earliest and the most criticized firewalls, which nowadays are not easily found. They are usually Hardware based i.e. Router Based (a router is a piece of device which connects two
networks together.) Whenever a Packet Filter Firewall receives a packet for permission to pass through, it compares the header information i.e. the source and destination IP address, and port number with a table of predefined access control rules If the header information matches, then the packet is allowed to pass else the packet is direct contact between the untrusted system and the trusted private system.
Such Firewalls can be fooled by using techniques like IP Spoofing in which we can change the source IP such that the firewall thinks that the packet has come from a trusted system which is among the list of systems which have access through the firewall.
Application proxy Firewalls
The shortcomings of the packet filter firewalls are addressed by the new type of firewalls developed by the DARPA. It was widely believed that the earlier type of firewalls were not secure enough as they allowed the untrusted systems to have a direct connection with the trusted systems. This problem was solved with the use of Proxy servers as firewalls. A proxy server which is used as a firewall are called application proxy servers. This kind of a proxy firewall examines what application or service (running on ports) a packet is meant for and if that particular service is available only then is the packet allowed to pass through and if the service is unavailable then the packet is discarded or dropped by the firewall.
Packet Inspection Firewalls
It can be also known as an extension of the Packet Filter Firewall. It not only verifies the source and
destination IP's and ports, it also takes into consideration or verifies that content of the data before passing it through. There are two ways in which this kind of a firewall verifies the data to
be passed:
State and Session.
In case of state inspection, an incoming packet is allowed to pass through only if there is a matching outward bound request for this packet. This means that the incoming packet is allowed to pass through only if the trusted server had requested for it or had sent an invitation for it.
In case of session filtering, the data of the incoming is not verified, but instead the network activity is traced and once a trusted system ends the session, no further packets from that system pertaining to that session are allowed to pass through.
All along you will come across many Firewalls on various systems, basically a
firewall can be established
or setup in two ways:
1. Dual-homed gateway
2. Demilitarized zone (DMZ)
In a dual homed gateway firewall, there is a single firewall with 2 connections, one for the trusted network and the other for the untrusted network.
In the case of a Demilitarized Firewall or a DMZ there are two firewalls, each with two connections, but there is a slight difference in the case of a DMZ setup.
In the case of a DMZ setup, there are two firewalls, the first having two connections, one leading to the untrusted network and the other leading to the host systems like the email server or the FTP server etc.
In the case of a Dual Homed Gateway the untrusted network is connected to the host systems (email and FTP servers etc) through a firewall and these host systems are connected to the internal private network. There is no second firewall between the host systems and the internal
private trusted network.
The basic structure of the DMZ setup declares it to be a more secure system as even if an attacker gets through the first firewall, he just reaches the host systems, while the internal network is protected by another firewall.
Friday, August 31, 2007
Block Or Unblock Websites without software !
Many times in schools, colleges & offices surfing some sites like orkut,etc are banned !
To overcome this you can unblock these or block some other websites and play pranks !
Do The Following :
fFor eg you want to block www.xyz.com !
* Open the folder C:\WINDOWS\system32\drivers\etc
* There you will find a file named HOSTS
* Click on the file and press SHIFT and now right click on it .
* From the right click menu select Open with .
* Now, select Notepad to open the file from the list !
* Now, in the file under the line 127.0.0.1 localhost add another line as 127.0.0.2 www.xyz.com.
* Now, File>>Save !
Now, open your web browser and try openning www.xyz.com , it will not load !
To unblock sites just do the vice versa !
Monday, August 27, 2007
Fooling Rapidshare
Its very easy to fool RapidShare server if your IP address is assigned by your ISP Just follow these simple steps clean up IE or netscape cookie ( In this case the one that belong to rapidshare website) On Command prompt type ----->ipconfig /flushdns<---Enter
type ----->ipconfig /release<---Enter
type ----->ipconfig /renew<---Enter
type ----->exit<--------Enter
Or save these commands in a bat file and run it everytime you need to fool Rapidshare server.Remember to clean up rapidshare cookie in your temp Internet files folder. Now you should be ready to download as many files as you want from their server.
Posts
