Password hashing function almost by definition does not handle any data that must be protected from the user, so side channel leaks do not make much sense. Only secret information comes into play in final comparison of hash of user supplied password and your stored hash and I don't see any way of exploiting possible timing leak in that comparison that does not require breaking the hash in the first place.
Side channels don't matter for bcrypt.
Re:Django-bcrypt
by koenigdavidmj on Friday February 04, 2011 @11:04AM
(#2179880)
Can you explain why this is? (Not doubting you; just curious.)
The online operations exposed to an attacker in a bcrypt system are done almost entirely on attacker-known data.
Be careful.