Jump to content

H@L0_F00

Dedicated Members
  • Posts

    834
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by H@L0_F00

  1. Maybe the casper file(s) has to be in a folder named "casper" on your root like with BT4 without editing your init scripts? And just so you know, I don't think it's the init script itself that finds and mounts the casper file system, init calls a bunch of other scripts. I plan on working on figuring out how to move around the casper folder though which shouldn't be too hard or time consuming since I've messed with Ophcrack successfully.

  2. I actually started trying to figure out how to make Ophcrack look in a different folder for the tables a little less than a week ago. I had never touched an initrd or init script ever before. I didn't know that it was archived with both gzip AND cpio. After I discovered this, I tried to edit Ophcrack's initrd in Back|Track... Not a good idea. The file permissions were all screwed up. I finally did get it working though so now I have Ophcrack looking in a couple subdirectories for the tables and it also mounts NTFS and FAT32 file systems as rw so I can save passwords, user names, etc. I plan on working on Back|Track 4 PreFinal next in order to get the damn "casper" folder off the root of my flash drive and with the rest of the BT4 files/folders. That should be easy now that I have an idea of what I'm doing and how to do it.

    I'll post a guide for editing Ophcrack's initrd when I have enough time. It might take a while because I see it as being quite a long tutorial, but it shouldn't take > 3 days for me to get around to it. By all means, try to do it yourself though because that's how you learn and finding things out yourself is much more fun and rewarding when you accomplish what you set out to do :)

  3. I reorganized things to make it a bit easier to read and navigate.

    Please don't change things around if you aren't sure it will still operate the same. Like the splashimage and default commands. They need to be before everything because Grub4DOS executes the file by the order it appears.

  4. Since there's been so many new guides and useful posts coming about I think there are now too many to sticky them all separately, so I'm making this topic, with links to all the things people should take a look at before posting so only one post needs to be stickied.

    How it all started!

    Episode 524

    Episode 524 Topic

    Episode 602

    Episode 602 Topic

    Guides

    [Guide] Making your USB Bootable - Psychosis

    HOWTO: Boot Grub4Dos and Grub2 from one usb - nemesys

    Multiboot LiveUSB (English) - TheHermit

    [Guide] Ubuntu 9.04 Desktop from ISO - Psychosis

    [Guide] Ophcrack Live 2.3.1 - Psychosis

    [Guide] Changing the default Ophcrack tables directory - H@L0_F00 (HAL0_F00)

    [Guide] Change the casper directory in Ubuntu (BT4) - H@L0_F00 (HAL0_F00)

    [Guide] Windows PE - Psychosis

    [Guide] Passwords in Grub4DOS - H@L0_F00 (HAL0_F00)

    Rename, Move, or Remove "menu.lst" - H@L0_F00 (HAL0_F00)

    Other useful posts

    Test your Multipass in a Virtual Machine! - H@L0_F00 (HAL0_F00)

    HOWTO: VirtualBox USB Testing on Linux Host - nemesys

    Multiple Partitions on USB Multipass - Coreyja

    PeToUSB Not Required - ArkNinja

    Grub Menu Utility - Psychosis

    The Definitive USBMultipass Config - Battosia83

    Multipass Grub2 Config

    Some GRUB2 References - numb3rs

    Billix for linux multiboot - nullspace

    Archlinux livecd that can be booted from iso - godane

    Tools and files

    PeToUSB

    Modified PeToUSB (reported to work with larger drives!)

    grubinst and GRUB4DOS

    GRUB4DOS Guide

    GRUB4DOS Wiki

    I'll be updating this when more comes along so you might want to check back every so often. There's also no need to reply to this thread since I'll be actively updating it so please refrain from doing so in order to keep it neat and concise, thanks.

  5. Thank you for posting :)

    I've found out it was sdb1, which I had originally guessed :).

    I then added that to my /boot/grub/device.map, like so.

    (sdb1)   /dev/sdb1

    In my menu.lst, I have this entry.

    title USB Boot Test
    chainloader (sdb1) +1

    .

    I'll test it just now.

    EDIT

    Didn't work. A big fat error 23: problem parsing number. Or something. Damn. Ideas?

    Drives don't always show up as the same device in two different distros, let alone Grub4DOS and Ubuntu. To find out which device it could be in Grub4DOS enter the command line by pressing 'c' after you boot. Type in "root (" and then press TAB. This will show all available drives. Try chainloading different ones. I'm quite certain the drive and the "+1" command need to be one string which also might be what's giving you the error. Use "(drive)+1" instead of "(drive) +1"

  6. Actually, setting it to mount the SD card based on the UUID would be the best bet if you were able to get it working because then you wouldn't have to worry about the drive showing up as a different device on a different machine (which happens quite often in Linux). The only way I know of doing this is modifying /etc/fstab. Modifying the init scripts isn't quite easy. I just started learning about it and it took me about a week just to modify the Ophcrack scripts to search for the tables in "/.multiboot/Ophcrack/tables" as well as mounting all FAT32 and NTFS file systems as rw so that I can save passwords, user names, etc. I'll post a guide on it when I get the time (probably < 3 days) so that you may follow it if you'd like, but you'll want to modify different scripts and lines than I did and you'll have to figure out what those scripts and lines are.

    And with that command, the '|' is called a pipe. It takes the output of the first command and "pipes it" to the second command. The same thing could be achieved by doing:

    gunzip ../initrd.cpio.gz
    cpio -id &lt; ../initrd.cpio

    Note: Use the same distro as root to extract/modify/compress the scripts so that the file permissions stay the same. This was a big problem I had before I realized what was happening and why.

  7. I found a reference to "devicemap" but it returns an unknown command error.

    Is there a help function with Grub2? With Grub4DOS you could use "help map" and it would give you info about "map." You might want to try something like "help devicemap" and see if it returns anything.

    EDIT: Just checked, "help" is still implemented in Grub2. Here's a list of the commands.

  8. Personally I just do not see the point of trying to figure out where the hell we came from other than to give a finger to everyone's religion. This is pointless and time wasting. Besides, in 100 years I'll be dead and so will you so.. I really could care less where we came from.

    I think two things should happen. 1. People should quit pushing religion down people's throats, and 2. non religious people should quit pushing their theories down people's throats..

    That simple. I keep my shit to myself and you to yours. There.. Now we are all happy except the idiots that want to rub other's noses in their own shit because they feel like they owe the world a service to cram their own bullshit down the other's throats.

    Have a nice day! :D

    If we know where we came from, we can better predict where we're going. We might also learn about why we do some of the things we do or why we're susceptible to some diseases or viruses more than others. If we can study our ancestors, we can better understand ourselves. Why not study a simpler model of ourselves? It could only help us move forward. This is hardly about religion at all and I don't see anybody forcing anything upon anybody. If the theories of evolution offend you, don't click the damn link and don't reply to the damn thread. It's that simple.

  9. What about chainloading PLoP from Grub, loading the ISO or floppy into memory, then chainloading back into Grub from PLoP?

    That's what I said. Except I tried that before without removing and reinserting the flash drive while loaded into PLoP and it didn't find a USB device to boot from, which I think is because it saw the flash drive as a HDD. I'll test it and post what happens.

  10. Anyone tried chainloading Grub4DOS/Grub2 from PLoP? Is it even possible? If so, can it be setup automatically to boot straight into Grub via PLoP?

    (My computer and school computers only support USB1.1 boot :()

    Are you wanting to boot PLoP from USB and then reboot the USB from PLoP with USB 2.0 support? I attempted this once without success and then got rid of it. I think the problem was that PLoP didn't recognize my flash drive since it was already plugged in and booted from, making PLoP think it's a HDD. If you loaded the ISO or floppy image into RAM using "map --mem", disconnect your flash drive, and reconnect it it may very well work. And yes, there is a way to customize it here, although I haven't tried any of it.

  11. I've discovered that you can name your menu whatever you'd like as well as place it in any directory you'd like. It helps reduce clutter and the amount of files on the root of your drive. I also keep my menu and all submenus in "/.multiboot/menus/" which helps keep everything neat and contained. To do this you must edit the "grldr" file's integrated menu which GRUB defaults to when it doesn't find "/menu.lst" You can even eliminate having a seperate menu altogether by putting it all in "grldr" if you'd like.

    Editing "grldr"

    Open "grldr" in a text editor (Notepad doesn't recognize the line terminators, making things difficult. Wordpad does though)

    Scroll to the bottom

    Find the lines:

    configfile
    default 0
    timeout 1
    
    title find /menu.lst, /boot/grub/menu.lst, /grub/menu.lst
        errorcheck off
        configfile /menu.lst
        configfile /boot/grub/menu.lst
        configfile /grub/menu.lst
        find --set-root --ignore-floppies --ignore-cd /menu.lst &amp;&amp; configfile /menu.lst
        find --set-root --ignore-floppies --ignore-cd /boot/grub/menu.lst &amp;&amp; configfile /boot/grub/menu.lst
        find --set-root --ignore-floppies --ignore-cd /grub/menu.lst &amp;&amp; configfile /grub/menu.lst
        errorcheck on
        commandline
    
    title commandline
        commandline
    
    title reboot
        reboot
    
    title halt
        halt

    This is the integrated menu, you can make it instantly load another menu by replacing everything above with something like:

    configfile /whateverfolder/yourmenu

    Or, you can replace everything from "default 0" to "halt" with your current menu, keeping the line "configfile" before your custom list because that's what tells GRUB where that what precedes is your list. Keep the NULL terminator as well which might appear as a box in most text editors (hex value: 00).

    I recommend using Notepad++ for all your text editing needs.

  12. Hi,

    I cannot get this to work. When I check this out in computer management, Mark as active is grayed out. I'm trying to get multipass to work on a SDHC card via a SDHC to USB adapter, but it won't work. I have also tried doing this in my Asus 1000HE's built in SDHC card reader, but that won't work either. Is there something I am missing?

    I have also tried to get this to work with Ubuntu 9.04 and grub2, but again it won't work.

    Try GParted and check the "active" option on the partition flags menu.

  13. I have a question, call me stupid for asking this - wouldn't a FAT/FAT32 device have the possibility of getting infected on a compromised/infect system, which would require the use of this device make it fairly insecure and a rather a bad idea for using it as FAT/FAT32?

    would a linux format like ext3 be more secure when it comes to infect systems and be a bit more secure overall?

    What does the file system have to do with security, dealing with viruses/malware/trojans/etc., unless it's encrypted? I guess you could say that a file system unsupported to said compromised system couldn't be (easily?) infected, but I don't think that's your reasoning behind why you think ext3 is somehow more secure than FAT32.

×
×
  • Create New...