Posts Tagged ‘MySQL’

o’reilly mysql conference & expo 2010

It is my pleasure to be your Program Chair, for the O’Reilly MySQL Conference & Expo 2010, to be held April 12-15 2010, in Santa Clara, California.

It is of course, not something I embark on alone. I have a program committee, comprising of some amazing folk: Brian Aker, Kaj Arno, Roland Bouman, Sheeri K. Cabral, Robin Schumacher, Baron Schwartz, and Jeff Wiss.

I can highly encourage you to submit a proposal. You have till January 27, 2010, which basically means, less than a month, so get cracking! I also can highly recommend you to register as an attendee.

I’ll talk more about the processes, et al, in a later blog post, but I want to ensure that in 2010, we are going to be completely open and transparent in our decision making process. And I want you, the MySQL community, to participate. Watch this space for more details.

And again, its a great honour, being your Program Chair for the conference in 2010. I expect it to be a blast.

Harish Pillay and Brian Aker debate with Richard Stallman (Part 2)

The attendees were not satisfied with the first answer RMS gave to Brian, that Harish Pillay (Chief Technical Architect, Red Hat Singapore), chose to ask RMS what more he had to say, with regards to the letter he’d written. He answered quite candidly in this video, which Brian chimed in for as well.



The back channel for all this was Twitter… Don’t hesitate to follow @harishpillay, @brianaker, @piawaugh or even @webmink (Simon Phipps, while not at the event, was available on Twitter). Some interesting reading, naturally.

Brian Aker debates with Richard Stallman

At foss.my 2009, Brian Aker asked Richard Stallman at his keynote, about the Oracle/Sun acquisition (with a focus on MySQL), with regards to the parallel licensing approach used by MySQL. Brian was referring to:

As only the original rights holder can sell commercial licenses, no new forked version of the code will have the ability to practice the parallel licensing approach, and will not easily generate the resources to support continued development of the MySQL platform.

from Richard’s Letter to the EC opposing Oracle’s acquisition of MySQL. Listen to the discussion between Brian and Richard.



Flickr’s upgraded shard

While going about my day, I stumbled upon John Allspaw’s tweet about his experience with MySQL 5.0.51 versus Percona’s 5.0.83 highperf Percona build. For those that don’t remember John from the MySQL Conference & Expo’s, he’s the guy managing operations at Flickr, and he recently even wrote a book about webops.

Click on the photo above, to see when the upgrade happened. Amazed?

Haven’t tested this out myself, though I’m curious to see how this stacks up against MySQL 5.4, which is also aimed at being a high performance release. In another note, it seems like the mysql-cacti-templates could use a bit more verbose documentation.

MySQL in RHEL5/CentOS5 gets an update

It’s worth noting that Red Hat Enterprise Linux (RHEL) 5 has had an update to MySQL in the last month. This naturally means that CentOS 5 also had a similar update. It’s now bumped up to MySQL 5.0.77 (goodbye 5.0.45!; which is what RHEL5 shipped with). This is a moderate security release, so consider updating, if you can afford a mysqld restart.

Read more about the 4 CVE bugs fixed. CentOS followed suit within two weeks.

SecuRich

I got to meet, and share a meal with a most interesting Darren Cassar at FRoSCon/OpenSQLCamp, who’s the mastermind behind SecuRich. Some sparse notes, while we await his slides. I think there’s some great potential here, and SecuRich is exciting and should be given some more love.

Designed to work with Sybase and MySQL in mind (because he’s hacking on migrating Sybase to MySQL).

How often do we audit user privileges and access levels? How often do we forget temporary elevated privileges?

What you have in MySQL today: Authentication against ‘username’@’hostname’, and the password is hashed by PASSWORD() function. There is wide range of privileges, and the granting of privileges is controlled.

What are limitations in MySQL today: Password limits are not available (password size limit, password history, password complexity meter, password minimum age), its quite complex to manage, there are no roles, it is easily unsecured (if you provide an access to the MySQL database, you can try brute force attacks, etc.). Once you drop the database, the grants are still there – obsolete grants are not removed.

SECURICH has password limits, reduces complexity to manage, has roles, is a lot more secured, and soon, there will be removal of obsolete grants.

Compatible with MySQL 5.0 and later, as it uses INFORMATION_SCHEMA extensively. It requires I_S.processlist, which is only available in MySQL 5.1 though.

I don’t see why this wouldn’t work on Windows, besides some scripts written in BASH. My only experience with this is however on Linux and OSX.


i