SteveManorGoogle Hacking evolve (alert system)-

Tuesday, August 3rd, 2010

Google hacking is getting a reboot. Researchers dig through the search engine with specialized queries in order to locate vulnerabilities on websites.

At the Black Hat security conference, researchers Rob Ragan and Francis Brown from security firm Stach & Liu, detailed their new efforts for hacking both Google (NASDAQ: GOOG) and the Microsoft (NASDAQ: MSFT) Bing search engine. The new tools and techniques are intended to provide a rapid alert system for enterprises to help identify risk within their organizations.

The GoogleDiggity and the BingDiggity projects, these are the tools that enable users to perform security research with pre-built query strings to locate common vulnerabilities. The GoogleDiggity tool uses the Google AJAX API and Google’s custom search to deliver results.

Ragan noted that back in 2004, researcher Johnny “I Hack Stuff” Long created a Google Hacking Database, which included queries that could be used to detect potential security issues. Ragan and his colleagues are now using a similar idea to build a Bing Hacking Database for vulnerability search queries using Microsoft’s search engine.

Brown noted from an enterprise scalability perspective that it’s not practically feasible for companies to periodically Google hack themselves. But for an enterprise, it is important to have a way of knowing when they have some kind of vulnerability or information leakage as soon as possible, he argued.

The researchers have leveraged their Google hacking work to create search-engine-powered back alerts. The approach is similar in scope to the Google Alerts system in which users select a keyword and are then sent emails or RSS updates whenever new instances of that keyword are found.

Ragan said, “What we did is we imported our hacking query database into Google and Bing hacking alerts”. “So we’re looking at over 2,300 queries and getting updates via RSS as they happen.”

Brown noted that the hack alerts system will be made available as an OPML file so that others can simply import the RSS feeds into a feed reader.

In an effort to help enterprises scale and customize the hack alerts, Ragan said that his team is working on a Google desktop gadget as well.

Tags: , , ,
Posted in Database, Technical News

BobbyeM71hxwCHKDSK/F Fails to Fix File System Problems

Monday, May 31st, 2010

One of the most common reasons for unbootability of the computer system is the file system corruption in Windows XP. And for damage in file system, the reasons responsible for that are unexpected system shutdown (due to power outage or human mistakes), virus infection, MFT (Master File Table) damage, and more.

In order to get past the corruption issues in a Windows XP system is by executing CHKDSK/F command. This command checks the physical and logical integrity of the file system and repairs it in case of any damage.

Though the command, in most of the situations, is a life-saver, but do not guarantee 100% success in every life system corruption issue. In such cases, when the CHKDSK command fails to repair, an ideal alternative is to reinstall Windows XP and restore data from an updated backup. However, in case no backup is available, the user can easily recover data using a commercial Windows Recovery application.

Let’s consider a practical scenario that explains the above situation. You encounter the below error message at the startup of Windows XP operating system:

“C:\$MFT is corrupt and unreadable. Please run the chkdsk utility.”

After the above boot error message pops up, your system becomes unbootable and its data gets inaccessible. As suggested in the error message, when you run CHKDSK utility, you encounter another error message:

In the master file table (MFT) bitmap, CHKDSK discovered free space marked as allocated. CHKDSK discovered free space marked as allocated in the volume bitmap. Windows found problems with the file system. Run CHKDSK with the /F (fix) option to correct these.

As error message suggest, when you execute CHKDSK utility with ‘/F’ parameter, it shows the same error message. Since the system could not be started, the data saved in the Windows based hard drive remains inaccessible.

Resolution: In order to overcome the CHKDSK/F failure error message, follow the step mention below:

1. Reinstall Windows XP on your system.
2. Restore the data from an updated backup. In case no backup is available, use a commercial Windows Data Recovery utility.

Such windows data recovery tools use effective recovery techniques to perform complete recovery of all formatted files and folders.


Tags: , , , , ,
Posted in Database, Purely Technical

LolaTheriotHow to resolve the error 2537 in SQL Server 2000?

Wednesday, May 19th, 2010

While mounting the database, it could be frustrating to view an error message, which not only results in unmountability of the database, but also in inaccessibility of database records. Such error messages can be caused due to database corruption. Some of the few main reasons responsible for database corruption are metadata structure damage, network issues, hardware malfunction, improper system shutdown, and virus infections.

In order to overcome such error messages, the database administrator needs to run an inbuilt repair utility named ‘DBCC CHECKDB’. While this command is competent enough to repair a damaged SQL Server 2000 database, it might also result in loss of data from the database. To prevent any such data loss situation from occurring, you will need to repair the database by using a powerful MDF Database Repair application.

Lets consider a real-time scenario where you encounter a severity level 16 error message while trying to mount your SQL Server 2000 database:

“Table error: Object ID O_ID, index ID I_ID, page P_ID, row ROW_ID. Record check (CHECK_TEXT) failed. Values are VALUE1 and VALUE2.”

Once the above error message flashes on the screen, the database records become inaccessible.


Two main reasons liable for the occurrence of 2537 error message are discussed underneath:

  • A condition specified in the CHECK_TEXT statement could not be fulfilled.
  • The database table is logically or physically damaged.

Tips to Resolve:

To get past the above error message, an easy way is to restore the database from an updated backup. However, if in case backup is not available, and then repair the database using following steps:

  • In case the SQL Server 2000 database table is physically damaged, and then replace the physically damaged component with a new component. To determine the component that is physically damaged, check the system logs.
  • In case the SQL Server 2000 database table is logically corrupted, then run DBCC CHECKDB command with a suitable repair clause. While doing so, the logical corruption can be resolved, but it might also result in loss of data. To ignore such data loss situations, it is advisable to repair the database using a commercial MDF Repair application. Such MDF File Repair tools are totally non-destructive and keep the original file untouched while repairing.

Tags: , , ,
Posted in Database, Purely Technical