Wednesday, August 10, 2011

Strangest sync error ever - Google Calendar

This is very strange.

I use Google Calendar Sync to sync an Outlook/Exchange calendar to Google Calendar.

On that machine I authenticate with two Google accounts, one has two factor authentication.

It looks like Google Calendar Sync is posting transactions to both accounts even though it has only one account's password.

At least, that's the best explanation I have so far.

Again - one of the weirdest things I've seen in a while, even allowing that sync is fraught with weird errors.

Tuesday, August 09, 2011

Steve Jobs hates me: Viewing Mac OS X Lion Parental Control logs

OS X Lion is not all bad. [1]

Yes, it's a memory hog (64 bit hurts). Yes iCal and Address Book drive strong geeks to drink. Yes, it's insane that it can auto-quit background apps (really, that's nuts).

On the other hand, 10.7.0 is less buggy than 10.6.0 or 10.5.0. That's progress. I might even upgrade my main machine after version 10.7.3 instead of waiting for 10.7.4.

Better yet, Mission Control and Full Screen are very nice on an 11" MacBook. Well done Apple.

Indeed, Mission Control is so good I dared to hope that Apple had fixed one of the most ridiculous bits of OS X -- the non-resizeable Parental Control log file window (See: Viewing Mac OS X Parental Control logs).

In 10.5 and 10.6 this screen has a control for a resizeable window, but it would only extend vertically. Most of the logged URLs were unreadable.

So what happened in 10.7?

You are guessing nothing. You would be wrong. The resize control was fixed. It now correctly indicates that the window can only be sized vertically.

Think about that.

Apple recognized there was a bug. They put some (small) amount of resources into fixing the bug. Instead of making the window resizeable however, the engineer fixed the control.

That can't be incompetence. That has to be malice.

There's only one possible explanation.

It's personal.

Steve Jobs hates me.

[1] The best review isn't the celebrated, and quite good, Ars Technical Review. It's Robert Mohn's Macintouch review. If you are only going to read one, read that one.

Sunday, August 07, 2011

Blogger search: no longer complete

For years Blogger's search of past posts worked well. Lately I've found it misses strings in some older posts, even strings that appear in post titles. So there's some unannounced limit been placed on search, possibly for performance reasons.

I hope Google will fix this, though it's a bad sign that they didn't bother to announce it. In the meantime I'm looking into what I can do with Blogger's export to "Atom Export Format". On first pass, it's not too promising. Gordon's Tech produced a 14MB XML file, including comments but excluding images (Text Wrangler opened it without blinking).

What I want is an HTML archive I can view locally and let Spotlight index. The sort of repository I used to create by running a robot against blogger.com. Maybe I need to try that again.

 

 

Saturday, August 06, 2011

What do do with an old iMac that shuts down unexpectedly?

Our 6yo G5 rev B iMac is shutting down unexpectedly. It's mostly likely the power supply, which is sold for about $150 with shipping. (This was an exotic Apple model -- it was designed for easy repair.)

It's an old machine with a partially delaminating monitor. So it probably only has a couple of years left in it anyway. That argues for replacing it with a mini and a monitor for about $800.

On the other hand, the kids use it when their MacBook is busy and it doubles as a movie theater and media server. It can run Classic, so it's valuable to people and businesses running legacy software; it still has a resale value of about $450. Throwing it out will cost money, plus that kind of waste hurts my soul.

Yet again, do I know the sudden shutdowns are a PSU? Could be something else. The costs of investigation are high ... but not as high as the pain of buying and configuring a new machine.

Decisions ...

I'm probably going to do a hardware test (if it will run long enough), reset the SMC/PMU and physically inspect the capacitors and mb. If it does well there I'll order the PSU.

Update: Capacitors look good, but it shutdown during the hardware test. I'm 90% sure it's the power supply, there was a brief recall five years ago but it was fine then. It's long past the time even a generous vendor would replace a PSU, so I ordered a "new" one from iFixit. The quotes because "new" in this context means Apple sourced -- I very much doubt anyone is making truly new G5 iMac PSUs. iFixit was $15 more than the lowest price, but they have by far the best reputation of the vendors I found. I will also be using their install directions, so I like to encourage them.

Update 8/10/11: The replacement came from iFixIt in a couple of days. It was very well packed. iFixIt includes a mailer to return the old supply so it can be "recycled". I think that means returned to Apple to be refurbished. Please do that, there can't be too many of these in circulation.

As usual, installation was trickier than the iFixIt  video suggests. I suggest look at user notes on all the G5 supplies they sell to get more tips. Here's what I wrote:

1. It is very hard to disconnect the optical sensor cable from the motherboard. There's no hidden catch, you just have to insert your spunger/thin screwdriver blade between the fittings and gently twist. I used a surgical clamp to also pull on the cable -- that did it. (The cable is being replaced, so you don't need to worry about it).
2. The top right screw is hard to remove. I had to partly remove it, then lever the power supply up as in the video while continuing to loosen it.
3. I used thin wide screwdriver blades to disconnect the power supply connect, my spudger wasn't rigid enough.
4. The supply has clearly been used before. In the context of something this old "new" means Apple refurbished. That's fine.
5. Beware the optical sensor, it's glued to the power supply. Look for it. When you insert the new supply place it first.

