Hi dD0T,

thanks for having a close look at my patch.
Regarding the magic '30000' number, I tried to shift the balance from performance, in which case 10000 could probably be considered closer to a safe minimum, toward more security.
More information available here: http://blog.agilebits.com/2013/04/16/1password-hashcat-strong-master-passwords/
But in the end making it runtime dependent is really a better fit for servers (a really nice idea). Would it be a good idea to add a configuration option for overriding (fine-tunning) this value, or forcing to change a database value directly can be considered 'better' in this case?