News aggregator
CCCKC CNC 101
The title says it all. CCCKC now has an operational, home built, Joe’s CNC (2006 Model). The below video is the maiden cut.
At our Thursday meeting this week our resident CNC guru, Craig B., gave a primer for members and guests alike. That overview video can be viewed here (50 mins). Members will have to be trained and certified before being allowed to operate the machine. Stay tuned for information about future training opportunities.
Micro TV-B-Gone This Weekend!
We’ll be building the kits on Saturday February 19th Starting @ ~2:00 PM.

Only 20 kits are available so make sure you’ve contacted atomicc@ccckc.org to reserve yours. Kits are $4. If you have a soldering iron you can bring please do, we only have a limited number in the space.
The kit’s are based on this instructable.
February Turbo talks.
Click here to see our ustream of February’s turbo talks.
Whats up in 2011
CCCKC will be participating in the first Kansas City MAKER FAIRE. It will be held at Union Station.
More details to be released soon!
Mean while at CCCKC, Tom Collins and company has begun work on the CCCKC MAME cabinet.
From Jan2011
While doing so Joel hacked a drink bottle into a shotglass for the espresso machine.
From Jan2011
From Jan2011
The Fabricators group has been very busy at CCCKC advancing the capabilities of the maker bot and RepRap Mendel’s.
From Jan2011
An evite from Surbo?
Building 2D Movie Glasses
If you've watched a 3D movie, You've probably taken your glasses off in the middle, only to see a double-vision mess caused by being able to perceive both video channels at the same time with both eyes. Watching a movie this way is likely even more frustrating than enduring the side-effects of 3D.
Obviously, I'd suggest not seeing movies in 3D if you are prone to these side-effects, but perhaps your group of friends just HAS to see this movie in 3D, or maybe your schedule makes it more convenient to see a 3D showing. Here, I'll show you how to take two normal pairs of disposable RealD glasses and hack them so that your eyes only see one of the two video channels, effectively stripping the 3D effect from the big screen. The sad part: you still have to wear the stupid glasses.
There are several families of 3D video. RealD(tm) is currently the most commonly deployed 3D cinematic technology, and it uses something called circular polarization. Some of you might be familiar with polarized lenses used in sunglasses and camera filters. Those are usually linear polarizers. Linear polarizers are also used on LCD screens and have a number of other commercial applications. It would be possible to show movies with the left and right channels polarized linearly at right angles to one other, but this would force moviegoers to hold their head in such a way so that the lenses remained perfectly level, or else video brightness and channel separation would fall to pieces, although brightness always suffers a little when using polarized lenses.
Circular polarization works similarly, but the light is polarized in a helical fashion. This is a much more complicated process that solves several of the problems with linear polarization. One channel is polarized in a clockwise helix while the other channel is polarized counter-clockwise, allowing the lenses to filter out the other channel without being constrained the way linear polarizing lenses would as I mentioned above. The easiest ways to demonstrate this are to look through a pair of these disposable goggles and into a mirror, or look at one pair of 3D glasses through another pair. Apologies in advance for using crappy camera phone pictures for this. It's all I had on hand.



You would think all we have to do is take one of the lenses out and flip it over, so that both lenses only show the clockwise or counter-clockwise channel. I thought so too, but there seems to be more at play than I suspected and that won't work. Edit: each lens contains two filters bonded together, a polarizer and a "quarter wave plate", and flipping one lens over puts these filters in the improper order.
You'll have to tear into two pairs of 3D glasses, but the good news is that you can make two pair of 2D glasses out of them and give one to a friend. In a pinch, you could probably do all of this right there in the theater with nothing more than a simple Classic Swiss Army Knife. I'd recommend making these ahead of time, though.
If done correctly, this will get rid of most of the artifacts of stereoscopic cinematography, and hopefully relieve any side effects you might suffer.
RealD frames are snapped together in two pieces. With a small screwdriver, knife or other prying device, you can separate the inner part of the frame. We just need the lower part of one side of the frame to come apart far enough to slip the lens out.

Slide the lens out of the frame, being careful to not scrape it up.

Perform the two above steps on the opposite lens of the second pair of glasses.
Using scissors, trim the thin lens material so that you can fit each lens into the "wrong" side of the other frame. Don't trim so much that it's prone to fall out of the frame, but trim enough that it won't bend or crease when you put it back into the frame.

Carefully slide the lens into the other frame, being sure it slides into the thin slot snugly. Remember, we're taking the left lens of one frame and putting it into the right side of another frame, and/or vise versa. You don't really need to put the second frame together if you only need one set of 2D glasses.

