Not to mention, the article mentions using HMAC for his password databases.  I am not sure how this is any better than salting.  His argument against salting was that the salt is going to be stored somewhere.  Well, the key he is going to use with HMAC is going to be stored somewhere too.  In general, hashed password storage is a tough game to win in an absolute sense.  So, we are effectively left with slowing the attacker down to the point that it isn't worth their while.  I didn't see any mention of using iterative hashing (aka stretching) to increase the time required by an attacker to brute-force passwords.  I agree with your "TLS in motion and PGP at rest" quote, though I don't know if we have a similar thing we can point to for password storage.  Is there a go-to library we can just say "hey, use this".  I know we can use bcrypt, or do iterative hashing, etc.  But, I don't know off the top of my head what stock library we should tell folks to use so they minimize the chance of shooting themselves in the foot with password storage.  Maybe this is something that should be added to keyczar.