BT4-PreFinal Manual Install -Dual Boot

[Archangel-Amael]

I understand the purpose for using ubuntu/debian as the base
I was just trying to understand the purpose behind not having a root user,
which you would get by using the install.sh
The only thing I can imagine is for those who would be using it as a normal
machine instead of a security/pentest platform
I was basically asking "what am I missing from the picture", when I asked "am I wrong with this thinking"

Maybe I am not understanding your post correctly. But there is a root user.
Furthermore the purpose of root in BT is that most of the tools require root privileges in order to run/function properly.
In addition to that anyone that is using the distro as intended knows about this and knows the risks that may be involved.

[zade7]

Maybe I am not understanding your post correctly. But there is a root user.
Furthermore the purpose of root in BT is that most of the tools require root privileges in order to run/function properly.
In addition to that anyone that is using the distro as intended knows about this and knows the risks that may be involved.

^^^that is exactly what I am saying

and it is for this reason I am saying
if you plan on actually using BT4 for its intended purpose, and need to have it installed to your HD then this method of manual installation is "the best way to do it"

what I was wondering is: simply put "why would the install.sh even be included" because it is so restrictive

*** I am sorry for bloating this thread with a question not really even related to the topic. I was merely trying to comment, and agree with adri_ht
on the fact that the GUI install makes little sense to use

~Z~

[Snayler]

One thing i noticed is missing on the tutorial:

mkdir /media (or add it to the existing mkdir command like "mkdir /mnt/bt4/{dev,mnt,tmp,proc,sys,media}")
chmod 1777 /media/

This will prevent the "cannot obtain lock on /media/.hal-mtab" error when mounting cdroms and usb devices.

Anyway, good tutorial! Thanks for sharing.

[imported_hatake_kakashi]

I am not a dev, neither does my thoughts and opinions does reflect backtrack devs.

I do believe the installer was included due to extranneous amounts of request after BT3 which didn't include one by default. That plus the fact that many users seem to prefer using flashy GUI tools rather than working with the bare CLI.

This was the reason why ubuntu's base (or kubuntu should I say rather) was chosen. kubuntu is relatively popular amongst newcomers and their package management system is somewhat flawless (of course relying on debian). However kubuntu, like ubuntu has a strict security standard. Users must learn to not run or do everything as admin/root because it can easily lead to the compromise of their systems. Like how Microsoft had when their OS were plagued and Vista came in with something called UAC that mimicked what ubuntu have had but in a more severe state.

As a result, this sort of practise was passed through Backtrack . I am presuming the reason why the devs have not removed such strict practise was to purely tame users. Sure it maybe a nuisance to a seasoned security professional, though I'm sure enabling root access permanantly is not going to force you lose a limb and a leg over it. Instead the majority of the backtrack users seems to be rather new and am totally unfamiliar with linux, most likely because of all the hype that their mates were running it, etc.

I tend to treat the restrictive practises as ways to teach one how to ride a bicycle. Nobody can ride a bike on two wheels on their first go without falling. The use of sudo is no different that it makes the newcomer ride the bikes with training wheels.

Last but not least, if a pentesting distro that allows users to install it does not have training wheels imagine what the forum would be like. Users plagued with worms because they never realised the whole point of preventing root access? users complain or get angry because of some guidance or help they received which involved wiping their backtrack installation, if not their entire computer setup?

Just my 0.02 cents.

(edit) Moderators: Please feel free to move the last few posts on this thread with regards to the questioning of the installer and/or restrictive practices. I believe this topic is questioning what is right or wrong and not about how manual install should be.

[Cerox Rex]

I have sucsesfully ben able to install BT4 to to dualboot with my Ubuntu system and it seems to be loading properly.

That is untill it starts waiting for the root filesystem!

Here it just gives up after aprox 10 sec and drops me to a <ramfs> shell promt.

My guess is that i'v done somthing wrong in my gruvb.conf file but i am unable to figure this one out by myself.

Grub.conf:

### BEGIN /etc/grub.d/00_header ###
if [ -s /boot/grub/grubenv ]; then
have_grubenv=true
load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
saved_entry=${prev_saved_entry}
save_env saved_entry
prev_saved_entry=
save_env prev_saved_entry
fi
insmod ext2
set root=(hd0,5)
search --no-floppy --fs-uuid --set 93e3262d-a26b-41bf-8ac3-a4c11cf1c079
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
if [ ${recordfail} = 1 ]; then
set timeout=-1
else
set timeout=3
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/white
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry "Ubuntu, Linux 2.6.31-16-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod reiserfs
set root=(hd0,1)
search --no-floppy --fs-uuid --set 5b54f715-ac6a-442a-8962-3ded89930c3a
linux /vmlinuz-2.6.31-16-generic root=UUID=93e3262d-a26b-41bf-8ac3-a4c11cf1c079 ro quiet splash
initrd /initrd.img-2.6.31-16-generic
}
menuentry "Ubuntu, Linux 2.6.31-16-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod reiserfs
set root=(hd0,1)
search --no-floppy --fs-uuid --set 5b54f715-ac6a-442a-8962-3ded89930c3a
linux /vmlinuz-2.6.31-16-generic root=UUID=93e3262d-a26b-41bf-8ac3-a4c11cf1c079 ro single
initrd /initrd.img-2.6.31-16-generic
}
menuentry "Bactrack 4" {
irecordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd0,8)
linux /boot/vmlinuz-2.6.29.4
initrd /boot/initrd.img-2.6.29.4
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
linux16 /memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
linux16 /memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Memory Test (on /dev/sda8)" {
insmod ext2
set root=(hd0,8)
search --no-floppy --fs-uuid --set 70ad89ef-06c6-4aaf-b57c-e9510e02fbe1
linux /boot/memtest86+.bin
}
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

Dont kill me for posting all of the grub-conf file

And do forgive my poor English.

[shwerm601]

I have sucsesfully ben able to install BT4 to to dualboot with my Ubuntu system and it seems to be loading properly.

That is untill it starts waiting for the root filesystem!

Here it just gives up after aprox 10 sec and drops me to a <ramfs> shell promt.

My guess is that i'v done somthing wrong in my gruvb.conf file but i am unable to figure this one out by myself.

Grub.conf:


Dont kill me for posting all of the grub-conf file

And do forgive my poor English.

Was this for a dual boot with ubuntu 9.10 because if so 9.10 ships with grub 2 by defualt. This differs from grub legacy in that there is no menu.lst to define OS boot options. What you will want to be doing is boot into ubuntu and create a new config script to update grub with.

Check this out it should set you in the right direction:
hXXp://XXX.dedoimedo.com/computers/grub-2.html

Remember though, if for example /dev/sda1 was hd0,0 in grub legacy that now /dev/sda1 is hd0,1 in grub 2.

Good luck!

[frezasaga]

this guide is easy to follow................already installed in VMWARE using the guide that the first poster make...........