Skip to main content

Weak Passwords and MySQL

I still remember the day, when I attended my first lecture at this university. The one thing my Prof warned me then was to make sure that I keep my passwords *cryptic*. For me cryptic then meant anything that was not my name or my date of birth. Of course how could I expect somebody to know that a new word could be formed just with my bike license plate number and my sister's name.

Then I was just a kid, someone not exposed to technology, rather someone not exposed to its dark side. But then, I am not alone. People who should know more about this than me, the "system administrators" think on these lines even today too. Else how could a password guessing worm access a flaw in MySQL affecting not one, not two but eight thousand databases!!

Comments

Popular posts from this blog

Gmail Chat Disabled

The fact that it happened does not surprise me but that it took so long for our network administrators to figure it out does. And if you are wondering how do you disable Gmail's chat features on your network, you only need locking DNS lookups to chatenabled.mail.google.com , by returning 127.0.0.1 .

Advertising Billboards as Rain Covers

Advertising billboards are put to use as Pakistani refugees, left homeless after the October 8 earthquake, set up their tents in Muzaffarabad, Pakistan. [via SFGate ] Technorati Tags: Pakistan Earthquake

Community effort to create a single persistence model for the Java community

A community effort led by Sun Microsystems is aiming to create a single 'Plain Old Java Object' persistence model to provide a single object/relational mapping facility for Java app developers in J2SE and J2EE. Paul Krill writes In a letter to the “Java Technology Community” on Friday, specification leads on Java Specification Request (JSR) 220, which is the proposal for Enterprise JavaBeans 3.0, and JSR-243, for Java Data Objects, state that the two technologies feature divergent persistence models. “This divergence has caused confusion and debates among Java developers, and is not in the best of interest of the Java community,” said JSR-220 leader Linda DeMichiel who also is a Sun employee, and Craig Russell, a staff engineer at Sun who leads JSR-243. “In response to these requests [for an end to the unwanted divide], Sun Microsystems is leading a community effort to create a single POJO (Plain Old Java Object) persistence model for the Java community,” the letter said.