punkwalrus (punkwalrus) wrote,

Master of his Yard - plus Wireless hacks, Cody Banks, and KDE success

I got to really look at the back yard for the first time in ... months. Since late November, I have either been houseridden, working too hard at work, sick, or the back yard was a pile of snow. I got to actually do some yard work on this nice day. Most of my yard work consists of this pattern: work, rest, survey, repeat. I feel a bit foolish during the "survey" part, because I feel like some sort of Daniel Boone. But I am not looking for "them rebbits, 'coons, injuns, an' bars," but for signs the house is about fall apart somewhere. My house has been good so far, but this time, I noticed some dry rot around the trim of two doors. I also found the source of the leak into my rec room. The winter's ice had forced the crack open wide enough to be noticeable. I hope I can fix most of this.

Sometimes, Christine and I go out to Starbucks together. Today was so nice, we decided to do this. We sat in there, talked about some things, and then watched people.

Later, we went to take CR to a movie, and we saw "Agent Cody Banks," a film with Frankie Muniz (from the show "Malcolm in the Middle") and Hillary Duff (from the show, "Lizzy McGuire"), two teen heartthrobs currently. CR wanted to see it. It was... okay. It was very typical of any kid's movie. It had bad, stereotyped acting. The bad guys were all scarred, angry, mean, and had an evil mountain base with a female voice computer counting down stuff. The CIA was some sort of sleek-black place with the latest in technology, and agents worked in almost minimalistic cartoonish settings as interesting as the inside of a locker. Lots of Segway scooters, I guess as part of their product placement. It was interesting to see this film from the CIA I knew to what the public things the CIA or FBI is. I mean, the most important meetings are probably held in old, boring rooms at a big laminated meeting table with coffee stains, torn up chairs held together with duct tape, and drywall that hasn't been washed since 1977. Not sleek black rooms with holographic displays. The movie wasn't *terrible*, but it's nothing to write home about, either. I also decided Segways were pointless. The move about as fast as people walk, they take up more space in hallways, and seems like an expensive solution to a problem I am not sure was worth noting, anyway. They just seem like an invitation to more accidents with pedestrian's ankles.

We also went to our friend Roberta's house last night. She had been inviting us over forever, and we kept not being able to go because our life was in chaos. She has a nice house, and has done a lot of her own work on it. Sean and Lou-ann were there as well, and we all talked for six hours about the war, relationships, and the stuff my friends and I usually talk about. It was a good time, and I was glad to see Roberta's house finally, even if I did have another migraine wave.

Non-geeks may skip the rest of this entry, although the bit about wireless should serve as a red flag to those of you contemplating stuff.

I noticed that our Starbucks now finally has 802.11b available. I contemplated how easy it would be to hack, based on study I did for work, plus stuff about networking I already knew (thanks, Cisco!). To hack a wireless LAN, you have to get pass three things (assuming they have the brains to actually set up security blocks, you never know with retail):

1. Break the 128 bit encryption
2. Hack a username and password
3. Spoof MAC address

See, as I have read online, #1 just tales time, unless you get #2 first via social engineering or something (some people are so stupid when it comes to protecting their info, I read on one site where someone just looked over another's shoulder). But I also saw one site that claimed they did broke 128 encryption to a cafe in 5 minutes, so you could be parked in a car near the Starbucks. Then you set up a packet sniffer and get a login and password for #2. You should also be able to get #3 the same way. Chances are that Starbucks doesn't even check for #3 because what if a customer brings in a different laptop? But it would be good to spoof this anyway to confuse a back trace. Wireless is so easy to hack, I'll probably never use it in my house except to have it on only when I need to use the laptop elsewhere or for friends at a party.

I am real proud I got KDE to work on my home OpenBSD system. Here's what I did, in rough order:

1. Installed OpenBSD 3.2 from FTP
2. Installed ports from "/pub/OpenBSD/snapsnot/ports.tar.gz" (this is where my audience gasps, I know)
3. Installed bash and samba
4. Tried to install KDE. Got "C compiler cannot create executables." WTF?
5. Realized that I installed "snapshot" instead of "current"
6. Deleted /usr/ports
7. Downloaded "/pub/OpenBSD/3.2/ports.tar.gz"
8. Tried compiling KDE. Got some package error with "arts3"
9. Did a delete_pkg on "arts3." Reinstalled.
10. Got compile error. Would not let me compile.
11. Deleted /usr/ports/arts3. Tried to add_pkg.
12. Got a "cannot find Makefile."
13. Now also, several shell commands stopped working. The "ps" (print jobs) command was one of them.
14. Got mad, realized I probably hosed my system. Flat reformatted and reinstalled OpenBSD 3.2 because I am too lazy to figure this out.
15. At work, I was installing KDE on another system, but after 5 hours, got a "postgresql" error. Doing "/usr/ports/databases/postgresql/make all" and then "make install" fixed this.
16. When I got home, I made sure I went to "/pub/OpenBSD/3.2/ports.tar.gz"
17. Made bash and samba again. Then made postgresql and then KDE.
18. At home, KDE "make" took *14* hours to compile on a P2/450 mhz system. Only maybe 10 minutes of that was actual downloading stuff (I was on cable at home). At work, on a P3/600 mhz system, it took about the same amount of time (I was on a LAN with a fat T1 pipe). Jesus Jumping Frog! What a commitment.
19. Tried to start KDE with "startkde." Got X authentication errors.
20. Did xf86config to made an X86config file. startkde = X authentication errors.
21. Made a ".xinitrc" file in my root directory with only one line: "startkde"
22. KDE starts! Yay! Then in 640 x 480, which is WAY too small. Luckily, I remembered I could increase the resolution with "control alt (number keypad) plus" to cycle through resolutions. Did setup.
23. KDE not only works, but it set up my sound card! I NFS-mounted my Linux shares, and played mp3s and mpeg movies.
24. Tried to "make all" for Mozilla. Got an error that "mozilla-0.9.3 is marked as broken: core dumps in dynamic library constructor." The Mozilla web page had no help. That's okay, KDE's Nautilus was a pretty good replacement.
25. I installed Seti@Home. Because if the machine is on, and I'm paying for it's electricity, it's gonna WORK for it, man!

So that's what I did, in rough order. I showed you my mistakes so when you get the same thing, you'll know how to fix them. Again, don't e-mail me for support. I am just doing this as a "gee whiz" hobby plus to get some secure servers at work. To do:

- Get user account on my system to be able to run KDE. Right now I'm getting authentication errors and "KDE cannot find the necessary files" errors from the user account. I think if I change my user to the "wheel" group, this will fix it.
- Find a place for this box. My den is too hot with only 3 systems running, and it's cold outside. In the summer, this could be unbearable.

This entry was originally posted at http://www.punkwalrus.com/blog/archives/00000078.html
  • Post a new comment


    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened

    Your IP address will be recorded