Comments on: Google’s Code Search http://illyana.com/2006/10/05/googles-code-search/ Fri, 21 Nov 2008 08:35:23 +0000 http://wordpress.org/?v=2.0.4 by: Adam http://illyana.com/2006/10/05/googles-code-search/#comment-1001 Sat, 21 Oct 2006 18:40:13 +0000 http://illyana.com/2006/10/05/googles-code-search/#comment-1001 I use wordpress, and I had some concerns about this but here's why it shouldn't be a big deal for most: 1. The MySQL useer/pass in stored in there - not your user login 2. The MySQL DB should be locked down and not accept connections from random IP's so this shouldn't be too much of a concern even if it does leak (you don't use the same pass for MySQL as login do you?) Finally, you can fix this if you move the various variable declarations to a separate file outside the web root and then use and include statement to bring them back into the WP code. Of course, this makes upgrades a little tricky.... I use wordpress, and I had some concerns about this but here’s why it shouldn’t be a big deal for most:

1. The MySQL useer/pass in stored in there - not your user login
2. The MySQL DB should be locked down and not accept connections from random IP’s so this shouldn’t be too much of a concern even if it does leak (you don’t use the same pass for MySQL as login do you?)

Finally, you can fix this if you move the various variable declarations to a separate file outside the web root and then use and include statement to bring them back into the WP code. Of course, this makes upgrades a little tricky….

]]> by: techrageo.us http://illyana.com/2006/10/05/googles-code-search/#comment-846 Mon, 09 Oct 2006 05:48:20 +0000 http://illyana.com/2006/10/05/googles-code-search/#comment-846 <strong>Security and Google Code Search</strong> If you use WordPress be careful. An example Google Code Search search going around is “username file:wp-config.php” which happily displays username and passwords in WordPress config files… if they’re in compressed archives or a ... Security and Google Code Search

If you use WordPress be careful. An example Google Code Search search going around is “username file:wp-config.php” which happily displays username and passwords in WordPress config files… if they’re in compressed archives or a …

]]> by: Mal http://illyana.com/2006/10/05/googles-code-search/#comment-829 Fri, 06 Oct 2006 13:32:28 +0000 http://illyana.com/2006/10/05/googles-code-search/#comment-829 I say "reg ex", but only cause I can't do complicated words like "reg expththt" I say “reg ex”, but only cause I can’t do complicated words like “reg expththt”

]]> by: Jack http://illyana.com/2006/10/05/googles-code-search/#comment-828 Fri, 06 Oct 2006 13:31:01 +0000 http://illyana.com/2006/10/05/googles-code-search/#comment-828 The explanation I prefer is that Google figures that we don't really care about the the 3rd page of results, let alone page number 2 million, so they cheat a little when they give their number of results. The shortcuts they take are for performance reasons, so I'd speculate that it's a lot faster, and therefore more accurate, to find "x" than it is to find ".*". The explanation I prefer is that Google figures that we don’t really care about the the 3rd page of results, let alone page number 2 million, so they cheat a little when they give their number of results. The shortcuts they take are for performance reasons, so I’d speculate that it’s a lot faster, and therefore more accurate, to find “x” than it is to find “.*”.

]]> by: Mal http://illyana.com/2006/10/05/googles-code-search/#comment-827 Fri, 06 Oct 2006 13:29:00 +0000 http://illyana.com/2006/10/05/googles-code-search/#comment-827 I can't tell you exactly why it happens, but I can speculate as to why Google doesn't worry about it. There's a combination of factors, but essentially it's this: Google prefers performance, reliability and relevancy over accuracy and data consistency. The search results on the first page have to be fast and relevant, every page after that diminishes in importance. You see Google make this kind of choice all the time, a great example is the lack of folders and IMAP in GMail. you get performance and relevancy from your mailbox, even if it's not presented in the most structured manner. I can’t tell you exactly why it happens, but I can speculate as to why Google doesn’t worry about it. There’s a combination of factors, but essentially it’s this: Google prefers performance, reliability and relevancy over accuracy and data consistency. The search results on the first page have to be fast and relevant, every page after that diminishes in importance. You see Google make this kind of choice all the time, a great example is the lack of folders and IMAP in GMail. you get performance and relevancy from your mailbox, even if it’s not presented in the most structured manner.

]]> by: Caz http://illyana.com/2006/10/05/googles-code-search/#comment-825 Fri, 06 Oct 2006 11:59:15 +0000 http://illyana.com/2006/10/05/googles-code-search/#comment-825 regexps? I know what it means but how the hell do you pronounce it!? regexps? I know what it means but how the hell do you pronounce it!?

]]> by: Rowan http://illyana.com/2006/10/05/googles-code-search/#comment-822 Thu, 05 Oct 2006 22:56:05 +0000 http://illyana.com/2006/10/05/googles-code-search/#comment-822 Any idea why they estimate more hits for 'x' than '.*'? Any idea why they estimate more hits for ‘x’ than ‘.*’?

]]>