News for hackers. Stuff that matters.
Re:Monitors.txt - lazy webapp monitoring by cheald on Saturday November 05, 2011 @05:34PM (#3200985)
Not true. I can have a service monitor "http://foo:[email protected]/password/protected/endpoint/ or "http://mysite.com/protected?auth_token=2caf5e77cfa057ad2f36e... just fine.

Passwords are security by obscurity, sure, but putting them in a world-readable file at a common known location is the height of ridiculous.

Re:Monitors.txt - lazy webapp monitoring by icebraining on Saturday November 05, 2011 @05:38PM (#3200996)
Then you can put monitor.txt behind that password protected endpoint too. My point is that whoever you need to give access to the file also has access to the actual website, which has all the information (it has to, since it's supposed to be able to test against it).