Went to PA today for a while and saw a couple of funny things:
This sign was outside of a resturant in Bridgeville, PA:
The second was at Krispy Kreme.. They have a special, all you can eat for $2.99 on Thursday nights:
anything dealing with *NIX or what ever I want to write about
Went to PA today for a while and saw a couple of funny things:
This sign was outside of a resturant in Bridgeville, PA:
The second was at Krispy Kreme.. They have a special, all you can eat for $2.99 on Thursday nights:
So the memory works freaking awesome in MacOSX.. However in BootCamp with Windows XP SP3…. It will only allow Windows to see 1.99GB of ram. That freaking sucks.. So far the only thing I have found that will fix it, is upgrading to Vista or Windows 64 bit… ECK!
IBM’s Xforce published their new 2008 annual report. In it they had this chart:
Surprising is that IBM put’s one of their own OS’s near the bottom of the list. Some of my opinions are :
1. No one uses AIX that much, so no one looks for holes in the code.
2. Any one who uses AIX, doesn’t have it directly connected to the Internet.
3. It is so cost prohibitive to use, that people are looking at Solaris/Linux or Windows to run their business on.
But the funniest thing about this is the last I used AIX the following were still done on install by IBM:
1. telnet enabled
2. root logins allowed remotely
3. no ssh comes with the OS, you have to install a crappy “linux toolkit”, and then install another 10 different packages to get SSH enabled.
4. No RBAC
5. Syslog configuration does not exist
6. Root does not even have a password on install
Seems to me that IBM needs to fix some fundamental issues with their OWN OS before they can say it is not one of the “Most Vulnerable Operating Systems”.
The funniest issue with this is for MacOSX to be listed at the top, all most all of those require some one to actually run something on the machine with administrative privileges.
Quick steps to recovering (aka resetting) the root password on MySQL:
1. Find the PID of the mysql process
ps -aef | grep mysqld
root 11889 11090 0 Jun 10 ? 0:00 /bin/sh bin/safe_mysqld
mysql 11909 11889 0 Jun 10 ? 525:44 /local/mysql-5.0.45-solaris10-i386/bin/mysqld --basedir=/local/mysql-5.0.45-sol
2. Kill the mysql process; kill 11909
Make sure not to use a -9…
3. Create a file that the user that runs mysql can access; and place in it the following:
UPDATE mysql.user SET Password=PASSWORD('FozzyBear') WHERE User='root';
FLUSH PRIVILEGES;
4. Start mysql: mysqld_safe --init-file=/path/to/file &
5. Try to connect as root now, if it works, delete the temp file; stop and restart mysql.
Granted, the above can be done by any one who knows the password for the account that MySQL runs under, or has root access to the machine. I usually leave the mysql UNIX account in a locked state, so no one can su to it, so you have to have access to root, to be able to su to it.