Snap the frames back together, then wipe the lenses clean, as they're sure to have fingerprints all over them.


If you did it right, you should see that the movie looks the same through both eyes, and that looking at yourself in the mirror shows both dark lenses through both eyes, instead of just the lens you're looking through being dark.

We are proud members of the Security Bloggers Network.
This content originally posted on HiR Information Report. Copyright © 1997-2010, HiR
Introduction to encrypted Internet chat
This post was made mostly to go along with a quick presentation I'm doing for Cowtown Computer Congress this evening. This is a quick and dirty rough draft that will likely be edited for speling and grammer err0rz.
SILC is Secure Internet Live Conferencing, and it borrows many things directly from Internet Relay Chat, fixing some of the weaknesses of IRC by using certificates, key exchange algorithms, digital signatures and encrypted connections. The end result is a chat platform capable of being used by groups or one-on-one communication where you can be absolutely sure you are communicating with the person you think you're communicating with. With the appropriate measures, you can also be certain that messages can't be trivially intercepted or forged by outsiders, even if the SILC server or network has been compromised. When talking in public groups (equivalent to IRC channels), only those in the group can see the messages due to a shared session key. People sniffing your local network segment won't know what's being said or with whom you're communicating.
While on the topic of encrypted chat, I'll also discuss Off-The-Record, a cryptographic plug-in that sits on top of certain instant messaging platforms (like AIM) by sending strong-crypto messsages over base64-encoded strings between users. To this end, it's usually easy for someone monitoring the network to tell with whom you're communicating, but nearly impossible to determine the actual contents of said communication.
Of course, some of these things have been recently been addressed, albeit not nearly as thoroughly, by using SSL/TLS. Several modern IM protocols rely on SSL/TLS, and certain IRC implementations also can use SSL now. These are beyond the scope of this article, but worth mentioning in passing.
There are two actively-developed clients that I will cover:
- A SILC plugin for irssi, a popular IRC client, which works best on Linux
- Native SILC support in Pidgin IM, which works on Mac OS X, Linux and Windows. Pidgin plugins for Off-The-Record exist for Mac OS X, Linux and Windows as well.
Irssi is my favorite IRC client. It's a curses-based program that runs in the terminal. The SILC plugin for irssi can be found in many package repositories. For example, installing it (and all dependencies, including irssi itself) in Ubuntu is as easy as:
$ sudo apt-get install irssi-plugin-silc

If you're familiar with IRC, it uses some familiar derivatives of commands:
Load the SILC plugin, prompts for your private key passphrase
/load silc
Connect to a SILC server
/connect -silcnet SILCnet [silc-server]
Join a group (or channel)
/join [group]
Grant operator status to a user in a group you control
/cumode [group] +o [user]
Send a one-on-one message to another user
/msg [user] [message]
To compare, this is a screen shot of captured traffic from plain-text IRC, followed by one from SILC.


Pidgin
Pidgin is a cross platform open source chat application that natively supports all the major Instant Messaging protocols, including AIM, SILC and IRC. Once you've added a SILC server (via Accounts), you simply go to the Buddy List and select "Add chat" to join a group.

Off-The-Record
Adium, the Pidgin port for Mac OS X comes with OTR built right in!

Installing on Ubuntu is easy, as this will install Pidgin and the OTR plugin and all dependencies.
$ sudo apt-get install pidgin-otr
To get it up and running on Windows, first install Pidgin, then run the OTR plugin installer.
On Linux and Windows, you'll have to enable the plugin and generate a key before you can use it.


And then, once you initiate a chat with someone who also has OTR, you will need to verify their key. The best way to do this is in person or over a trusted communications platform. If you know their voice well enough, a phone call would probably work just fine.

Although AIM uses SSL by default these days, it's not uncommon to see AIM go across the wire in cleartext. Here's a screen shot comparing packet captures from a cleartext AIM session and one using OTR. You can't see it in the screen shots because of how large the OTR message is, but the OTR session only encrypts the message content itself. You can still see the names of the parties communicating.


