Tuesday, April 13, 2010

- Password Crackers

THC Hydra


For the last few months i have found myself relying on the only usable piece of hardware at my disposal, an old ass macbook. I have found using the mac simple and straightforward for simple tasks, such as internet access, email, using calculators and word processors, et cetera. I have also found using more advanced system functions, such as bios and command line functions much more difficult. I feels as though macintosh put safety locks on everything, much like childproofing a house, they have childproofed their operating system.

I have been around "fringe" software or software that exists along the border of legality and enforcability for some time now, and this is my first use of a password cracker tool. I started with a simple google search and came across a page listing all of the best crackers, each specialized for various functions. The two i chose to use were the two listed links above. I chose these two because i wanted easy mac use. I didn't want to be forced to screw around with drivers, as all of the varying hardware drivers, and software drivers, and mobo conflictions that are likely to erupt, just make me a sad panda. This task i found giving me a headache just thinking about, windows is so much more accessible for this more complex stuff.

After getting into the nitty-gritty of all of the stuff I needed to learn to use more windows friendly software on a mac, the first problem i cam across is that mac has no means to compile code. All of the password cracker programs i came across, brute forcers, WEP, and WPA password crackers, all require compiling. In layman's terms, compiling is turning programming code into a workable and usable file, it turns people code, into computer code. Apple has on their main sight all of the files they think a typical user has to have.

After creating a specific "designer" account and re accessing the sight, cruising through clumsy web design and finally finding the download link i needed, downloading, and installing I was finally able to use the actual software i wanted to use, or so i thought. 

After spending some time screwing with UNIX commands that I now realized i should learn if i want to take this seriously, I came to a new conclusion. I needed to change my wireless card driver. Something that discouraged me from the start. After looking into the problem a bit more, it turns out that the feature i needed to use from my card, packet sending, is disabled by corporate mac. Disabled meaning, has complete functionality but is purposely handicapped by the developers.

With a little more digging it turns out that the way to change the functioning of the wireless card is available and usable, but is only available for firmware designers at apple.

In summary I have found that apple for the sake of improving the daily use for the typical user has sand-bagged the whole experience for a more adept user. It feels less like apple is helping me by pointing me in the direction of more stable processes, and more like i'm a grown man who has spent his own money buying a product i don't even have full rights to. This whole experince has just re-entrenched me into my staunch offense on apple's distribution (lack thereof) of dumbed down hardware and software.

If you have any confidence in your ability to use a computer or program, and are curious about either of those things, stay the fuck away from apple.

No comments:

Post a Comment