For the iPhone, Apple chose a business model of selecting carriers to associate with, and sell the iPhone as a whole experience instead of merely a device, including data plans and their special visual voice mail. Only with carriers that accepted their conditions, from subsidization of the equipments to profit sharing contracts. Not all carriers accepted this and some of us only had the choice of either not having an iPhone or changing carriers.

This happened until Apple, by the laws of some countries, became legally bound to supply operator-free versions of the iPhone. They complied with the laws, and the iPhone is sold unlocked in several countries, including Italy, from where my own iPhone was imported from.

Everything worked great, including the tethering option (connecting your computer to the internet using the iPhone) since the upgrade to iPhone OS 3.0, to the point that I decided to cancel my separate data-only contract that I used with a 3G USB modem to connect my laptop to the internet, and asked my carrier to upgrade the data plan on my voice card from 1GB to 3GB a month. It was a win-win situation for me, as I would pay less, and carry only the iPhone for everything.

Well, it worked well until last week, when the iPhone OS 3.1 upgrade showed up. As a legal user of the iPhone, and never having it jailbroken, I never really bothered to check if such upgrades would break something. My belief was that Apple would only add new features and make things work better, as they have been doing since I bought my iPhone almost one year ago. With the 3.1 upgrade, tethering stopped working. It just disappeared from the options.

After looking around for the reason, I found this page. Apple changed the way the iPhone accepts the tethering configuration, and now requires the APN in the carrier bundles to be signed, meaning that tethering will only work with the Apple associated carriers who allow tethering explicitly.

I have nothing against certain carriers forbidding tethering, it’s their own policy. But this change by Apple has meant that I have a legal operator-free iPhone (for which I paid much more than a subsidized and contract-locked iPhone) with a voice+data contract with my own carrier that allows tethering, and yet, I can’t.

I decided to wait, and seek clarification on Apple’s own support forums, on this thread. What pushed me over the edge to write this post was that they deleted my last message, citing that

“Your post was removed from Apple Discussions as it contained feedback or feature requests. These areas are intended to address technical issues about Apple products. Although your feedback is appreciated, unfortunately these forums are not designed for it and your thoughts/concerns will not get the attention they deserve.“

which is laughable, considering what is already posted there and the message that was deleted:

In the end, the real reason Apple sold operator-free iPhones is because they were made to by the legislation of certain countries. And because the AT&T data network is bursting at the seams (and they still want to push the marketing mantra of “unlimited” data plans), they forced Apple’s hand into cutting the problem by the source – just kill tethering in general. Apple’s solution, to allow tethering at all with their partner carriers who allow it, was to cryptographically sign the APN strings in the carrier bundles. Which left everyone with legally unlocked phones out in the rain if they don’t work with partner carriers (like myself).
I can understand why they did it. It just means they’re not worried about losing the fringe share of unlocked customers, who represent a tiny percentage of their sales.
If Apple doesn’t solve this (and I repeat, I think the percentage of users affected is not enough to force them to re-think their strategy), our only recourse is legal. They advertised an important feature, it worked perfectly with unlocked phones for a while, and then they removed it.

I think this whole incident is just bad marketing, and bad PR. Bad marketing, because they’re pushing an important feature such as tethering to sell the iPhone (saying “check your carrier for availability” – mine supports it), and then removing it, even if it only affects a certain part of their customers; and it’s bad PR because instead of saying to the owners of legal operator-free iPhones “please wait for a solution, it is coming”, they’re just passing out the message that they just don’t care. I know they didn’t want to have the obligation to sell unlocked iPhones (as it goes against their business strategy), but it’s not nice to be on the receiving end of this treatment.

And no, I’m not going to boycott Apple’s products, I’d be the one to lose, and neither am I going to seek legal recourse. If the situation is not solved soon, I’ll just revert to my previous solution of having a separate data plan. This is more of a warning to prospective buyers – you either buy the iPhone from a supported carrier or you might face surprises such as this one in the future, even if you do everything “by the book” and buy a legal operator-free iPhone.

I’ll be talking about the host Mac (the one where the original filesystem resides) as host, and the moving Mac as the client, where the remote volumes will be read/written from.

Requirements:

1. Make sure you have admin privileges on both the host and client computers (although running your main account with admin privileges is not advised);
2. Make sure that on the host machine that you’re either connected directly to the internet and have TCP port 22 not firewalled or you have privileges to reconfigure your internet router to re-route port 22 requests from the internet to the host computer;
3. Make sure that you can access the host computer from the internet, either by having a fixed IP address (not normal on domestic aDSL or Cable connections), or by using a free service such as DynDns.org (this explanation goes beyond the scope of this howto – search for the solution for your own router or Mac on the internet);

Procedures on the host machine:

1. On System Preferences, under “Internet and Network” you’ll find the “Sharing” icon, click it;
2. Under “Services”, turn “Remote Login” on – authenticate yourself as necessary beforehand if needed;
3. Open a terminal window on the same machine, and type ssh yourusername@127.0.0.1 to test if in fact the SSH service has become activated – follow the instructions;
4. If the computer is connected directly to the internet, also under “Sharing”, you’ll find the firewall tab, click on the allow column for “Remote Login – SSH”;
5. Or if you’re connected to the internet through a router, you’ll have to look for port mappings or something equivalent on the router, to relay all internet requests for port 22 from the internet to the host computer (this explanation goes beyond the scope of this howto – search for the solution for your own router on the internet).

