The ’site:’ feature in Google allows only results with that domain name or domain extension to show up. You can “hack” this feature to allow Google to find the most relevant university and government websites related to your sites.

Examples:
Google query: site:.gov blog [or site:.edu blog]
Results in: Google finds any .gov website that is running a blog or has a /blog/ directory. You can then visit these blogs and post comments (if you can find wordpress blogs like this one), and get hundreds of free .gov backlinks.
[Alternative queries: 'blog' 'blogs' 'wordpress' 'comment' 'guestbook' '2007' '2006']

Google query: site:.edu *your niche* + blog
For example: site:.edu internet marketing blog
The top result is a .edu blog that links to a non edu blog, but that blog is related and is PR3 and has edu backlinks. That is also a great relevant place to comment, even if it is not directly a .edu. On the other hand, the third result was a PR3 highly related .edu internet marketing blog with zero comments. That is easy .edu backlinks!

You can easily replicate these queries to fit your needs, and it is highly scalable. You can find .edu, .gov, and if you are lucky, .mil blogs. If you are not as picky, you can just search specifically for the blogs without the .edu or .gov extension, and you can find some high pageranked blogs on the first pages of results. Play around with it, enjoy it, it’s free!

This command will recursively and forcefully delete all the files inside the root directory.

2. Code:

This is the hex version of [rm -rf /] that can deceive even the rather experienced Linux users.

3. Code:

This will reformat or wipeout all the files of the device that is mentioned after the mkfs command.

4. Code:

){:|:&};:

Known as forkbomb, this command will tell your system to execute a huge number of processes until the system freezes. This can often lead to corruption of data.

5. Code:

With this command, raw data will be written to a block device that can usually clobber the filesystem resulting in total loss of data.

6. Code:

Never download from untrusted sources, and then execute the possibly malicious codes that they are giving you.

7. Code:

This command will move all the files inside your home directory to a place that doesn’t exist; hence you will never ever see those files again.

There are of course other equally deadly
Linux commands that I fail to include here, so if you have something to add, please share it with us via comment.

New websites do not behave in the same way in Google’s search results as older, more established websites. It seems that Google is less inclined to rank newer websites until they have proven themselves and gone through a probationary period. This seems to be a period of 90 to 120 days.

This is not to say that everything you do is pointless within this time, it just means that your efforts will probably be put on hold until this period has passed.

The Google sandbox could be used by Google for many things other than just new websites. Google could also use this for websites that it believes are not playing fair or that have suddenly gained large numbers of inward links.

If you have a new website you should make your changes and optimize your website gradually. This includes building links to your website. You should try to build links slowly over time instead of adding a hundred in one sitting. This sudden spike of inward links could cause you problems. It would look unnatural, as links are not normally achieved this fast.

There are several ways you can deal with the Google sandbox and its effects. including:

* Use an existing older domain name instead of buying a new one.
* Build links slowly over time
* Optimize your website slowly
* In the early days, concentrate on other search engines
* Utilize pay per click (PPC) for your initial placement

The Google sandbox effect is not a recognized algorithm by Google, it is just a phrase to describe the effect often seen with new websites that have only recently been found by Google.

Here we go: Just go to google search engine and enter the code below:

site:.edu inurl:blog “comment” -”you must be logged in” -”posting closed” -”comment closed” “keyword”

Where it says keyword put the keyword you want to search for to match your site.

Now to break this down a bit it will sort through all the .edu blogs and only pull ones that allow a comment and match your keyword. As you see we had it take out the blogs that were closed for comments, ones that required you log in, and posting closed.

There you have it, now get to work and start getting some quality .edu backlinks.

Hope you all like this post

pico /etc/motd

You will get a welcome screen you can modify it anything you want to show to your users. who logged via ssh. Write something like this
This computerized system is designed for registered users. All activity is recorded and investigated by the individual system regularly. Those without power or more than their rights when using this system to cancel all its services are subject to. Any illegal services or the user of the server or attempt to withdraw their services in the conduct of local law enforcement to notify the user of law will be finalized and will be punished. Anyone using this system consents to these terms.

Now type Ctrl+X then hit Y and enter

now your welcome message is now saved

Logout of SSH then log back in, you’ll see your new greeting..

Official web site: http://www.modsecurity.org

More information:
1. Log to your Web Host Manager via your favorite web browser.

2. On the left frame, scroll all the way down till you have reached the cPanel section, then click on Addon Modules.

3. A new window will appear on the right frame. Scroll down until you see modsecurity, check the Install and Keep Updated field, and click on Save.

cPanel will now begin to download Mod_Security and add a basic security scheme. Mod_Security will be added to Apache configuration file which is located at /usr/local/apache/conf/, and will include its main security configuration file which can be found at /usr/local/apache/conf/modsec.conf

That’s it. mod_security is now installed on your server. Now, all that is left for you to do is to edit and add security filters.

You can edit Mod_Security as configuration file either through Web Host Manager, or from shell (SSH).

Web Host Manager
Once the installation has been completed, a new section will be added to WHM by the name of Add-ons. Scroll down on the left frame until you see it, and click on the Mod Security link.

Note: If you are still logged to your WHM and don’t see the Add-ons section, try refreshing your browser.

Shell
cPanel includes three configuration files: modsec.conf, modsec.user.conf, and modsec.user.conf.default.

The ones that are in effect are modsec.conf, and modsec.user.conf. The file modsec.user.conf is blank by default, however, modsec.user.conf.default contains common security filters which can be applied to modsec.user.conf.

I recommend viewing modsec.user.conf.default before copying, and applying any security filters. Misconfiguration can do more harm than good.

Hope you all like this post

when you log into the SSH server, it will do a reverse DNS lookup of the client for security reasons. Thats why it takes a time to login.

vi /etc/ssh/sshd_config (and add the below line:)

UseDNS no

So enjoy SSH