http://www.google.com/codesearch
The Google Code Search team has just announced support for AppleScript, COBOL, ColdFusion, Haskell, Modula-2, Modula-3, OCaml, R, Rebol, SML, and VHDL. You can select them on the advanced search page or with the "lang:" operator. Other languages are supported with a bit more work:
The search company’s latest offering, a source-code search tool labelled Code Search, could well be misused by crackers. Although the tool aims to simplify life for developers, it could be used by attackers to search for bugs in software, password-related information, and proprietary code that shouldn’t have been up on the Internet in the first place.
The source-code search engine was unveiled on October 6, 2006. Unlike the company’s ubiquitous Web search, the Google code-search analyses actual lines of code as and when it finds source-code on the Internet. This will help developers to search source-code listings directly, and, in the case of open-source code, build on existing code snippets to create new applications that might not have been created quite as easily if not for the existence of this search engine. With these benefits comes the drawback that the service can be used to search for code that is vulnerable, such as examining code for vulnerabilities in password mechanisms.
Although skilled hackers may be able to do this kind of search with a conventional search engine, Code Search offers an easier way out.
Another aspect of the matter is that organisations backing up their files should avoid using http to transfer them (basically they should avoid posting code onto even internal Web sites) for there’s always the off-chance that someone may accidentally upload code into a directory that outputs its contents, so before you know it Google Code Search might have indexed your enterprise’s crown jewels. Placing the archives out of the Web root and using Secure Copy (SCP) or a secure FTP client is a much better idea.
Google, of course, defends itself. It claims that proper security procedures, if followed, will ensure that there are no problems.
The source-code search engine was unveiled on October 6, 2006. Unlike the company’s ubiquitous Web search, the Google code-search analyses actual lines of code as and when it finds source-code on the Internet. This will help developers to search source-code listings directly, and, in the case of open-source code, build on existing code snippets to create new applications that might not have been created quite as easily if not for the existence of this search engine. With these benefits comes the drawback that the service can be used to search for code that is vulnerable, such as examining code for vulnerabilities in password mechanisms.
Although skilled hackers may be able to do this kind of search with a conventional search engine, Code Search offers an easier way out.
Another aspect of the matter is that organisations backing up their files should avoid using http to transfer them (basically they should avoid posting code onto even internal Web sites) for there’s always the off-chance that someone may accidentally upload code into a directory that outputs its contents, so before you know it Google Code Search might have indexed your enterprise’s crown jewels. Placing the archives out of the Web root and using Secure Copy (SCP) or a secure FTP client is a much better idea.
Google, of course, defends itself. It claims that proper security procedures, if followed, will ensure that there are no problems.