Easy BasicAuth in Python (at least with Twitter)

Being slightly ADD I tend to be the kind that starts lots of projects. Reversing projects, webapp projects, coding little utilities I've wanted, even rewritting pieces of code that other people have already written just for my own education. Sadly that also means that when I get hung up on something it's easy to push it aside, not finish it, and work on something else. It's been a personal goal recently to complete a bunch of these 3/4 of the way complete projects before I start the multitude of new one I have in mind.

One of these has been a Python Twitter client/libary. Something to hook when I want to access Twitter for some of my other projects and to use for CLI Twitter access, being a Terminal nerd like that. Basic enough, it was before I'd been writing a lot of code, I wanted to work with a web API of some kind, and it helps that I know the guy who maintains the Twitter API in case I ever have questions. My implimentation has been pretty straight forward, the API is easy to use, documentation very through, and I got everything together with just one little (little being used sarcasticly) issue: authentication.

BasicAuth is straight forward enough. Seemed simple. Yet after reading more than a dozen documents, reviwing code in a number of other applications, and reading the urllib2 spec a number of times I could never successfully authenticate. Finally I stumbled across someone else who had the same issue, and found the answer in httplib. After playing around with his code the following works:

#!/usr/bin/env python

import sys, os
import httplib, urllib, base64

class BasicAuth():
    def __init__(self, username, password, url):
        """Builds class. Creates authentication and connection objects."""
        self.authentication = { "Authorization": "Basic %s" % base64.encodestring("%s:%s" % (username, password)).strip() }
        self.connection = httplib.HTTPConnection(url, 80)
   
    def get(self, path):
        """Generates and executes authenticated GET request."""
        try:
            self.connection.request("GET", path, urllib.urlencode({}), self.authentication)
            response = self.connection.getresponse()
        except:
            print >> sys.stderr, "Get Request: Failed"
        else:
            return response.read()
   
    def post(self, path, type, content):
        """Generates and executes authenticated POST request."""
        try:
            self.connection.request("POST", path, urllib.urlencode({ type: content }), self.authentication)
            response = self.connection.getresponse()
        except:
            print >> sys.stderr, "Post Request: Failed"
        else:
            return response.status, reponse.reason

I don't know exactly why the httplib method works so easily and the urllib2 method constantly failed inspite of my constant efforts. Thankfully the rest of the code I'd written worked flawlessly. It's got a few more hours of cleanup, but I'm hoping to have it ready for release this week. Until then, here's working, easy, BasicAuth for your Python based enjoyment.

The Alpha Hacker Dilemma