That's all I've got for now.
We are proud members of the Security Bloggers Network.
This content originally posted on HiR Information Report. Copyright © 1997-2010, HiR
Links: 2010-12-14
#tags: hackers metasploit
#tags: hardware hacking opensource music programming
#tags: infosec opensource OpenBSD vpn infiltration
#tags: defense pdf windows
We are proud members of the Security Bloggers Network.
This content originally posted on HiR Information Report. Copyright © 1997-2010, HiR
Links: 2010-12-08
#tags: forensics linux infosec privacy
#tags: locks lockpicking physicalsecurity humor fail
#tags: locks security automotive lockpicking physicalsecurity
#tags: dos oldschool software
#tags: cartoon humor
We are proud members of the Security Bloggers Network.
This content originally posted on HiR Information Report. Copyright © 1997-2010, HiR
Links: 2010-12-07
#tags: movie video
#tags: virtualization virtualbox software opensource
#tags: pci compliance
#tags: defense weapons
#tags: makerbot fabrication ccckc hackerspace video
#tags: science measurements mechanics electronics
#tags: science biology chemistry
#tags: music movie
#tags: movie review
#tags: adobe pdf drm fairuse
We are proud members of the Security Bloggers Network.
This content originally posted on HiR Information Report. Copyright © 1997-2010, HiR
Links: 2010-12-05
#tags: irc mac osx software opensource
#tags: defense security infosec software tools freeware
#tags: socialengineering humor
#tags: humor
#tags: ne network security tools opensource dos networking hacking testing
#tags: piracy lawsuit electronics
#tags: privacy security internet opensource
#tags: microsoft tools freeware sysadmin
#tags: electronics soldering
#tags: politics wikileaks humor
We are proud members of the Security Bloggers Network.
This content originally posted on HiR Information Report. Copyright © 1997-2010, HiR
Links: 2010-12-05
#tags: irc mac osx software opensource
#tags: defense security infosec software tools freeware
#tags: socialengineering humor
#tags: humor
#tags: ne network security tools opensource dos networking hacking testing
#tags: piracy lawsuit electronics
#tags: privacy security internet opensource
#tags: microsoft tools freeware sysadmin
#tags: electronics soldering
#tags: politics wikileaks humor
We are proud members of the Security Bloggers Network.
This content originally posted on HiR Information Report. Copyright © 1997-2010, HiR
Automate posting links from Delicious to Blogger
Delicious has an "experimental" (as in, not maintained since 2008) "Blog Posting Tool" that simply refuses to work with Blogger, the platform we currently use. In fact, it's so arcane that I don't really know if anyone has ever really made it work on anything other than Wordpress.
I threw something together in PHP that uses the Simple HTML DOM library to parse the output of the Delicious API. One part of that library that broke pretty spectacularly at first was trying to grab the "tag" attribute of each element. Simple HTML DOM uses "tag" as a variable name all over the place, and it caused some major recursion. I used preg_replace to change the name of "tag" to something else to avoid this namespace collision.
It's written in PHP because I was originally planning on cooking up something web-based, but I went more lightweight instead. Who knows, maybe I'll re-write it later on. Perhaps perl, python, ruby or even newLISP would have been better for this. It's designed to be run manually from the command-line or (more specifically) a nightly cron job.
I just know that there aren't any easy-to-use solutions for posting Delicious links to Blogger, and a lot of people seem to want something like this. It's rough, has some vestigial debugging code left in it, and it's probably not easy enough for most folks. It does what I wanted it to do, though, and you'll probably be seeing a lot more frequent link posts because of it.
Source. Public Domain. Yadda yadda. Enjoy.
We are proud members of the Security Bloggers Network.
This content originally posted on HiR Information Report. Copyright © 1997-2010, HiR
Links: 2010-12-02
#tags: productivity work video leadership
#tags: gnome linux
#tags: robotics toys
#tags: linux virtualization sysadmin
We are proud members of the Security Bloggers Network.
This content originally posted on HiR Information Report. Copyright © 1997-2010, HiR
Links: 2010-11-29
We are proud members of the Security Bloggers Network.
This content originally posted on HiR Information Report. Copyright © 1997-2010, HiR
RepRap Mendel Progress
The RepRap Mendel I have been building at the hackerspace has just had its belts on motors attached. By hotswapping the stepper motor plugs onto the CCCKC Makerbot, I was able make the robot move for the first time! Here’s proof:
CCCKC Encryption talks and key-signing party
“There are two kinds of cryptography in this world: cryptography that will stop your kid sister from reading your files, and cryptography that will stop major governments from reading your files.”
— Bruce Schneier, Applied Cryptography
Drop by CCCKC on Saturday, November 13th 2010 to learn a bit about encryption and how to use it in every day life to keep your private life private.
Email asmodianx [at] cowtowncomputercongress.org for details.
More information at GNUPG.ORG
LANDSKETCH FOR HIGHWAYS
I’m excited to announce that we have released the second application in the LandSketch Series. This application is called LandSketch for Highways and is targeted at making the preliminary design process for corridors much more efficient. With this new product you can quickly layout many alternatives for your possible corridor and immediately check your environmental impacts. For more information and to watch an online demonstration click on the following link: http://www.eaglepoint.com/solutions/workflow/office/landsketch/landsketchforhighways.asp