Even though my supply lasted a reasonable (but not great) amount of time, I've been annoyed at Apple for the high failure rate on the G5 iMacs. Going through the removal process though, there's nothing "cheap" about this bizarre and exotic "power supply" with its attached optical sensor. Apple must have been very unhappy with the manufacturer; I bet there's an interesting story buried in this supplies high failure rate.

iFixit included a $5 off coupon code. I'll never remember it, so feel free to try it: 5611FIXIT.

Lastly, the repair does seem to have worked. With the old supply machine shutdown less than two minutes into the hardware test. This time it completed a 1.5 hour hardware test.

Thursday, August 04, 2011

Oracle ODBC access with 64 bit Windows 7

I know it's a dying technology, but I still get a lot of value out of Microsoft Access manipulation of data stored in Oracle tables. I have a Windows 2003 server VM that runs Access 2003 and has 32 bit driver access to our corporate Oracle tables.

We're moving to Windows 7 (finally, and boy is Win 7 ugly), so in addition to my ancient VM I looked into using Access 2007 with those tables. The first thing I discovered was the 64bit Oracle 10.x installer didn't install the expected Oracle ODBC drivers. I also noticed that Windows no longer includes Microsoft's ODBC driver ...
Data Access Technologies Road Map

... Oracle ODBC and Oracle OLE DB: The Microsoft Oracle ODBC Driver (Oracle ODBC) and Microsoft OLE DB Provider for Oracle (Oracle OLE DB) provide access to Oracle database servers. They are built by using Oracle Call Interface (OCI) version 7 and provide full support for Oracle 7. Also, it uses Oracle 7 emulation to provide limited support for Oracle 8 databases. Oracle no longer supports applications that use OCI version 7 calls. These technologies are deprecated. If you are using Oracle data sources, you should migrate to Oracle-supplied driver and provider....
I spent a few minutes poking around the net, and it looks like there's no easy way to install Oracle's drivers into 64bit Windows. Indeed, it's not clear they exist. I'll do a bit more research with some more focused searches and post an update here.

Progress, as is usual, is a mixed bag. Access was an ugly, awkward Frankenstein application, but there's nothing like it for mixing and matching a wide range of disparate data sources. The deeply nested and reusable query modules could be horrendously slow -- but for what I do the performance was often adequate.

I'll miss Access.

Update: Superuser.com tells me that there exists a 64bit Oracle 11g driver. However, the user's unspecified version of Access is 32bit and it can't use the 64 bit driver. We're on Oracle 10g.

Wednesday, August 03, 2011

Wet iPhone: prevention and treatment

