Creating an iso on Mac OS X

I know that a lot of you have done this already, but I always forget the best way to create an iso from a cd on the Mac.

I ran across an entry on a forum (http://forums.macrumors.com/showthread.php?t=220740#6) from tgage who gave the following:

From within Terminal (Applications->Utilities->Terminal)

Mac OS X Tiger (10.4)

You can determine the device that is you CD/DVD drive using the following command:

drutil status

Vendor Product Rev
MATSHITA DVD-R UJ-825 DAM5

Type: CD-ROM Name: /dev/disk1
Cur Write: 16x CD Sessions: 1
Max Write: 16x CD Tracks: 3
Overwritable: 00:00:00 blocks: 0 / 0.00MB / 0.00MiB
Space Free: 00:00:00 blocks: 0 / 0.00MB / 0.00MiB
Space Used: 66:55:27 blocks: 301152 / 616.76MB / 588.19MiB
Writability:

Now you will need to umount the disk with the following command:

diskutil unmountDisk disk1

Now you can write the ISO file with the dd utility:

dd if=/dev/disk1 of=file.iso

When finished you will want to remount the disk:

diskutil mountDisk disk1

Thats it.  Just wait for it to finish creating the iso and you are good to go.

Firefox 4 Security Features

http://isc.sans.edu/diary/Firefox+4+Security+Features/10594

On March 22nd 2010 Mozilla released the long awaited firefox 4 browser.  Of the improvements to the browser Mozilla added what is referred to as "XSS and Content Security Policy (CSP)".  This does a rather decent job at preventing certain browser pop-ups/alert boxes.

However, for someone that plays around with XSS and loves alert boxes this was a slight problem.  You won't find CSP in any of the menu options but you will find it in 'about:config'.  If you do a search for CSP you will find the following two entries:

security.csp.debug - false
security.csp.enable - true

If you want to make sure that you can test your alert boxes it is highly recommended that you go and mark 'security.csp.enable' as 'false'.

Can't run update-manager even if I am in the sudoers file (Debian)

First I would like to send a major thanks you Mike for finding the answer to my question.

I was trying to run the update-manager but it was not playing nice.  Every time I would launch update-manager it would ask for the "administrator password" which I didn't want to use.  This also prevented me from running other applications as well (anything under the administration section in Debian).

Mike ran across the following article which suggested the following:

run "gksu-properties" and change "authentication mode" to "sudo".

That's all folks, things work just fine now.

http://www.linuxquestions.org/questions/debian-26/changing-graphical-auth-method-su-to-root-gksudo-856640/