it was right after my accident, when i lost my hand
Around middle of last month, I got fired from my job as a web applications developer at this company that does web stuff for the state — the job I moved to Des Moines for in the first place. In the midst of a long time-wasting build-up to breaking the news to me, they gave me a lot of what sounded like out-of-their-ass rationalization about their reasons, but I think it really comes down to a couple specific incidents and I'm not going to talk about them here.
It's fine though, I guess. I'm taking on some freelance stuff. It's not enough yet, I need more. I'm really strapped for money, enough that it worries me, and yet I'm happier. At the end of the day, I'm not all wiped out with that "tired from doing nothing" feeling where I can't get up the wherewithal to do anything but veg out in front of the TV. Maybe the illusion of security makes me lazy and I need to be out hustling to really feel alive. I do know that I don't like being expected to hang around an office certain hours when I don't have a whole lot to do there. I like working when I have something to do and am ready to do it. That might be a few hours in the morning and a few in the middle of the night — if that's the case, don't make me sit around an office all afternoon trying to look busy. It's a sure way to turn me into one of The Working Dead. I had assumed if I was in someone's employ, that the management above me would see to it that I was assigned as much work as they believed I should be getting done. I thought that was their job. Just because I can always come up with piddly little bugs to tinker around fixing doesn't mean I'm not bored out of my mind waiting for someone to assign me something I can sink my teeth into. I guess most programmers watch YouTube videos or something, instead of tinkering with those piddly bugs.
Whatever. I was thinking today how great it would be to make my living in music, because then I would always have time to work on music, and if I was working on music all the time, I would get really, really good at it — and being really good at music is more satisfying than being really good at programming because when you're good at music, people can tell. Even people who generally listen to Top 40 crap can tell, if you put them in a venue and let them watch a gig, the difference between the performer who has become very skilled at writing songs, or singing, or playing their instrument, versus the one that's just dicking around on the side and thinks he can get by with that. In music, quality is conspicuous.
Programming is a different deal. I realized this from a freelance maintenance project I'm involved in, where the code constitutes a "web application" in roughly the same sense that a beaver dam is a "structure." Every little task I'm assigned takes twice as long, and is twice as frustrating, as it could be, because I have to root around in the code to find the relevant bits, which never seem to be anywhere sensible. The client doesn't have the budget to pay me to put a lot of time into restructuring it, so I make do. With customers of my programming work, be they my clients, my employers, or the clients of my employers, basically if the graphic design looks pretty and the app appears outwardly to do most of what they asked for, the code underneath can be complete shit. I might take pride in the quality and maintainability of my code — and I do — but hardly anybody else can tell the difference, even if they care. People will even put up with features that don't work, and will devise workarounds, because they honestly don't seem to know they could have it better. So why have I put all this time and energy into being good at programming? We can see how it's paying off: I can't hold down a full-time job doing it.
Another consequence of my move to Des Moines has been that I ended up playing in a band that's light-years better than any I've been in before. I'm playing gigs in other towns for a change. We have an album out that's actually on CDs, not on CD-Rs I burned on my computer. And the music, the songs we're doing and the performances of them we've been pulling off, are the real deal. And people can tell. You can tell that they can tell, because they love it, and they say so. And with every bit of time we put into it, we get even better. We aren't making anything approaching a living at it, but it has the best chance by far of becoming a paying proposition of any band or music project I've been involved with. It also makes me very happy, instead of frustrated. I really ought to be taking it seriously, refusing to compromise or let anything interfere with it.
As Bob Lefsetz reminded me in yesterday's letter, "an artist creates because he has to." And that's me. I could quit just about anything else I do, other than music and my family. I could give up programming if I had to. I could give up coffee, or meat, or beer, or writing bitchy blog posts. But I don't think I could give up music. Besides, "in this economy," and perhaps in any really, it's a fallacy to treat any job as permanent.
In light of this, I now consider my primary profession to be musician. I'm done pretending that something else is the case. I sling code for money. I'll even write good code for money, because I personally find it easier and more satisfying than writing crap. But that's "satisfying" in a very relative sense. I'll write as much code as I need to, to make whatever part of a living music doesn't cover, up to and including all of it. I still love programming, and would probably love it with more conviction given the right company or project, but so far that company or project either isn't out there, or doesn't return my e-mails. But music lovers are right here in front of me.

