May 2007


from MacApper

So there you are in your cubicle at work utilizing your employer’s expensive internet connection for everything except something that can actually justify your pay check. This is a good enough time to do some power ebaying, youtubing, or hell even some chatty chat with that sexy new bit on the side. It doesn’t get any better than this right? To actually get paid to surf the internet whilst firing off a reply to the occasional email, to keep up the guise of you actually being alert and attentive to the various happenings at work. Imagine if your poor sap of a boss actually knew what you were up to!

Guess what, chances are he does. Or is about to.

There’s always some little weasel of a sys-admin just waiting to inform “the man” of just how much time you, his star employee, is actually NOT spending justifying that paycheck. Just imagine when the schmuck presents ream after ream of printed logs of your questionable online antics. IRC, MSN Messenger, AOL Messenger, YouTube, pr0n, and the list goes on. You get the picture. Now before you fire up Monster.com on your soon to be former employer’s dime, there is thankfully an answer.

SSH Tunneling
The concept is simple. All your activities are sent through an encrypted SSH tunnel to some remote server which in turn does all the dirty work (so to speak). The beauty of course is that all that nuisance of a sys admin can ever see is a bunch of encrypted traffic.

Now here’s what you need:

* openSSH client. (thankfully OS X has this built in!)
* access to an openSSH server

from Lifehacker

I love Flickr, but I’m terrible at uploading pics to my Flickr account. It’s not that there aren’t already a lot of great tools for getting photos into Flickr (there are); but I need a way to monitor my pictures folder to upload everything I dump in there. Call me lazy, but I just don’t want to take the extra steps if I don’t have to.

Luckily a cross-platform script called uploadr.py can watch a folder of your choice for new pictures, then automatically upload them to your Flickr account. Here’s how to set up uploadr.py.

from Xbox-Scene News:

Here are some details about the Xbox360 LIVE bans I got directly and indirectly from GaryOPA, Commodore4eva (C4E), Iriez and others. Of course don’t take any of this info as 100% confirmed, noone knows exactly based on what data MS is banning … it’s just an analysis of what they think is happening and what MS might/can be checking.

C4E thinks MS is probably detecting and banning consoles from LIVE by tracking usage of backups via timing of the challenge response (c/r) on the drive over the last few weeks or months. A modified FW will reply much faster to the the Challenges requests (stored in a table) than an original firmware (seek on drive). They probably do this test more than once and can ban you if you’re above a certain average.
FuzzyLogic also found that microsoft is sometimes doing additional checks on discs: PFI/DMI (so images without these sectors (or if using an old FWs without support for PFI/DMI) can probably be detected easily), drive inquiry (reads ascii string from drive), and capacity (reports capacity of disc) are requested. Strange thing here is MS requests 0×8000 bytes for PFI and DMI, while it should normally be 0×0800 bytes. TheSpecialist pointed out that the remaining 0×7800 bytes contains the relocated SS and PFI on burned discs … which would make it very easy to detect backups for MS. C4E however told us this would not work on TS drives as its cut off to 0800 even if more data is asked, it’s unconfirmed how modified HLG FWs drives respond to this atm.
The “read capacity check” will also work as detection on HLG because, unlike the newest TS FWs, it doesn’t have true ’stealth media’ yet, these drives are reporting back the burned disc based size of PFI instead of the correct PFI.
Apparently there’s also an issue with SS (Security Sector) extracted from Hitachi-LG, some necessary data is screwed … which means that probably only the Toshiba-Samsung / kreon setup has been extracting correct SS.

Another thing they are probably detecting (but probably not using yet to decide to ban or not) and log/flag is if you ever booted your Xbox360 with DVD SATA cable not connected to your Xbox360 (E64). Many people did this to power their drive when they wanted to flash it (power connected to 360, SATA to PC). So it’s highly suggested to use an external power to flash next time.
It’s also possible MS also bans based on stuff like bad credit card info for your country, running a NTSC machine with euro-address/credit card (or inverse), having out-of-region (arcade) games and demos on your HDD, unofficial 360 HDD, internet downloaded gamesaves etc. There’s no clear view on all this yet.
For now, C4E believes Microsoft is not detecting modified FWs or detecting FW changes/updates. Using a special FW they did not detect any debug commands sent to the drive by MS (they went through the dash/kernel updates with the special FW as well and did not detect any debug commands there either). So they think either:
A/ MS is not doing any FW detection right now, and only previously (maybe on request of MS servers while playing on LIVE?), or
B/ MS is banning based only on the timings of the drive, ss/pfi/dmi checks, capacity, drive inquiry and c/r verification.

We also got information C4E is working on an “iXtreme Online” FW for Toshiba-Samsung drives, a Hitachi-LG version and maybe even BenQ version might follow later.
The new FW will have less features than the current Xtreme FWs: no single-layer (DVD5) support, no ripping of games (0800 mode), but more features to safely play from burned discs (emulate the exact speed and timings of the original games) and prevent booting from un-safe discs (without PFI and DMI or bad SS - so discs not passing the ‘Stealth Check’ (using Xbox Backup Creator(info)(info) for example) are not going to boot on the new firmware), or images that aren’t exact dumps of the original.
There’s no official ETA (maybe this weekend though for TS drives), and of course no guarantee MS will never ban you based on new checks (that’s the risk it takes if you want to be part of the modding community ;)) The HLG FW will take a bit longer as it’ll require true ‘Stealth media’ etc added.

This new FW will of course be made mostly for new consoles being modded, because even if you’re not banned from LIVE yet there’s no way to know if MS already has info/logs on your console ID regarding timings or other stuff so even changing to this new firmware in the near future may not stop that console ID from being banned in the next wave of MS bans.
If your console is not banned yet, it’s highly suggested you don’t boot any burned discs, originals should be ok, even when offline (MS might be storing results of some checks in flash), until the release of the new FW.
If your console is already banned this will of course not help you … just enjoy the offline playing on that console for now (with some games you could try using 3rd party networks like XLink Kai(info)) and maybe some day a new exploit will allow you to do more with that console.



$10 Police Flashlight Hack! - video powered by Metacafe

from Xbox-Scene News:

With the amount of posts we see on our forums … it’s clear, Microsoft decided to start banning Xbox360 with modified firmwares today (both Hitachi-LG and Toshiba-Samsung drives).
While it’s the same release date as Halo3 beta, it seems that people who didn’t download Halo3 also get banned. They probably detect backup discs (and not the modified firmware) when you play ‘em online (not confirmed yet).
Even people using the new firmwares with disc-jitter added get banned, so it looks like Microsoft found another way to detect it.
Just like on Xbox1 it looks like Microsoft bans the console unique ID (serial), not the LIVE user. Microsoft will not allow anyone to login on LIVE on a banned console.
Many people on the official xbox.com forums also claim they got banned but didn’t have a flashed firmware … we’ll have to see how that story develops in the coming hours and days.

Eric D. Schabell » Linux courses
The following Linux courses have been created by me, released under the GFDL . They can be viewed in slide format online, but for a more complete introduction to the material I am available for teaching contact information is listed at the bottom of this page. I have taught these courses commercially…

from Simplehelp

This tutorial will take you each and every step of the way through installing Linux programs in OS X - using Fink and FinkCommander.

Something I should mention up front - during this process you’ll be asked to enter your password about a half-million times. I left those ’steps’ out to keep this shorter.

1. Installing Fink and Fink Commander
2. Configuring Fink
3. Installing Linux applications
4. Launching Linux applications with Quicksilver