On 10 October 2014 12:00, Stephen Frost <sfr...@snowman.net> wrote: > * Thom Brown (t...@linux.com) wrote: >> To be honest, this all sounds rather flaky. Even if you do rate-limit >> their queries, they can use methods that avoid rate-limiting, such as >> recursive queries. And if you're only after one credit card number >> (to use the original example), you'd get it in a relatively short >> amount of time, despite some rate-limiting system. > > The discussion about looking up specific card numbers in the original > email from Simon was actually an allowed use-case, as I understood it, > not a risk concern. Indeed, if you know a valid credit card number > already, as in this example, then why are you bothering with the search?
The topic being "column redaction" rather than "column formatting" leads me to believe that the main use-case of the feature would be to prevent the user from discovering the full value of the column. It's not so much point 1 I was responding do, rather point 3, where you don't know the card number, but you get information about it in the results. The purpose of this feature would be to prevent the user from seeing all that data, which is a security feature, but at the moment it just seems to be a way of making it a little less easy to get at that data. >> 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. I wouldn't be against formatting per se, but for the purposes of that, I would say that views can already serve that purpose. -- Thom -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
