Jump to content

Trcx

Active Members
  • Posts

    7
  • Joined

  • Last visited

Posts posted by Trcx

  1. I would have praised him if he had went to the IT department with his findings (instead of parading the feat around and showing his teacher). Plus from what it looks like to me like no one has gotten the kid to reenact this exploit so the administrators can fix the issue.

    While I understand your sentiment, I would say that going to the teacher was the right choice as most k12 systems don't have the IT department in the building unless they are fixing an issue.

    I'm not sure that I agree with the praise sentiment, but punishing him is definitely the wrong direction to go. If he is anything like me it would not discourage him from "tinkering" with computer, but rather discourage him from reporting vulnerabilities.

  2. No problem. It works for most distros. There have been occasions where I've been able to completely negate its need by writing a custom grub config, but I don't remember how to do that....it was late and I didn't bother writing down the steps and I haven't had the time to figure it out again. Now I'm working on compiling the b43 drivers under backtrack...it's not proving to be be as easy as under debian. I just found out that there are published patches to enable packet injection and such...just hoping that it will work. Because then backtrack will probably be the next distro that I run on my mac.

  3. The problem is that most distros mount the cdrom the wrong way (at least from what I can tell), causing the partial boot problem. The solution is to "burn" the iso to a usb drive using dd.

    It's been a while since I've used OS X, but the commands should go something like:

    diskutil list/code]
    
    insert the usb drive to burn too and rerun
    
    [code]diskutil list/code]
    
    Figure out which drive number OS X assigned to the USB drive, this should be fairly obvious as it should be the only new entry in the command's output.  
    Now run
    
    [code]sudo dd if=/path/to/BT.iso of=/dev/diskX bs=1m

    Where X is the drive number that you determined earlier. If it throws an error about the 1m not being a real number use 1M instead. dd will not show any progress, but generally for me it takes around 10 minutes, but (obviously) that depends on the size of the iso. You can have it display how much of the iso is copied though by sending it the USR1 single. Something like

    kill -USR1 <pid>
    

    where the pid is the process id of dd, something that you can find through the top command, or ps -A.

    Finally, boot the cd-rom, but have the newly burned usb drive inserted, now when it searches for the live filesystem it will find it residing on the usb, and will boot into the distro.

×
×
  • Create New...