Procedures on the client machine:

You will need three pieces of software:

• MacFUSE – obtainable here;
• sshfs – also obtainable here;
• MacFusion – a wrapper to make everything more user friendly, obtainable here, make sure the version you’re downloading is compatible with the core version of MacFUSE you obtained (as I’m writing this, everything is a bit under development, so there are incompatible beta versions floating around)

1. Install MacFUSE and reboot, followed by installing sshfs and MacFusion (which in theory don’t need a system restart to work);
2. On a terminal window on the client, outside from the host’s LAN (i.e., connected through the internet) test first if you can SSH to the host machine, by typing ssh username@completedomain.com
3. If you can login into your account, the next step is to fire up MacFusion (which should be located in your Applications folder of your client machine
4. MacFusion is really simple – preferences are resumed to setting MacFusion to startup itself at boot, to check for updates to itself on Startup, and what to do when the client Mac goes to sleep and resumes.
5. The only thing missing now is to add, if you wish, the host computer to MacFusion’s favorites list – you’ll have to supply the name (whatever you wish), the server (without any “http” or similar prefixes), the Port can be left at 22, you can change the Server Path to / if you want for instance to access the “Volumes” directory to access any external disks that specific user has access to, and the most likely authentication method you’ll be using is “Password”.
6. The first time you try to mount (connect to) to the host’s filesystem from the client machine, MacFusion will even be nice enough to give you the option to store the password in the Keychain – this is up to you, if you trust you computing space enough to store passwords or not.

This is it! If everything worked, you’ll have a brand new volume on your desktop, that works exactly like a local LAN drive, with the permissions of the user you logged yourself as. Now you can do backups remotely through the internet, do anything you could do with a local LAN drive, but through a fully encrypted tunnel, and just limited by both the upstream and downstream speeds of both the host’s and client’s machine internet connections.

If you assume a 7% sales tax when buying in the US, vs. 21% VAT in Portugal, the difference is of € 521.66 in the US vs. € 833.69 over here – € 312.03 more, or almost 60% more expensive. For the same binary, probably downloadable from the same server. Sometimes I hate living in Europe.

Imagine that you use the online banking service of bank xyz on www.xyz.com – with this exploit, when your browser requests the IP address of www.xyz.com, instead of the real IP address, it will receive the address of either a server that looks exactly like your bank’s website, or you connections will be routed through a proxy server that will act like an invisible go-in-between, relaying the content both ways, but storing everything.

This is just one more reason why the default passwords of everything should be changed.

The primary display is the MacBook’s LCD (1440×900) and the secondary display is an external LCD (1680×1050).  I’ve resized them to the same size for clarity.

The main display is the normal desktop, with Firefox, iCal, Adium, a terminal window, etc.  Things get a bit more layered on the second display.  On the foreground you can see a Windows install running on VMWare Fusion locally, running Mapsource.  Behind that on the left, it’s a Remote Desktop connection to my home Windows server, with another Windows install running on it (it’s the WAMP where matsu is served from).  And finally, behind all windows, on the right, is a Citrix connection to a Reuters hosted platform.  It’s amazing what I’ve seen in the evolution of computing since 1983, from my first computer until today…

1. On the location (address) box, type about:config (this will bring up a list of all configurable settings)
2. On the filter box, type click_hold – this will single out the ui.click_hold_context_menus setting, which has false under the value column
3. Double click the ui.click_hold_context_menus line to turn false into true
4. Close and restart Firefox, click holding will now bring up context menus

1. Go to www.vmware.com
2. Download the beta VMWare converter
3. Install it in the machine you want to virtualize
4. Run it – it’s really easy, if you have any doubts about the process, google it
5. Choose the destination folder on a networked or external storage drive
6. After the process, move the created VM folder to the machine where you’re going to run the image
7. Again, at www.vmware.com, download the VMWare player to install on the new machine
8. Run your older computer inside your newer computer!! You can configure the virtual machine with it’s own separate IP address, so you don’t need to re-configure your router’s port forwarding settings and such.

It works – if you’re reading this, this is being run in a WAMP installation (Windows XP, Apache, MySQL, PHP) inside another computer running Windows XP. I’m planning, when I’m not feeling so lazy, to do a very light LAMP (same thing but with Linux) image to run matsu in, that is portable to any machine running Windows or Linux (and hopefully Mac OS some day). As a bonus, it’s running much faster virtualized like this than it was on it’s own (albeit slower) dedicated machine.

1. Plug your iPod on another computer (so it doesn’t sync automatically with the bogus version of your Address book);
2. Don’t pair the iPod with that computer/iTunes;
3. Enable the iPod as a drive if not already;
4. On the iPod partition, there will be an iSync.vcf file inside a folder named “contacts” – copy it from that computer to your computer;
5. On the Address book, from the File menu, choose Import, and vCards (or command-O), and choose the iSync.vcf file you copied;
6. You should now have back all the contacts you had before the crash, from the last time you connected your iPod to your computer.

Hope this was useful to you!

Not bad, not bad at all! I used the computer normally, reading and replying to e-mail, IM’ing, and browsing the web.