Abstract information here:
https://www.defcon.org/html/defcon-17/dc-17-speakers.html#Dixon

I haven't released too much information on the Carrier Pigeon project, but that was due to the nature of the vulnerabilities identified. Though they are small, they can pack a big punch and I did not want to reveal the information without first giving vendors the heads up.

It was just recently that I was tasked with creating a simple SharePoint site that had multiple subsites. Some subsites would require access control using all the same groups while others would use a combination of groups and users. The site itself was already built and I viewed the task as being something trivial to do within SharePoint.

For those (if any) who read my blog, you may have noticed that posting has been pretty sparse lately. That's not to say I have not been documenting (because I have, trust me), but I have been pretty busy finishing up Carrier Pigeon project. As of now I have 3 functioning tools and a rough draft of the final research paper.

The Synthetos website is an effort for spreading the python message, providing collaborative python development of security products and lastly a personal 'notepad' for Riley Porter's Ubuntu Linux fixes and hacks. Check it out.

www.synthetos.com

Last month (and I guess technically last year) I started a quick project to make a Python class that someone could use to calculate the CVSS V2 score based on the many variables that CVSS takes into account. It took me a few days to get everything working, but as of now a class has been created that can take in the required variables or the CVSS string itself.

WSS by default allows 50MB files as its maximum upload. This works for some, but for others like myself, I needed it to be increased. I found plenty of blogs online to make this happen including this useful Microsoft document (http://support.microsoft.com/kb/925083), but it lacks one specific step that I needed - It and many of the other blogs only take into account WSS 2.0 and not 3.0.

For anyone who develops with Python on Windows this post is for you. There appears to be a bug in the Windows version of IDLE that caches your code upon executing it. This is a problem because users may use IDLE to continually test their code as changes are made. This is exactly what I was doing when this issue occurred. I made changes to my code and hit F5 to run it through IDLE.

Back in April of this year I was asked to help out with some testing on several networking devices. The devices I was setup to test were my Cisco routers, switches and access points. The goal of the testing was to identify whether or not malicious input could be used as a device's name.

As of right now, to submit documentation one has to create a blog entry and fill describe their solution to some problem. They can then upload their files and post the blog accordingly. This works fine, but the content type, blog, does not really fit for posting documentation.