News for hackers. Stuff that matters.
Re:The MongoDB hack and the importance of secure defaults by aioprisan on Wednesday January 11, 2017 @01:31PM (#13376219)
You can set up the latest MySQL with a blank root password and open to the world as well. The lack of good security options is a 1.x-ism, now there are plenty of security mechanisms now https://docs.mongodb.com/v3.2/administration/security-checkl...
Re:The MongoDB hack and the importance of secure defaults by morgo on Wednesday January 11, 2017 @02:36PM (#13376794)
It is much harder to do this with MySQL.

The default is now a randomly generated password. You have to overwrite it with --initialize-insecure if you want to setup with a blank password.

Re:The MongoDB hack and the importance of secure defaults by aioprisan on Wednesday January 11, 2017 @04:32PM (#13377666)
I don't buy that. Just did an apt-get install mysql-server and it let me install with a blank password (Ubuntu 16.04 MySQL Server 5.7)
Re:The MongoDB hack and the importance of secure defaults by morgo on Wednesday January 11, 2017 @04:58PM (#13377872)
It is most likely appearing to work without a password because it is using socket authentication (vs tcp). See: http://mysqlserverteam.com/secure-by-default-in-mysql-5-7/

If you want to double check, try 'mysql --protocol=tcp'.

Re:The MongoDB hack and the importance of secure defaults by Sanddancer on Wednesday January 11, 2017 @07:07PM (#13378703)
That's ubuntu screwing things up, not mysql. When you run the init manually -- mysqld --initialize -- it does require a password.
Re:The MongoDB hack and the importance of secure defaults by aioprisan on Wednesday January 11, 2017 @11:15PM (#13379784)
Since we're just talking about defaults, you'd get an equally unsecured MySQL install on the latest and most popular AWS AMI today, as you would with old MongoDB installs.