That's why you do an audit, to determine if there is "much to break" or not. Maybe it's caching passwords in a tempfile somewhere, or it uses "4" as it's rando

That's why you do an audit, to determine if there is "much to break" or not. Maybe it's caching passwords in a tempfile somewhere, or it uses "4" as it's random seed every time, or any one of a million other things that could go wrong. Nobody knows until they read the code. I'd rather use an audited Password saver program, everything else being equal...