Thursday, October 30, 2008

Free AT&T Wifi Access for iPhone

Its great they're finally doing this but the to say "accessing AT&T Wifi hotspots is easy" is a joke:

Activate Wi-Fi from the settings icon on your iPhone.
Select "attwifi" from the list of available networks.
Enter your 10-digit mobile number and check the box to agree to the Acceptable Use Policy. Tap "continue."
You will receive a text message from AT&T with a secure link to the AT&T Wi-Fi hotspot. You will not be charged for the text message.
Open the text message and tap on the link for 24-hour access to the AT&T Wi-Fi hotspot.

They have to come up with an easier way for me to roam around AT&T Wifi spots or its just not worth the bother. Same goes for Panera, its too much work, i'll just use Edge/3G before I go through all the click throughs etc. Those may be fine on a laptop but on a phone its a real pain.

Monday, October 27, 2008

Labels

For those faithful 5 followers of my blog out there, i've labelled my
previous entries to make finding things easier. Blogger really should
show an index of the labels so you can jump to them quickly.

Saturday, October 18, 2008

1Password & Syncing

I've mentioned before that I love 1Password for password management on my Macs and iPhone. Until they added iPhone support I had a reliable password manager that kept all my macs up to date and my passwords were everywhere. When they added iPhone support they ran into a nasty bug with permissions which caused a lot of pain. Their solution was to move away from Apples sync services and keychain approach to their own file format. In the process they lost the real ability to do synchronization of passwords between machines. Their recommended solution is to move your new 1Password keychain to a network drive shared between the machines, either a real network drive (same network) or a virtual one like iDiskDropBox, etc. This "solution" leaves a lot to be desired. The shared storage approach either requires money (iDisk) (plus its notoriously crappy) or is a freebie with caveats that it could disappear at any moment (DropBox). While nobody really has sync working well, Apples sync services are generally workable. 

So the solution for me? There are a few options:

1) Give up on iPhone sync - no passwords on the road and I cant remember generated stuff, not an option
2) Give up on multiple computer sync - I have a computer I use for work and one for home, not an option
3) Use one of their sync methods - iDisk stinks. Dropbox could work but it can come and go, its another application, I dont need to store my stuff online, the space is limited etc.
4) Sync some other way.

So, i've mentioned before that I use rsync/ssh to keep things up to date on the files side and now that apps like 1Password are recommending a similar approach, off we go again, here's whats working for me with no new apps:

in my crontab file (crontab -e) I have (among other things :p):

#
# 1Password Sync
#
30      12      *       *       1,2,3,4,5       export SSH_AUTH_SOCK=`echo /tmp/launch*/Listen*`;rsync -avS -e "ssh -p <a port> -i /Users/Rob/.ssh/ssh_key " /Users/Rob/Library/Application\ Support/1Password/1Password.agilekeychain/ Rob@example.com:"/Users/Rob/Library/Application Support/1Password/1Password.agilekeychain/" 2>&1 | mail -s "Backup: Sync 1Password from MacBookAir to Home Desktop" rob+cron@example.com
40      12      *       *       1,2,3,4,5       export SSH_AUTH_SOCK=`echo /tmp/launch*/Listen*`;rsync -avS -e "ssh -p <a port> -i /Users/Rob/.ssh/ssh_key Rob@example.com:"/Users/Rob/Library/Application\ Support/1Password/1Password.agilekeychain/" /Users/Rob/Library/Application\ Support/1Password/1Password.agilekeychain/ 2>&1 | mail -s "Backup: Sync 1Password from Home Desktop to MacBookAir" rob+cron@example.com

This syncs first from my mobile machine, then back from my desktop. 

A few comments:

1) I dont use --delete which may be an issue if I ever want to delete Passwords but thats not something I do often in this case. The shared drive approach solves this problem but has the other issues mentioned above.
2) The whole export/SOCK thing is so it can use my saved ssh password for "/Users/Rob/.ssh/ssh_key" from my OSX keychain when it ssh's into the remote machine as a cron job. As mentioned before I use a not-well-known ssh port, and then no username/password just a ssh key.