The iPhone is too precious. The fragility is not the big problem; any well made case seems to make an iPhone as durable as most any other phone. It's the water resistance. Or rather, the lack of resistance. When it comes to water, the iPhone makes Barack Obama look a tough negotiator.

It doesn't have to be this way. There's not much good to say about the obsolete Blackberry, but it's pretty good at surviving a swim. Maybe Apple will make some iPhone 5 or, more likely, iPhone 6 improvements. For example, they could go to a different connector, or get rid of the water-vulnerable home button.

In the meantime, every iPhone user needs to know the water drill. Go right now and read the Apple Core's overview. I've been through the rice version of this drill several times (family of five + 1 dog = 5 iPhones with 3 SIM cards = water practice). The key steps are:

  1. Wipe (shirt can work), remove case, wipe/shake water off.
  2. Power down the phone. Don't check to see if there are problems.
  3. Dry thoroughly. (I avoid compressed air, might push water into case).
  4. Place in a sealed container or baggie of rice (brown is best) or, if you have some stockpiled, surround with DampRid pouches (Amazon sells 'em).
  5. Leave in a hot dry environment for 24 hours. Some experiment with car in sunlight -- I worry a bit about too much heat. I like using radiant heat from an incandescent bulb.

Memorize and be ready. Remember, a new iPhone 4 is through;">$600-$700 $250 or so. You don't get the subsidized price unless your contract is up, and then you get a new contract a non-warranty iPhone repair will cost about $270 or so. [1]

That's treatment. Prevention is better. Most iPhone cases don't seal off vulnerable areas; I'm considering the Otterbox Commuter because of the port plugs. If you're boating, or even biking/walking in a downpour, you want a waterproof pouch like the Seattle Sports Dry Doc Digi Case. I bought one for my bike bag, but after my the middle kid's phone did yet another night in a rice bed I made it his phone case:

He can use the phone through the case in most locations, including anywhere outdoors. In his bedroom and in the water-free living room he uses the naked phone. He's happy with this arrangement, and I'm buying another waterproof case for my own phone and (another post) my MacBook Air.

[1] Correction! Martin reminded me in comments. I was thinking replacement, but in this case the phone is not lost. Apple will do refurb swap for about $270. I don't know, however, if this implies a contract extension.

 

Saturday, July 30, 2011

Google+: Circles are for both access control and subscription lists

The Google Reader UI lets me manage people who post once a year and newspapers that post 100 articles a day.

For example, the NYT Science feed is in both my Science folder and my NYT folder. The Science folder I read closely. The NYT folder I scan, and I "mark all as read" after picking a few interesting headlines.

So Google Reader can handle all kinds of traffic volumes, but G+ used to overwhelm me. A few high volume posters were clogging my read. Then I finally realized I'd misunderstood Circles.

Circles, I thought, were about access control. I thought Circles defined collections of people (once we called these mailing lists) who were able to read what I posted to them (notify and access).

I was partly right. Circles are access control. Circles, however, also define subscriptions or streams. They are, in this sense, analogous to the folders in Google Reader, where each person is a 'blog'.

It's not hard really. Circles are just collections of people. Those collections of people can be used for both access control (who you post to) and who you read (stream) [1]. So a person may be part of a Circle I post to, but I may rarely read their high volume posts (Guy cough Kawasaki cough).

Most of my posts are to "Your Circles" or "Extended Circles". That's a big set. On the other hand, my primary "stream" is a set of people who post a few times a day and have something interesting to say. I call that circle "Conversational".  "High Volume" is made up of the yackers with thousands of followers.

With the G+ web interface Streams are on the left side, but only the first ten or show Circles created display there. "Conversations" wasn't showing until Google+ added Circle ordering. Now "Conversations" is first on the list.

On my iPhone's Google+.app it's not obvious how I csan follow my "Conversations" stream. It's buried away in the app's oddball UI. Here's a rough guide:

  1. Tap Circles
  2. In Circles screen there are two tabs at the top: People and Circles (yeah, that's weird). Tap the Circles tab.
  3. Tap a Circle ("Conversational" in my case)
  4. In "Conversational" there is a list of people, and at the bottom of the screen there are 3 buttons/tabs to press. Press Posts. There they are.

Did I mention that the Google+.app UI is as incoherent as post-Jobs OS X (ex: Lion)?

I think Google could have done a better job of explaining this. Looking at their iPhone app I suspect they didn't fully understand Circles themselves.

[1] Fellow Geezers, think radio station.

PS. I still want iTunes style "Smart Circles".

Thursday, July 28, 2011

Apple's $1000 docking station

Anyone can sell a laptop docking station for $1000.

Only Apple can make something that seems almost worth it ...

Apple Thunderbolt Display (27-inch) - Apple Store (U.S.)

With just one cable, connect any Thunderbolt-enabled Mac and get 27 inches of high-resolution screen space, high-quality audio, a FaceTime HD camera, FireWire 800 and Gigabit Ethernet ports — and a Thunderbolt port you can use to daisy-chain additional high-performance peripherals such as hard drives and video capture devices...

... The Thunderbolt Display includes a MagSafe connector that powers and charges your MacBook Pro or MacBook Air. The connector sits on your desk, ready and waiting. No need to unwind the cord to the power adapter that came with your notebook. Leave it exactly where it is, in your bag.

Yes, it's insane.

And yet ...

If I wanted the best of all worlds, and I was single, the combination of an 11" MacBook Air and the Thunderbolt display would almost make sense. Hang storage and peripherals off the display, plug in power and Thunderbolt cable, and the MacBook Air becomes a serious iMac contender. Disconnect and travel with an ultraportable.

A 27" iMac is $1,700. An 11" MacBook Air is $1,200. Together they come to almost $2,900. The MacBook Air and the Thunderbolt Display together are "only" $2,000. Really, cheap by comparison.

Heavens, but Apple is Satanic.

PS. Anyone remember the Powerbook Duo? Aka MacBook Air 1.0, but with 3 much cheaper docking station options.

Restoring an XP backup (.bkf) file in Windows 7

Based on a long history of problems with copying GBs of data over the LAN, I decided to move my data from a corporate XP box to a Win 7 box using XP Backup. That old utility is stone simple, but for me it's been fast and reliable.

I mounted a share on the W7 machine then ran backup to put every bit of my old machine into a .bkf file on the new machine. From there I'd unpack at leisure. In a month or so, once I'm satisfied I've not lost key data in a crevice of XP, I planned to delete the .bkf file.

Naturally, I did a small test first.

Obviously, or I wouldn't be writing this, the test failed. Windows-7 no longer supports restores from XP backup files.

I was open mouthed. This is the sort of middle-finger gesture I'm used to getting from Apple. Whatever their many, many faults, Microsoft has always been kinder to data. The formats are usually proprietary, but at least they're supported.

I couldn't believe it, so I looked further.

Happily, my faith was justified. You can now download a Microsoft Win 7 utility that will restore from a .bkf file. Description of the Windows NT Backup Restore Utility for Windows 7 and for Windows Server 2008 R2. It worked for me.

Wednesday, July 27, 2011

Lion: the curious case of the stingy desktop pictures

My copy of Snow Leopard has seven folders of desktop pictures, about 35-40 images.

OS X Lion comes with 14 images total. Stingy and weird.

It's not the only odd thing about Lion. OS X 10.7 feels like post-Jobs Apple; a compromise mashup between OS prosumer and OS lite. More on that in a future post.

Sunday, July 24, 2011

Viewing Mac OS X Parental Control files

One of the many signs that OS X parental controls are half-baked is that Snow Leopard's default log tool doesn't actually .. you know ... display the site history. It's not just Snowie, this is old incompetence.

I'd wondered if there was any way to actually view the sites visited; perhaps a way to load the records in another tool. My Google searches found nothing, but a question on the most illustrious superuser.com site brought a comprehensive answer.

The answer was excellent even though I started out with a misleading question ...

OS X stores Parental Control logs in /Library/Application Support/Apple/ParentalControls/Users/[username]/year/month with the extension .data.

For example, 15-usage.data contains usage data for the 15 day of a month.

The log files are system read/write only. To access them one must change permissions or use terminal.

I would like to be able browse these files. In an Apple discussion I found a reference to using a "SQL" add on for Firefox to browse them. I guessed this meant SQLite Manager for Firefox, but I the SQLite browsers I've tried can't open the file.

The file is binary, but in a text editor it shows typical Apple .plist header.

I suspect a form of SQLite, or Core Data (which I think can use SQLite).

Does anyone have information on how to browse these files?

My question was misleading because the date-specific .data files are a red herring. The real data is in /events.data ....

osx - How can I view Mac OS X Parental Control files with format .data? - Super User (answer from Daniel Beck)

These date-specific files are regular binary plist files created from a Core Data object graph. Open with Xcode 4 or Property List Editor (comes with Xcode 3), or any text editor after you convert it to XML using plutil -convert xml1 filename.data -o filename-xml.plist in Terminal. The content is pretty much useless though, unless you know how to load it again.

Much more interesting is /Library/Application Support/Apple/ParentalControls/Users/username/events.data. This contains the user-specific applications, web sites and chat protocols in a SQLite container format. Open e.g. using Base, other tools here and here. The date columns are seconds since a date and time in early 2000.

For me, comparison of the GUI value and experimentation showed the 0 value to be Jan 2, 2000, at 2:00:00 AM. Dates shown are May 18 according to the UI. I suggest you focus on this file only; I believe the others are simply helper files for internal data structures.

Incidentally, Daniel Beck lives in Germany has 770 answers on superuser.

Friday, July 22, 2011

Google Voice and merging app and non-app Google accounts with the same user names

This is painful. I hope you don't have to understand it. It may help you to know that you will probably lose data if you merge accounts. In some cases you will be better off to avoid account merging.

If you're reading this, however, you probably do need to know how it goes. Before you begin, consider reading a post from November 2011 2010 - Why you may want to wait on the new Google Apps services - identity collisions.

Here's the problem, which Google calls conflicting accounts.

Consider the Google Apps domain "skynet.com" and a user "hal@skynet.com". Hal uses google mail at skynet.com, but he doesn't actually have a Google Account. He's merely a Google Apps person.

A year ago Hal wanted to sign up for Google Voice. To do that he needed a Google Account. So he signed up for one using his email address hal@skynet.com for his username. Note he won't get email this way, but he can get everything else Google provides.

Meanwhile, Google wants to unify their infrastructure and unite their Google Apps accounts with their Google Accounts. Every Google Apps user will now get a Google Account and most Google services (I don't think G+ is available for Google Apps users however).

Eventually Google moves Skynet.com to the new infrastructure. Now we have a problem. The username hal@skynet.com now has two potential Google Accounts. The old one with Google Voice and the one Google just created.

This has to be resolved. Hal can either change the username for his older Google Account, or he can discard his old account and merge a very few services into his new Google Apps Google Account.

Phew. Reread until your head hurts.

Anyway, I'm now doing this for Emily and my son Tim, both of who have to resolve this conflict now that Google has forcibly upgraded our family domain to their full service range. (Which is mostly good, except for this merger business).

It turns out this works pretty well for Google Voice -- except you lose any old GV contacts.

You begin the process by logging into your Google Voice account with your preexisting Google Account credentials. Then you're told you can either rename or merge. If you merge you can still access your old data (for a while) under a new username of the form: name%old_domain.com@gtempaccount.com.

You're walked through a series of screenshots as below:

Note that 8 months after Google started down this road they still can't migrate most products:

Here's how it looked after its done.

Tim really only used Google Voice, so his migration is pretty simple. Emily used a few services, I'll have to do manual data migration for these. Losing the Google Reader records are particularly painful. In particular "...  this process will only move your feeds, and will not move your trends, followers, people you are following, folders, shared links, or other information associated with your Google Reader."

Really, it's a pain. I expected Google would manage this better, but it is what it is.

Update: I ran into several small and medium bugs during the process. The worst bug is that Google continues to route logins to the conversion screens even after conversion has been completed.

In the end the primary data losses were with Google Reader and iGoogle (bookmark list). I think some of the bugs may be related to other changes Google is making to switch to G+

Thursday, July 21, 2011

Contact Sync and Database.sqlite3 corruption bring Mail.app and my fast iMac to its knees

Sometime over the past two weeks my relatively new iMac seemed to lose steam. It was slow to respond, lots of beachballs. Felt like it was occupied, but Activity Monitor didn't show anything obvious.

I think OS X was caught in a sync loop involving Spanning Sync, OS X iSync and MobileMe sync all synchronizing between OS X Address Book, my iPhone, MobileMe Address Book, and a subsection of Google Contacts. That setup has worked well for about a year, but it's fallen apart now.

Looking at the Spanning Sync logs a few contacts were being updated constantly. Nothing special about them I can see.

I'm afraid my Contacts Unification program has died. With MobileMe on the way out, and with Google frantically tweaking Contacts for their social/G+ initiatives, and Apple doing its own Lion and iCloud contact management I don't think this is going to come back. I'll need another approach.

For the moment I've set MobileMe sync to manual and disabled Spanning Sync. I may do a manual sync every few days. My iMac is working again.

Synchronization is Hell.

Update 7/22/11: This morning I received a warning from Carbon Copy Cloner about a physical read error with Library/PubSub/Database/Database.sqlite3. Interesting ...

07/22 08:25:58 rsync: read errors mapping "/Users/jfaughnan 1/Library/PubSub/Database/Database.sqlite3": Input/output error (5)

07/22 08:26:22 ERROR: Users/jfaughnan 1/Library/PubSub/Database/Database.sqlite3 failed verification -- update discarded. (51)

Disk Utility didn't find any physical errors, so I assume Database.sqlite3 has been corrupted.

I put Database.sqlite3 in the trash, logged out and back in, then deleted it. Mail.app recreated it, went from 7MB to 2MB. Safari and Mail.app both felt much faster. I then downloaded the most recent version of Onyx, restarted as Admin, then ran all the cleanup and automation scripts. At the moment the machine feels about 10 times faster.

Even though sqlite3 is a core part of OS X Data Management, but it's hard to find much about how it's actually used in most apps. I found one page that listed apps that use SQLite databases, but those apps are listed as storing data in different locations. I found a couple of references [1] that suggest this is where Mail.app and Safari store their RSS feeds.

One article mentioned using this command to fix this sqlite database:

/usr/bin/sqlite3 ~/Library/PubSub/Database/Database.sqlite3 vacuum

Using that search string brought up more interesting articles:

The second link is from 2009, and it sounds very much like what has been happening to me in OS X 10.6 ...

I am syncing, on several Macs and several user accounts, information such as Calender, Mail Rules, Bookmarks, etc. After recently updating to Safari 4.01 and OS X 10.5.7, all of a sudden I had all very bad Safari performance -- including constant freeze situations. After being ready to delete the impacted user, I realized that there were some issues with the database.sqlite3 file in the Library » PubSub » Database folder. The PubSub folder is used for tracking RSS feeds, and it seems my problem resided there.

After deleting the database.sqlite file, and resetting the Mobile Me information, the freezes and crashes stopped...

Deleting this file did not actually remove the feeds from Mail.app and Safari.

Looking at my feeds I see I've been tracking my Google Reader shared item feed. That is an enormous feed; I think I've been pushing the limits of what Mail.app RSS subscription can handle. I deleted all of my Feed subscriptions from Safari and Mail.app, then I delted all the data in ~/Library/PubSub/Feeds and I deleted Database.sqlite3 (again). On logout/login it was recreated with a size of 74kb (empty). Mail.app is now blindingly fast and my system is healthy again.

I won't be using Mail.app's feed reader features any more. They don't scale. I use Google Reader, but to archive some of my feeds I'm going to buy a dedicated standalone feed reader.

Update 7/24/11: I created an archive of my Address Book, cleared the iSync database then restarted MobileMe. It told me it was going to add 843 records. Coincidentally, that's how many I have. I went ahead anyway, since it's surprisingly easy to save and restore Address Book archives (I have about fifty versions saved). In fact I ended up with 843 that look correct on spot check. Curiously, both MobileMe and my laptop say I have 842 contacts. So there's something broken somewhere in iSync. It's easy to see why Apple dropped iSync (so far) from Lion. Synchronization is, honestly, and truly, Hell. This has underappreciated implications for health care interoperability incidentally.

The massive security hole in Google two factor authentication

I've been using Google's two factor authentication for a few months. It works reasonably well for the core Google App suite (gmail, calendar, contacts, etc) from a web UI if I use Chrome.

Even there, however, there are bugs. Even on machines I don't authorize for '30 day use' I sometimes connect without a request for an authenticator token. I think this is improving, but there's still no way to de-authenticate a '30 day' machine from the Google Account.

Beyond the core services though, there are lots of problems. The worst of these is Google's "Application Specific" password framework. It's the software equivalent of medical malpractice.

The problems start with the misleading name. There is nothing Application Specific about these passwords. If you write one down, or if one is captured by a keystroke logger, it works with most (all?) Google services. The same password can be used with an IMAP client to download email or with Google Chrome to sync passwords. If you know one has been lost it can be revoked, but of course by then it's too late.

The only sense in which these "additional passwords" are "application specific" is that Google has us label them by application. This is worse than worthless, it's misleading.

I find I have to use these "additional passwords" very frequently. Today, when I tried enabling Google Sync in the very latest Chrome release, I was asked for one. That was on a less-trusted machine, if a keystroke logger were running it would have been lost.

Obviously, I'm disappointed. Actually, I'm kind of appalled. This smells like a marketing maneuver. Somewhere in Google there are security people contemplating honorable seppuku.

1Password fails to sync - they have problems

Synchronization is Hell.

I know that, so I wasn't surprised when 1Password became increasingly messy. It had multiple logins with different passwords and I don't think it was synchronizing correctly from desktop to iPhone. I decided to start over.

Fortunately I've never trusted 1Password, so the "source of truth" for my passwords is a 15yo FileMaker Pro database with about 1,600 records. It's not only a credential story, it's a history of the WWW (as we used to call it.) So I deleted everything in 1Password desktop and did a sync to my iPhone. There's no UI indicator that sync is happening, but shortly thereafter there were about 3,200 records on my iPhone and 1,600 on my desktop.

Right.

So after some messing about I hit the "reset" button in 1Password/iPhone and tried to sync with the OS X app overwriting the iPhone.

Nothing happened. There was no error message, but clicking on the sync button didn't do anything.

Google eventually took me a to a very long 1Password tech support thread. It's sad reading -- clearly 1Password is in trouble. Towards the end I saw something promising ....

How to Sync 1Password on Mac to my iPad - AgileBits Forums: "defaults write ws.agile.1Password ShowWiFiSyncAuthAutomatically -bool YES"

Terminal hacks usually work. This one did. When next I started the desktop app I got the dialog for entering my 'secret codes' and I was able to sync. Everything is clean for the moment.

Obviously, 1Password doesn't meet my tests. My guess is that their too ambitious for their technical abilities. They've tried to make synchronization automatic and invisible, but they failed to provide a manual option for when things go wrong. Sync is Hell, things will go wrong.

What I really want is the old FileMaker Mobile app for the Palm. There's nothing like it now; the closest today is Bento's ability to sync desktop and iOS device. I'd go for Bento, but there's no iOS encryption option. So it doesn't work.

For now, 1Password is my least bad option. I can't recommend it for anyone else however.