I was kind of messing around with my (ghetto) home(made) desktop/server for a couple of days on our home network, and I thought it would be sweet listen to and control the music coming through my stereo, without having to constantly go over to the desktop when I wanted to change a song, change volume, etc. Also, partially because I couldn't get any sound from my laptop speakers (I've tried almost EVERYTHING). So, being the (?)creative(?) person I am, I set out to make my server sing - all through SSH-ing to it from my laptop, on the local network. This would be the best way for me to still control and listen to music with my mute laptop, and give my allegedly 1337* terminal skills a run for their money. * - sorry. I just had to get that out of my system... :) Here's How you can too... I just thought I would post this, partially as a lame excuse for a blog post, and mainly because I think others dealing with sensitive files in linux will find this useful. As you all know (or should, anyway) when you just delete files, on just about every operating system, the files are not actually gone. For some saving of confusion, I'll briefly cover why. When you send something to the Trash Bin, or "Recycle Bin", as known in windows, the file gets sent to a temporary holding folder, where it stays, until either you decide you didn't really want to delete the file, and resurrect it, or until you empty the trash bin. The problem is this. Let's say you have a file, "IMPORTANT.doc", and you sent it to the trash bin a week ago. Now it's time to clean the computer, so you open your trash bin, and empty the recycle bin. When you do this, it warns you that the files is going to be remove permanently, blah blah blah. So you hit yes and your file is gone. This is not totally true. What happened was that, when you emptied the recycle bin, the operating system wrote to your hard drive on a part of the file, known as the pointer. This pointer used to say: "This file is located here, and the data should not be messed with!". When you deleted the file, it wrote over that pointer, and changed it to say: "This file is no longer important. If you need to put another file on the hard drive, feel free to write over me." Or however the depressing story goes. So, as you see, the data is never really deleted, it's just marked as unimportant, like the back of used scrap paper ( You know, that lame half messed up printed on paper your mom gave you to color on when you were a kid... ). So, theoretically, the file can still be recovered with special software and, in more high profile cases, with an electron microscope. "Well..." you're saying, "how DO I delete my files, then?". Long story short, in all scientific reasoning, theoretically, there is no way to completely be sure your data is securely removed, beyond recovery- excluding the physical destruction of your hard drive (for just one file? Psh. Come on...). But there is a way to come close of this. The best way is to use a technique that recursively writes over the file data, multiple times, before removing the pointer. It's kind of like scribbling over a secret message with ink. Permanent ink. The more passes, the better the chances of the file being unrecoverable. The DoD has it. So why shouldn't you? To begin with, under windows you will usually need a third party application, such as Eraser. Under linux, the command is already there, you just need to know it! I have made a simple one-line script tested on ubuntu, so that all you have to do is open a terminal, right-click-and-paste, and then re-open the terminal. Here are the steps, to a more secure linux deletion method: 1. Open your terminal (located in "Applications > Accessories > Terminal".) 2. With terminal open, right click in the window and paste this code: echo 'alias sdel="shred -f -n 50 -v -z"' >> $HOME/.bashrc & exit 3. The terminal will close, usually almost instantly. This is supposed to happen. Open up the terminal again. Now you have a command called "sdel". Use this command on any file you would like to securely delete. For example: sdel IMPORTANT.doc This will go over the file 50 times with random and repeated data, then fill it with zeros, and THEN, remove the pointer. You have a file that is very likely 99% unrecoverable. Now we can all sleep at night. Anyway, this isn't too much in terms of a hack, but I just thought I'd throw it out there for people wanting to know if their files are really, truly being removed from their linux computers. Ciao! EDIT: I have come to find out that this trick may not completly apply on newer journaled file systems, such as ext3. This has yet to be confirmed (I'm no expert on FS's), but it is still worth using for that extra assurance. Lubuntu 9.10 Test ISO 09/02/2009
Hey, just posting this in the meantime, until the next project... I was looking over hackaday, and I saw that Lubuntu - a distribution variant of Ubuntu, utilizing the lightweight X11 Desktop Environment, or LXDE - has been released for testing. This is a little late notice, but if you didn't know, now you do. Beta testing is very fun if you're into it- and if you're not, you should start! You may like this distro anyway, because it's very easy on lower-end hardware, and so will work better on older computers (and nicer on new ones ;) ), possibly repurposing old PC's into- whatever you can make linux do... You can check out the blog page here, as they post the most recent download information. Belkin FAILs Big Time... 08/14/2009
Hey everybody, sorry it's been like a month since my last post, which is way too long, but don't give up hope; I will always be here to hack away, and will never just quit posting (unless in a sad event I am killed and thus can no longer post, but you already knew that :/ ). In the meantime, I've been just busy enjoying the summer, and reading LOTS of manuals, and books, from everything JavaScript to using the Processing language to interface with virtual COM port data. Also, a little bit of driving around town has led me to a (hardly) epic discovery. It's about the belkin router crashing exploit that I told you guys about a while ago, where, when you had access to an unsecured belkin router, you just enter a formatted URL that crashes the login program, and ultimately the entire router. Bye-bye internet. What I didn't know is that this exploit pretty much works on any belkin router, because the problem is that they use the same web interface on nearly all their routers, including the basic programs that come with it. A flaw in proprietary coding. So, to a certain extent, this is a pretty big thing, because people could just go wardriving around, crashing any unsecure, or poorly secured (Who uses WEP anymore???) Belkin routers ( For goodness sake, don't use the default router name!). Hello There... 07/08/2009
Hi guys I'm back; sorry for the long wait, as I have been pretty busy for the last couple weeks. Windows Password Resetter 1.0 06/22/2009
Today I finished writing a program I started last night, that works on Windows Vista, and should work on windows XP. Website changed... 06/13/2009
As you may have noticed, I have change the website so that the home page is now the "Hacks" tab. This way when you visit the site you can go straight to the hacks, instead of having to click through or wait five seconds every time you visit. The information that was presented on the "Home" tab is now in the new, "About" tab, along with the (non) liability notice. Belkin Crasher Update... 06/12/2009
Here is a screen recording of it in action, on Windows Vista. Just because the program doesn't work on Windows, I didn't say you couldn't crash it by hand. Really, you could do this with anything that has a web browser and WiFi 802.11/g support. Upcoming is a picture of the type of wireless router I am talking about, but first, I have to say a few things. If you have this router, It is vulnerable, but only if someone has or gains access to it. To prevent that from happening, put a password on it (preferably WPA2 encryption) so that only people you allow on can use it. If someone does happen to crash it (or you do :] ) just unplug it from the power source to force a reboot, and it should run like normal. That is, 99.99999999% of the time. If you happen to be the 0.00000001% that break their router by doing this, I am NOT to be held liable. You had you warning. Here's the photo: Belkin Crasher 1.0 Released 06/10/2009
I have - because of want to keep up my programming skills this summer, and plain boredom ;) - written a sockets command line application in C that exploits the hack that I discovered a little bit ago, that crashes Belkin routers. I have it on my downloads page. I did NOT write this program to be evil! I did this to help expand my experience and skill at hopefully someday becoming a CEH (or at leased some pen-tester dude, lol), but I'm not perfect at sockets programming (let alone in C, I prefer C++), so don't whine! Just use it wisely! Usually, I post about hacks or techie-like things on here, but today, I HAVE to post about something amazing that happened to me today. AMAZING. First of all, I would like to thank everyone at Hennessy Music, a local music store where I live, and more specifically Mr. Hennessy and staff for doing this for me. |


RSS Feed