Reset FireFox Master Password

September 30th, 2008

If you get into a pickle and are unable to remember your master password and you are willing to lose all the passwords stored in your FireFox password database, then this tip should help you.

Enter the following into your browser bar and press enter :

chrome://pippki/content/resetpassword.xul

Next you will asked you to confirm the fact that you are going to lose all the passwords stored in your FireFox password database. If you are positive you wish to continue then click the “reset” button.

Note : You should use the above command on your own password database or with the express permission of the password database owner. Your friends will most likely not be amused if you waste their time by making them restore their password database from a backup.

Enable ACL’s on Mac OS 10.4

September 11th, 2008

ACLs may be enabled or disabled on a per volume basis. By default ACL’s are not enabled on Mac OS Tiger systems.

If you are not really sure what ACL’s are then before enabling them you should check out this informative article at Ars Technica.
On Mac OS X Server, the WorkGroup manager will allow you to enable ACL’s on a per volume basis. However, on Mac OS X Client systems you must use the command line to enable ACL’s.

  • Enable ACL’s on the root volume :

% sudo /usr/sbin/fsaclctl -p / -e

  • Disable ACL’s on the root volume :

% sudo /usr/sbin/fsaclctl -p / -d

The -p option allows you to specify a file system mount point path on which you wish to either enable or disable ACL’s. If no other options are specified then the access control list status will be displayed when using the //-p// option.

Detailed usage instructions are available in the man page.

Restarting syslogd

September 10th, 2008

If you have noticed that some logs stop being updated or created, then it is possible that syslogd has fallen over on your system. This is quite common on some releases on Mac OS 10.4.x.

As pointed out by Extra Pepperoni

syslogd is supposed to reload on “killall -HUP syslogd“, but that never works for me. The functional solution is “sudo launchctl stop com.apple.syslogd; sudo launchctl start com.apple.syslogd“, which gets the logs logging properly again.