News for hackers. Stuff that matters.
Re:WordPress base configuration files on GitHub by mattgibson on Monday August 17, 2015 @09:50AM (#10072926)
Excluding localhost and some obvious cases where the values are in a local config file still leaves around 111,000:

https://github.com/search?p=1&q=filename%3Awp-config.php+DB_...

Re:WordPress base configuration files on GitHub by onion2k on Monday August 17, 2015 @10:09AM (#10073037)
localhost in the case of Wordpress just means the database is running on the same machine as the web server. Practically every WP instance is set up that way.
Re:WordPress base configuration files on GitHub by panopticon on Monday August 17, 2015 @10:32AM (#10073196)
> localhost in the case of Wordpress

Uh, the concept of localhost is not unique to Wordpress in the slightest.

Re:WordPress base configuration files on GitHub by erikb on Monday August 17, 2015 @10:47AM (#10073323)
That's not what he meant. What he meant was reading that the database is on localhost doesn't mean it's a development system. Many production instances of Wordpress run the database on the same host. Therefore localhost can also mean production. That might not be true for other services, but for Wordpress that's common. This is what he meant.
Re:WordPress base configuration files on GitHub by sarciszewski on Monday August 17, 2015 @10:02AM (#10072989)
Excluding localhost will exclude a lot of legitimate installs.
Re:WordPress base configuration files on GitHub by austenallred on Monday August 17, 2015 @10:03AM (#10072997)
Most wordpress devs support multiple environments in their .wpadmin (dev -> localhost, prod -> some server). So this is creating a lot of false negatives.
Re:WordPress base configuration files on GitHub by bdcravens on Monday August 17, 2015 @10:47AM (#10073328)
Which would be 99.99926% :-)