- [DeepSec 2015]50 Shades of WAF
- [DeepSec 2015] File Format Fuzzing in Android – Giving a Stagefright to the Android Installer
- [DeepSec 2015]How to Break XML Encryption – Automatically
- [DeepSec 2015] Hacking Cookies in Modern Web Applications and Browsers
- [DeepSec 2015] Can societies manage the SIGINT monster?
- [LHS Microcast] DeepSec 2015
- [LHS Microcast] Interview w/ Jen Ellis
- Taking out the Eurotrash
- All good things must come to an end
- [DeepSec 2014] Advanced Powershell Threat: Lethal Client Side Attacks using Powershell
The contents of this personal blog are solely my own opinions and comments, as such they do not reflect the opinions of my employer(s) past, present or future. No legal liability is accepted for anything you do, think, or consider fact as the basis of articles and links posted on this blog.
"Three to one...two...one...probability factor of one to one...we have normality, I repeat we have normality. Anything you still can’t cope with is therefore your own problem."
Note: A large portion of content I post on my blog comes from "live blogging" of security conferences. These posts are in notes form and are written live during a talk. As such errors and emissions are expected. I'm only human after all!
What about pulling out referrers as well? May as well while you are at it.
It’s a thought…. was going to maybe look at the user agent strings too 😉
Added support for extracting basic auth usernames in 0.4
If you pull out the time and date it happened and the response code you could probably create a set of Apache logs 🙂
OMG… you’re so right…
I could just open the logfile…. and print out each line to the screen, Maybe throw some colours in for good measure 😉
Pingback: » Apache Log Extractor - CyberPunk