Watch enough cliche movies about growing up and it becomes quite obvious that, at least in Hollywood, a guy growing up has a choice to make: be an Alpha male or not. I'm not sure of the science behind it, though I know in many primates there is some truth to this, but I think it's safe to say there is something of a divide. According to Encarta (yeah, I was surprised it's still around too):

al·pha male (plural al·pha males) noun  

Definition:   

1. dominant male animal: a male in a pack of wolves, or a similar pack or troop of animals, that other members submit to and follow and that takes priority in mating with females 

2. dominant man: a man who controls the activities of a group and to whom others defer ( informal ) 

In typical society the alpha male is confident, athletic, probably good looking, the guy who gets the girl, who can do anything. Experience tells us this is largely a mask, underneath it they're likely very different, a scared little puppy, but that's the perception. There is often an inner drive and societal encouragement to be the alpha male; or at least the supposition that getting what you want in life, be it fame, money, or women will be easier as the alpha male.

In the culture of folks who do IT there is definitely the concept of the alpha geek. This is the guy who disdains Windows, these days likely uses OSX or Ubuntu, but there was a day he rolled his own Linux distro or perhaps used Gentoo and took pride in the fact that he complied everything from source. He's the guy you go to for answers, who can do binary/hex/octal conversions in his head, and has coded in every language under the sun. If it's worth knowing he likely knows it.

This trend gets even more specific: The alpha hacker. While others are content to use Metasploit or wait for PoC to be released, he writes his own exploits and probably has a stack of 0days "just in case" but would never release them. He is the alpha geek with a malicious twist. He can debate the various debuggers/disassemblers, and knows exactly who he prefers IDA Pro to Softice. He walks around Defcon with an air of superiority, though without condescension, because while your neat new XSS or IDS evasion technique is cute it will be patched soon, and there's no patch for what he is capable of. You patch the exploit he used yesterday? Fine, he has more sitting around just waiting, and the day he runs out of them he'll just take a weekend or two and write a few more. He is the attacker you don't stop; you can try to frustrate him, attempt to piss off him, annoy him enough to get him to go for a weaker target, but he can't be stopped, not 100%. He's the kind of hacker the script kiddies wanna be like, at their keyboard every night, codin' in the glare of the monitor light.

It is at the impasse of this that I find myself. I am competent, I am in fact quite good as a hacker/security professional. I understand the attacks, I know their defenses, I can execute many of them. I've presented at a few security conferences, and hold an important position with a leader in the information security field, protecting hundreds of other companies. I am in a prime position in many ways. The biggest question at this point is the route to take: the alpha hacker's path or the security professionals path. 

Following the first path is a trail of reverse engineering, vulnerability research, coding, reading assembly, and attempting to own everything in sight. This position will earn the respect of many others in the industry, the chance to do important work that directly influences the actually security of those using the Internet, perhaps even the security of countries. This is the path of technician, the operator, the person creating the technology. This comes with a price, a ceiling. This isn't a ceiling of creativity, or acclaim, or glory; those things can be continuously earned every year. It is a monetary ceiling. Technicians are, by their very nature, a dime a dozen, and even at the top there may be many others striving to the same heights, and the alpha hacker is only as good as his last program, his last hack, his last vulnerability. A big payday, from this position, is rare.

Along the other path is little more technical knowledge, instead focusing on how to apply technology, integrating solutions, and selling products. It is the path to sales, management, and consulting. It's not about deeply knowing the technology, it's about superficially knowing much and being able to sell it. It is the path that is about knowing people and businesses. It rarely holds the glory of the alpha hacker, rarely the respect from those on the front lines. It does provide the chance to win the respect of the decision makers and C-Level execs, and as a result has the possibility of a big payday, either as a part of a sales team or working with a smaller company as an entrepreneur. 

Personally I'm torn. I have a passion for technology, and I love knowing the things no one else knows. The idea of learning to be the unstoppable wraith that is the worst nightmare of someone defending a system, and who is able to understand what applications are doing at the deepest levels, and understanding how to take advantage of it. On the other hand I am a people person, I converse well with others, both technical and non technical, and can explain complex concepts in simple ways, and I'm sure with a little bit of work would have no problem explaining and selling solutions. I'm on the cusp, able to go either direction, sales engineer or reverse engineer, and I simply don't know. i

In many ways this is even more fundamental, it's the question of what's more important, doing what you love or doing what pays the bills? Is it worth enjoying your time at work a little less to enjoy your time away from work a little bit more? I don't know, but I'm starting to wonder if there's a third option...

InfoSec vs. Coding

The job hunt is a long and onerous thing, full of hope, trepidation, and frustration. It's somewhat bizarre how it can all work out. Jobs that I've wanted haven't returned my emails, jobs that I never wanted have insisted on interviewing me (and in fact flying me out to the West Coast to meet with them) have turned out to be poor matches, just as I originally thought they were. Most notably recently, the job I was somewhat interested in, that turned out to be something completely different, that gave me an offer I never expected.

Sadly though I find myself, at least at this moment, somewhat disenchanted with infosec as a career. I know it's temporary, it always is, but that's where I find myself now. Security is an uphill battle, our successes are par for the course and hardly ever recognized, our failures are monumental catastrophes with dire consequences. It often feels in many ways you can never do anything right, only avoid mistakes. I don't think this feeling is unreasonable, simply the state of things. The only way to "win" the security game is to be someone breaking, not protecting.

I find, as a result, I rarely know what I want to do in security, a question I'm asked often, as you'd expect. Developing exploits sounds fun, but I haven't done it before, and the barrier to entry feels high, though I'm trying, at least on and off, to learn it. I have a certification in Incident Response, but I've never done any of it, though I feel like I should, so that's a draw, but again, it's essentially a janitors position, cleaning up others messes. General consulting is a mixed bag at best, fun and interesting one day, but dull and monotonous the next, though the money is often desirable. I know one thing I don't want to do is continue in the security monitoring area, it's too limited, like seeing someone about to get mugged, but being unable to do anything except yell at them to run, knowing they probably won't hear you.

I'm not saying it's driven me to it yet, but I totally understand why my friend al3x has moved from doing security work to building great software like Twitter. I can see the appeal of creating something, nurturing it, having it become something good, and winning, in some small way, a victory in seeing an idea become a reality. I haven't decided to make any moves out of information security, not close, but I admit many hours I used to spend trying to learn assembly (for reversing) or C (for writing exploit code) are now trying to work on skills to build my Python or Cocoa coding. I know all of these things are self supporting, knowing assembly will make me a better Cocoa coder, and python skills will be useful in infosec, but still, it's something of a shift in priority.

In short; I don't know. I'm frustrated and confused, but I know I'll work through it.