This question already has an answer here:
- How to securely hash passwords? 12 answers
Passwords of end Users are stored in Database which is encrypted (using one way hash like MD5). Apart from me, there are 'other' people belonging to other teams who have access to Database which means access to schema and the particular table where passwords are stored. By other teams, I mean Database Administrators who will try to know purpose of a column & table for creating indexes, normalization etc. Other teams also include System Administrators who take backups regularly.
Even though am using one way hash, there are sites which will help in decryption of these passwords by matching against their Database.
So, its as good as exposing passwords of end users to 'other' people who are not intended to know. I cannot restrict view permissions of these tables to 'other' people who also have to work on these tables for some other reasons.
Its a question of ethics. But, an attacker doesn't have any ethics(that's what I believe).
What options do I have in this regard?