Tag Archives: IP

EFF's SSD (Surveillance Self-Defense) Project

EFF-logo-transEFF has a page covering what they call The SSD Project (Surveillance Self-Defense) which they provide, “…to educate the American public about the law and technology of government surveillance in the United States, providing the information and tools necessary to evaluate the threat of surveillance and take appropriate steps to defend against it.“  This is important stuff, and what I wish others would know, so I’m posting links to the source in the hope it will get more exposure and results in the search engines of the Internet.  I will contact EFF and see if we can formulate a better method to disseminate and distribute this text, allowing for updates and annotations going forward. Also, I aggregate news that cover these kind of issues over on Left to chance, take a look, then follow @lefttochance and @eff on Twitter to stay informed, and consider joining the LinkedIn EFF Group I run to join in the conversation.  In other words, get involved and …

Know  your  rights!

Dark Night of the Soul

Notice: the text of this post in the gray, blockquote area was taken from the website Look Into My Owl, and I forgot to attribute it to them. The reason I used a blockquote was to signify that it was a direct quote, and that it wasn’t mine, but I didn’t say it wasn’t, and didn’t put a link to the original work as I usually do. It was an oversight on my part, and I regret it.

The more I try to hurt you, the more it hurts me

Ah, just another line that revolves in my head after repeated listenings of the amazing Dark Night Of The Soul‘, the Danger Mouse and Sparklehorse (Mark Linkous) musical collaboration with David Lynch.

DARK NIGHT POSTER FINALai

HOWTO: log the user's IP, not the proxy's, in Lighttpd access log

Lighttpd - fly lightWhen you run a webserver behind a reverse proxy or HTTP accelerator like Squid or Varnish, the webserver access logs will display the IP of the proxy (generally 127.0.0.1) instead of the end user’s IP.  This not only breaks any kind of tracking or reporting you want to run against your webserver logs, but it also takes away a datapoint I’ve had use for in general server admin tasks. This server runs Varnish in front of Lighttpd, and it reveals the end user’s IP in the header as X-Forwarded-For, so it’s just a matter of making Lighttpd (lighty) use that variable in its access logs instead of the default variable defining the referring IP. Once we know that, the configuration is simple; in lighttpd.conf, enter this: