cca-bypass 0.5

by on Dec.04, 2009, under realbasic

Now this is what I call rapid development! One day of coding, and I have a new and much improved version of cca-bypass. This version still has two binaries, but it has my own sec_cloak_apply, instead of sec_cloak. Basically, sec_cloak_apply allows me to do some additional things with the code, backing up the registry values, and allowing you to restore them later. This could come in handy.

Other than that, the big improvement is the addition of a progress bar, and making the login process asynchronous. This means that there’ll be a nice little progress bar to show you how far along in the login process the task is. Note that it takes a second after you click “Login” for the task to start running.

Finally, there is a LOT more error checking in the Login process, so all errors should now be in plain English. If you DO encounter an error, and you think you shouldn’t have, please let me know, and I’ll do my best to fix it. I can’t test every situation! Anyway, on to the download links for version 0.5:

Pre-compiled binary: (2.39 MB)

Source: (38 KB)

Note: I’m still considering this beta because I haven’t been able to thoroughly test it. It should be pretty, stable, though, so don’t be afraid of the “beta”!

Leave a Comment :, , , , more...

cca-bypass beta1

by on Dec.04, 2009, under realbasic

For a while, Cisco Clean Access on Windows has bothered the heck out of me. The client for CCA on windows is just plain buggy. It takes forever to open, prompts me to let it run as admin every time I boot into Windows, doesn’t let me use the Internet until I update Windows (which sometimes requires a reboot first), and sometimes just doesn’t work. However, I’ve only recently decided to investigate more, and figure out how to get past it.

The idea is simple: on a machine running Linux, everything is done through a web interface. This makes it simple to create a script to get through Clean Access. However, on Windows, while this web interface is presented, it simply tells you to download the client. The obvious method of bypassing this, changing the User Agent of your browser, doesn’t work: Clean Access has other methods of detecting that you’re running Windows, using TCP fingerprinting. Basically, Cisco has figured out certain commands they can send over the network, and exactly how a Windows machine will respond. So, the answer becomes to change these responses. (continue reading…)

1 Comment more...

Looking for something?

Use the form below to search the site:

Still not finding what you're looking for? Drop a comment on a post or contact us so we can take care of it!

Visit our friends!

A few highly recommended friends...