On 10 October 2014 12:45, Stephen Frost <sfr...@snowman.net> wrote: >> >> This gives the vague impression of security, but it really seems just >> >> the placing of a few obstacles in the way. >> > >> > One might consider that all security is just placing obstacles in the >> > way. >> >> There's a difference between intending that there shouldn't be a way >> past security and just making access a matter of walking a longer >> route. > > Throwing random 16-digit numbers and associated information at a credit > card processor could be viewed as "walking a longer route" too. The > same goes for random key searches or password guesses.
But those would need to be exhaustive, and in nearly all cases, impractical. Data such as plain credit card numbers stored in a column, even with all its data masked, would be easy to determine. Salted and hashed passwords, even with complete visibility of the value, isn't vulnerable to scrutiny of particular character values. If it were, no-one would use it. Thom -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
