ourdelta-developers team mailing list archive

[Arjen Lentz <arjen@xxxxxxxxxxxxx>]

Hi Gertjan

On 20/07/2009, at 8:31 PM, Gertjan Oude Lohuis wrote:
> Sorry, you are right. But please do acknowledge that people who take  
> the
> time to isolate and report bugs also do this voluntarily. Having them
> wait more than three months for an answer is not very friendly. I  
> think
> "reasonable request. should be fixed." shouldn't have taken longer  
> than
> two minutes to decide and write, and that is a hell of a lot more than
> no reply at all. ;-)

Quite so - and since we may presume goodwill, you may consider that  
perhaps the original notification was somehow missed.


> But we do appreciate your work deeply, so I appologize for the tone  
> of my comment.


Thank you.


Cheers,
Arjen.
-- 
Arjen Lentz, Director @ Open Query (http://openquery.com)
Exceptional Services for MySQL at a fixed budget.

Follow our blog at http://openquery.com/blog/
OurDelta: free enhanced builds for MySQL @ http://ourdelta.org

-- 
INNODB_BUFFER_POOL_CONTENT privacy issue
https://bugs.launchpad.net/bugs/352840
You received this bug notification because you are a member of OurDelta-
developers, which is the registrant for OurDelta.

Status in OurDelta - Builds for MySQL: Confirmed
Status in Patches for MySQL by Percona: New

Bug description:
INNODB_BUFFER_POOL_CONTENT does not prune rows returned in terms of what databases/tables the requesting user has access to. In many environments it is unacceptable for user to have access to data about the names of all database and table that exist on the instance.

I suggest that access to INNODB_BUFFER_POOL_CONTENT be restricted to user that have the SUPER privilege.