Many people used to use backtrack5 with different operating system like windows 7, so you can also make dual boot setup to run both operating system and other way is to create a persistent USB to make your backtrack5 live boot at every time and for every where usage.
Sign in. Log into your account. Password recovery. Can random characters in your code get you in trouble? They certainly can! Today, we are going to discuss CRLF injections and improper neutralization Sana Qazi - October 28, 0. Every company has a variety of scanners for analyzing its network and identifying new or unknown open ports. It's unthinkable to disguise the potentially Nowadays just as one cannot take enough safety measures when leaving their house of work to avoid running into problems and tribulations along the Sana Qazi - May 17, 0.
For different available loopholes, the majority of hackers all around the world are focused on attacking Windows users and servers. This article demonstrates the Passwords are always our first and, in cases, sole line of protection from attackers. If an intruder does not possess direct accessibility to a Kali Linux. Sana Qazi - August 5, 0. Forgot the Kali Linux root password? Stress not! This tutorial discusses the steps to reset Kali Linux system password. Follow the steps, and you This article is the part of Android Hacking tutorial; it covers step by step guide to exploit Android ADB to get the persistent connection This article demonstrates an in-depth guide on how to hack Windows 10 Passwords using FakeLogonScreen.
Hacking Windows 10 password is an exciting topic and Your Android phone can turn into a hacking device with just a few steps, having the ability to run tools like Nmap, Nikto, Netcat, In this article, we are going to learn how to hack an Android phone using Metasploit framework.
Android devices are growing very fast worldwide If you are tired of the old smartphone, but it can still open Facebook, Instagram, 22Bet, or other platforms, don't try to buy a Setting the partition type for the first partition to ext3 Command m for help : t. If you happen to get an error that mentions something like ".. You might be able to get away with continuing, but there is a good chance you will experience some problems. After rebooting, you will need to re-execute the startx command and the cryptsetup luksOpen commands.
If you happen to get an error with mentions something like ".. At least, this worked in my case. It is now time to get a couple additional packages installed that we need for LVM and encryption. First we need to update the local repositories and then install lvm2 and hashalot. Output has been ommitted. For Backtrack 5 R1 type the following. For Backtrack 5 R2 we only need hashalot.
Type the following. Our next step is to enable encryption on the logical partition we created above and make it available for use. Before we do that though, there is an optional step we can take if we want to make sure no one can tell where our data is on the drive.
It isn't really necessary since anything written will be encrypted, but if we want to be thorough and make sure no one can see where our data even sits on the drive, we can fill the logical partition with random data before enabling encryption on it. This will take some time, as much as a couple hours or more.
Execute the following command:. The following commands will setup encryption services for the partition and open it for use. There are several ciphers that can be used, but the one indicated in the command is supposed to be the most secure and quickest for Ubuntu 8.
Please note that the case of the command luksFormat is required. Are you sure? Type uppercase yes : YES. Enter LUKS passphrase: enter passphrase [type passphrase].
Verify passphrase: repeat passphrase [type passphase]. If you should happen to get a "cannot access device" error when trying to perform the cryptsetup setup commands above, make sure the USB drive has not been mounted.
That can happen sometimes. Now that that's all done, we can create our root and swap partitions using LVM. Again, the commands below will do so.
Play around with it a little and you may be able to make it a bit larger or you may have to make it a bit smaller. The final step is to format the logical volumes we just created. I have not included the output below for brevity's sake. If you want to try and eek out every last bit of performance and help your flash drive last longer, you can alternatively use the following command to disable journaling on the root partition. I have not tested this yet, but it should work just fine.
Remember that this will open you to a greater possibility of unrecoverable drive corruption. Notice that the first letter o is small case and the second is a capitol letter O. Believe it or not, we are finally ready to start installing Backtrack. To do, double-click on the install. This will start the graphical installer. Select you language of choice and click the 'Forward' button. The next step is to select our keyboard layout.
Pick yours and click the 'Forward' button. I can not vouch for any keyboard layout other than English. We are not going to indicate the mount points for our partitions. First let's setup our root partition. Click on the row with vg-root in it and click the 'Change' button. The system will re-read the partition table and redisplay it.
Now for the boot partition. Again, select ext4 and click the format checkbox. The disk partition will be re-read and the display updated. You will get this message if you are installing to a USB drive and not using a swap partition. Click the 'Continue' button. Don't forget! Make sure you select the target disk for your install as the device for the boot loader to be installed on or you run the risk of making the system you are doing this on non-bootable.
Then click on the 'OK' button. Click on the 'Continue Testing' button. We have now installed the main distribution to our thumb drive. The next step is to configure the newly installed system to use LVM and open the encrypted partition. However, before we do that we need to figure out the UUID of our encrypted volume. We want to do this so that we don't run into problems if the device name of the drive changes from machine to machine. This has changed with Backtrack 5.
We now use blkid. So execute blkid as below. We will need it later. Note: your output will be different than mine. Now time to configure our newly installed system. The first thing we have to do is make the newly installed system active so we can make changes to it.
We do that by mounting the partitions and chrooting to it. The magic to making all this work is to rebuild the initrd image that is used to boot our system. We need to include some things, load some modules, and tell it to open the encrypted volume, but first we have to go through the whole process of installing software again.
We have to do this because we are essentially right back where we started when we booted the live cd. Do the following again. The next step is to configure how initramfs-tools will create our initrd file. If my change it isn't correct in your installation, follow the directions below to correct it. I use the vi editor, but you can use your favorite editor. We need to add the following line to the file. If you are new to vi, hit the o key and the type the following:.
When you are done typing that line, hit the esc key and then type ':wq' without the quotes to save and exit vi. The file should look like this. The uuid is unique to my case. Make sure yours matches your system.
Again, use your favorite editor or vi. We need to delete the first line that starts with UUID right after the line which contains 'vg-root.
We also need to remove the comment symbol from the start of the line with 'vg-root' in it. That line is just bolded above. For those new to vi, position the cursor on first 'U' of the line using your arrow keys and type 'dd', then move the cursor to the ' ' in the line above and type the letter o, then type the line below, hit the esc key and type ':wq' without the quotes to save the file.
The line needs to look like below when done:. Once that is done, there is one final thing we need to do before we can rebuild the initrd image and reboot. There is a bug in the cryptroot script that produces an odd situation.
When we boot our USB drive, it will appear to be stuck on the splash screen. What is actually happening is that the system is waiting on us to enter our luks password. We have two choices for doing so. The first is to just type it in when we see the splash screen. This works as long as we have waited long enough for the system to be ready for us. However, it's kind of hard to tell what's going on. The second option is to press the F8 key which takes us to the console.
There we will see the system waiting for us to enter our passphrase and this is where this odd bug shows up. Initially, it will look like 4 characters have already been entered. They haven't been, but that's what it looks like.
Then, every type we press a key, it will reprint the line asking us to enter our passphrase. We can fix that. Greg M and James had a conversation in the comments about this topic and found the resources needed to fix it. James was kind enough to send me the changes that need to be made. As mentioned, the problem is with the cryptroot script. This script is the script that requests our passphrase and mounts the encrypted volume.
Kind of important stuff. Greg and James used a patch file found in this post in the Backtrack Linux forums. Below I have included the actual changes to be made. Alternatively, you can use a patch file. The commands to perform the patch are as follows.
BTW - that's a zero in the patch command. Warning: You can make your system unbootable if the cryptroot script gets corrupted.
Go to line You should see the following:. That's it. Save the file and we are ready to rebuild initrd. To do that, execute the following command. Now, if having to press the F8 key at boot bugs you, you can change the boot sequence to go directly to the console. The line will end up looking like this:. Do not run aptitude safe-upgrade! It will remove some vital tools. Run apt-get upgrade instead which appears to leave things installed that need to be installed.
If you should happen to run aptitude safe-upgrade, ignore the warning about removing packages, type 'Y' and let it do its thing, you will need to run the following command before you reboot or your install will be broken. If you have problems, you can use the troubleshooting directions below to get back to the state where you can try to figure out how what went wrong.
Once you have a booting system, you are ready to login. The default userid is root and the default password is toor. You are now ready to login and being playing. Don't forget to change the root password as soon as you login the first time. You can make some final tweaks if you want like starting GNOME at boot, but for all intents and purposes you have successfully installed Backtrack 5 to a USB drive and don't have to worry about sensitive information being intercepted if it gets lost of stolen.
Richard, in comment , mentioned backing up his completed install periodically just in case something goes wrong with his USB drive. Note: You will use the device identifier of the DRIVE , not a partition, unless you want to dd each partition separately.
That seems a bit silly though. Do not boot to the USB drive for this. Execute the following to create a binary copy of your drive. You will need to have free space available on the target drive equivalent to the size of the USB drive. You can compres the image after the dd is complete using gzip or bzip2.
On a Windows machine, you will need to use a utility that will create a binary copy of the USB device. There are several products out there that will do this. This is freeware tool which creates an exact duplicate image of a USB drive. It does require. There are many other options.
If you run into any problems, you don't have to start over. As long as your encrypted volume is built correctly and you have the correct LUKS passphrase, you can get back to the place you were with the Live CD. You can now do any trouble shooting you need to do and try to reboot again. One note, if you want to check the UUID of your partition, do it before you chroot. Very interesting. I will have to play with this. I have done upgrades before on my Backtrack installations, but not using the safe-upgrade option.
I will put a note in the how-to to be careful with apt-get safe-upgrade. You can also avoid this problem by using apt-get upgrade instead of aptitude safe-upgrade. I have updated the how-to with a warning about this issue. It will remove encryptfs-utils and cryptsetup also. Thanks for an updated version of the guide! Following line:. Hello, this new tutorial for BT5 is simply excellent! Any tips for getting this live USB to work on a macbook?
That is the easiest way you can do. I just finished installing BT5 on a 64G USB stick for my normal Macbook one of the first unibody models and his is what i did, as far as memory serves. Way too much overkill for a partition that will only hold a few files and on a medium where resources are low. You can now boot the DVD and follow this guide normally. And for the partition steps in the guide, should we change partition number? Great guide! I had some trouble partitioning it from the command line on my first attempt so I opted for GParted.
I used the troubleshooting section and determined that the problem was I mounted sdb5 as the boot when it should have been sdb2. After that all works! Only other question… how do you change the backtrack splash that shows after the grub but before pressing F8 to enter passphrase? What I have done wrong? Can I repair that or do I have to make all new? Great stuff. True, but there are some issues with Backtrack 5 and persistence.
The Backtrack 4 how-to method does not yet work. Could you perhaps make a video of this tutorial? It would help me greatly. Also, when you want us to reboot after the mounting and chrooting stage, do you want us to reboot from the live CD or from the usb flash drive we just made?
Yes the USB you just made it because you were troubleshooting for any trouble you get it. Now you trying to to see if you are successful.
Good luck. I plan to make a video, but it will be a bit. Have to carve out the time to do it. BY the time I tell you to reboot, you are done. You will be booting from the new USB drive. I am new to installing backtrack at all and followed the guide all the way to the end and then I get an error when I boot up from the USB drive:.
Dropping to shell! Just cosmetic if one is coying and pasting. Could that be the problem? This may be worth noting in the walkthrough itself for the following reasons. When I removed the spaces, I no longer received the warning when I updated the initrd image, and I also was able to boot to my persistent drive afterward.
It exist my friend. I tried and it works for me. I do not know what you have done but try to use the guidelines step by step. Are you sure you did not jump anything? Let me know. Thank you. Same here I have that problem and still did not find solutions.
I just need help with the last part of the file editing and then I will be fine. As I stated above the error I am getting is:. Sorry I did not understand the process for this. Could you please help me sorted it of this. Thanks again for the article! Do you know why this is? If you do the partitioning in text mode without startx then you can get past the errors after you reboot.
I followed the fdisk part partitioning of the tutorial. I skipped next crypto parts and went directly to installation. Installation went as in the tutorial. In my case, all was already there. The only thing I did here is to comment out one line that was referring to swap partition, although I am not sure whether that was necessary at all.
When I left it untouched it worked. The rest is like in tutorial. First time, startx refuses to work, same as with DVD. To resolve this, as mentioned somewhere else, the following has to be done only first time :.
Now there is an issue. While the USB boots and works perfectly on the same computer where it has been produced, it seems that it has problems when booted on different hardware. On my netbook for example it fails to detect wireless adapter. When I boot the same netbook from DVD, the adapter gets detected correctly. I hope that this can be resolved.
The problem is different — somehow during boot, my wireless card gets renamed from wlan0 to wlan1. Later, during KDE session, wicd looks for wlan0 and can not find it. When directed to wlan1, wicd scans the networks correctly and everything works fine. Begin: Loading essential drivers… … Done. Dropping to a shell! BusyBox V1. Are you probably using an USB 3. This was the problem on my side…. After plugging the stick to a USB 2.
This was the issue for me. Now update your image again via update-initramfs -u and reboot. You should now get a luks passphrase prompt!
I get the password prompt, but after I enter the password I get a long series of errors, and BT refuses to boot. Hi all, i have some trouble, i cant create a extended partition. Above it says to add a swap for a hard dive install. Help is much appreciated! Try Easus Partition free; choose delete, Apply. Do a basic format with FAT Looks great! Hi, great guide, was wondering about the part wheere you have to press f8 to get into the console to input the luks passphrase, is there a way to fix that so the prompt for luks passphrase pops up itself without pressing f8?
Gave this a shot, ran into problems with video on an Acer AO It boots up. I select the default mode, or text mode. I let it run through the initial setup and then it freezes with garbled graphics on the monitor.
Same thing if I boot in safe mode. Will post if I can make it work with the simple stuff first. Maybe it has something to do with that. Fixing for USB stick: 1. Format a new partition with FAT Can perhaps be skipped 2. I wanted to ask thought, will following this guide also make my usb persistent with changes?
Everything seemed normal until the manual partition settings in the BT5 installer. And then finally at the end, I rebooted, and it was not even listed as a bootable medium. Is there anything in the steps I need to change to allow access to an extra FAT32 partition?
See what I did there?! Install went without a hitch. One thing I failed to do in my eagerness was check my fstab file. A few comments and a question. Apologize for the length, but any feedback appreciated!! When booting, after pressing F8 to remove the wallpaper screen to reveal the passphrase screen, I get: my actual luks crypt partition UUID is omitted for less clutter, the real output shows my actial ID.
Every press of a key to enter my password also repeats the line until I press enter. Afterwards, my luks partition is unlocked and the system does boot OK. While my system does work, I really would like to clean up the password entry.
Booting after a delay fails to an initramfs shell, maybe I will try and mod the script itself. Has anyone else had the multiple lines described here on password entry?
Has anyone gotten the initramfs scripts method for generating a new initramfs to work on BT5? For windows this is the most easiest way to make a backtrack 5 r2 bootable usb. I also have the same problem you described. I tried the patch and it works great. However the passphrase line still has four characters already in there when you come to type in the password. Yes I was going to mention that, I get the four characters pre-filled in also after applying the patch.
Would be nice to fix that, I am going to see if I can get someone interested in helping to mod the script, if you have any luck please post back here, OK?
I certainly will. James, a thought. I think the script is OK. The reason for the four characters is, I am suggesting, the results of the keyboard mapping for the F8 key you have to press to reveal the password entry which is hidden by the splash. So this would indicate the BackTrack 5 splash has something to do with it. The fact you have to press the F8 key to get to the enter passphrase line would certainly explain the rogue four characters.
In my experience you can simply type your passphrase at the blank GUI screen the red BT5 wallpaper before you press F8 and press return. I have the volume set up. When accessing the encrypted volume manually e. Why is 16GB flash drive the minimum for this tutorial? And why is an 8GB drive not enough room. Is it because of the encryption? If so, how could i install this without encryption. You can use ann 8GB drive, but you will only have a couple hunder MB of space left after the install.
The reason for grub error 15 is very simple and so is the solution. Hi Kevin, thanks for all of the hard work you put into that howto. Everything went perfectly, except for one small thing. There are grub. Anyway, can you help? Any changes here should be reflected in the boot menu. If I have a chance to test in the near future and figure something out, I will let you know. I have a similar issue with the loading of BT5 and entering the password. I think I seen a Gentoo setup with full disk encryption, and the spash image had a field for you to enter in your passphrase.
Ill have to search to build this into my BT5 install. This is a great howto, thanks for putting it together. Even command line has a noticeable delay. Is this just do to the encryption running off a thumbdrive? Same thing here. Unfortunately I ran apt-get autoremove after a few days of use and now my system is unbootable in the same way as running aptitude safe-upgrade I imagine.
Still no change. Hi, I am really enjoying this guide so far, it is really good. Thanks for making it. I have a question though. It will start accessing the repositories for hashalot and lvm2 and whatnot, but then it says:. Selecting previously deselected package hashalot. Set of commands.
Got it. I just created a new VM instance of backtrack and was able to install everything fine. Wish I would have held off on posting that long thing until I had tried a little harder. Oh well, maybe it will help someone else with the same problem. Once I did that I was able to edit the real grub. I am experiencing this problem too when moving from computer to computer Laptop to Netbook.
I have also stripped this down to just install on the flash drive with no encryption because its a little to time consuming. Ill do the encryption later once i figure this part out. Here is what I noticed. There is another install method I am looking into called usb persistent taking the Live Iso files and copying them over..
I just want it to load to the USBgrub and load. Ok well I was Mislead and my issue looks like the 64bit gnome OS is not compatible with the 64bit i Atom cpu.. I am having trouble with this instruction set. I will admit I am new to BT and only slightly familiar with Linux. I even get this when I reboot and go through the troubleshooting steps. Did I miss something or is there a step missing? This is the second time I have gone through the guide and keep getting caught in the same spot.
BT set the default for me for a completely different one that I expected not US and not the one I choose in the installer but a subtype of it…. This tutorial on Partial disk encryption of BT5 is a real help for h4x0rs!!! I also created the extended and the Luks partition.
Thanks for the info! Put an update at the top of the how-to and am adding that step right now. Will also test the rest as soon as my download finishes. Not sure what you did, but it is unnecessary to reinstall those packages in my testing. If you did any sort of apt-get activity with autoremove, that might explain what happened.
After following the guide and rebooting and selecting my sd card, I get: error: cannot read the Linux header error: you need to load the kernel first. Just one question: I have installed and regularly use truecrypt on my backtrack 5 usb. The problem is that everytime i shutdown, when i reboot into backtrack, truecrypt seems to be uninstalled and i need to install it again every time.
Am i doing something wrong? I of course added a Linux swap partition on my harddisk. Question is: is the swap partition now encrypted as well? My guess is not. How would I go about encrypting it as well? I thought there was something wrong with the drive, but formatting it back to fat32 and copying files under windows was fine and at the rated speed. Which is a shame because I bought the drive specifically for BT and I expected instant response — since running it on an 8GB Maxell previously was blisteringly fast!
I have tried the chmod command but does not seem to work. Please help. Thank you very much. Only then would the text remain green and acceptable resulting in a booting system. You cannot alter the spaces in between or anything and vi is very good at letting you know correct configuration with displayed text colors. If any mount options turned white it indicated problem. Good thing I made a backup of fstab before editing, eh? Thanks for the write up…. I love this setup.
First time, I thought that install had failed, because the screen remained black, so I re-install all the stuff. Mine have no LED…. At splash screen, I hit instead of in order to get to first screen. When I type my password, it gives a newline at each character?? Hope this helps. Have a look here :. Message re-send because some character dissapeared… ESC and F8 were written between brackets… Sorry… Erase the sentences before Hello, please.
Hi everyone. I need your help. Just wanted to drop a line or two to say thank you! I got it to work first time through on a 16GB Super Talent drive.
I am not experiencing the lag times that others have mentioned; quick access times all around. Thanks again! Every attempt says that the device is busy or already mounted to cdrom. I am new to linux, and I got that same error last night. I have searched all over the web trying to resolve it with no luck. It sounds like you figured it out. Can you help me shed some light on the problem? Suggest me as soon as possible. What you want to do is called dual booting.
Hello, I have a little problem. Everything worked like a charm for me until right after I entered the password for luks.
Any ideas? Have you tried the troubleshooting steps to make sure everything works manually? It happens some times. This tute is exactly what I have been looking for for a few days. Thanks a lot, Kevin! Great work! Well, I must say the procedure is exquisitely detailed, with images of every step.
This is what happened: a I tried to do it on a computer that already had Ubuntu on its hard drive. Guess what? It wants a swap partition and is not taking a no for an answer! I got as far as installing system and copying the files.
Have you verified that your volume group was created? Yeah maybe.. I set the options as directed and it works great. My problem is that this computer has no internet connection and I am trying to install these 2 programs from a USB drive. If you have the packages downloaded to a USB drive all you need to do is copy them to the newly installed USB drive before you chroot. After theses steps:.
They should be available to you from within the chrooted environment then. I am not sure how that would help. I think the problem is that I cannot copy from a separate attached USB flash drive to the inside of the newly encrypted install. Is there really no way to copy or install those files without having to connect to the internet and download them? I am sure this is a simple thing to do but searching Google relating to a question like this is very difficult, I get a lot of unrelated answers.
I just need to do this bit after getting to the stage I mentioned above. Everything else seems to work. But from a file stored on a flash drive and not connecting to the internet. I am sorry but this is proving very difficult for me.
It helps us prolong the life of our device. Obviously not your fault. Any hints or suggestions? Also do you have any experience using this guide with the Ubuntu install disk? Was their a reason you picked the BT flavor?
This was all about having a Backtrack install on a USB drive for penetration testing, not about having an encrypted Linux distro for general use. As far as working with a regular ubuntu install, that is where some of the original steps came from. If you look at the beginning of the tutorial, there are a couple of references that you can potentially draw on.
On the blank screen thing, I have had that happen when it is waiting for me to type my Luks phrase, but that is the only time. Have you tried pressing the F8 key to get to the console screen to see what errors might be displayed? Seems like there is some issue with the boot loader starting the process. Thank you so much, I was working into the night with this and it is starting to get me down. I am going to try your suggestion now!! Thanks very much. Is there any way I can start from the position I mentioned above without having to re-do everything?
A small suggestion for your tutorial, can you mention at the start that some users need to change which keyboard layout they use as this will affect their password later.
Can I ask a general question? I use truecrypt in windows and I understand it very well. You should be able to boot the DVD, install hashalot and lvm, and then open the encrypted volume and go from there. This would be very similar to the troubleshooting guidance at the end of the how-to.
I am trying to use my USB install from where I left off. I am getting to this bit. First the obvious question, did you install the lvm package before doing the cryptsetup command? If so, it is likely that the volume group did not get activated.
I think there is a comment above that this happens sometimes and directions on how to activate it. I have no idea what is wrong. I have followed this tutorial many, many times and been exceptionally careful at all stages. I always remember to use my actual path sda and not the one in the tutorial. I have started a fresh since my last post, again…totally wiped my USB drive and still it does not work for me. I am getting quite frustrated with it. I have managed to copy my hashalot and lvm folders to a temp directory in my mounted container.
I have even so I thought managed to install them there by chroot. I need to see that it is there and installed correctly as booting back up, installing hashalot, lvm, changing keyboard region, mounting the volume etc, etc just to start again takes so long. I should perhaps point out that I need to use this…vgchange -ay vg…. Every time I need to get back in to fix it. Could this be an indication of another problem and should this be run when booting in my install?
I desperately would like this to work and I will stick with it but I must admit it is starting to get to me. Any help would be very much appreciated. However I was able to see it bolded in word.
It turns out you mean this line. There is no example shown of the full page when finished. I presume it should look exactly like…. This whole thing is still not working for me and I have tried a few more times since I last posted. I have never failed at something like this before and I cannot understand what is going wrong for me. I can follow your logic and everything seems to go ok its just when I reboot it always fails. My last error message when trying to boot was ….
Per the first line of the how-to, this method has been verified with R1. I will offer that I have never tried to do it without an Internet connection to the box I was working on.
Generally, if the command execute successfully, then everything is going well. Hi thanks for your reply. Obviously UUID numbers will be different. I have never installed hashalot and lvm from source for this project. I strongly suggest downloading the ubuntu packages and using the built-in package management tools to install them. That very well may be the problem. Again, there may be dependencies that need to be met in order to install these packages and that may be why things are failing.
Those errors were due to clumsy posting and not what I was actually typing in, sorry about that rather embarrassing. I will struggle on trying to get this to work for me. If you get bored and get chance to try this without internet connection then I would be very interested in hearing how you got on.
First off, very impressive how-to. I clumsily attempted to encrypt the swap partition I allocated by duplicating the same steps as for the root partition e. I have a pvcrypt-root and a pvcrypt-swap, a vg-root and a vg-swap, etc. So, problem solved. In case anyone else is like me unfamiliar with using LVM, the correct solution is to do the following:.
Hi there, the only typo I found was when you are going to indicate the mount points, you said: We are not going to indicate the mount points for our partitions.
Could you tell me what steps I need to follow without encryption? Be careful to install it to correct partition though. Is there a bug with cryptsetup or something? I did this several months ago with BackTrack 5 and it worked a treat. I checked the crypttab file and everything is fine, no leading white spaces etc, fstab is also correct. Additional note. Looks like crypttab is buggy in BT5 RC1. I just tried it all over again this time using a BT5 image from release date and its working fine.
I did everything exactly the same when attempting to use BT5 RC1 and yet it failed here. Have you tried it with R1 instead of RC1? I have tested it with the official R1 release and it worked fine at the time.
Sorry I meant R1. However its nothing major. Has there been any progress concerning making this a persistent install? This method above results in a installation of Backtrack that retains changes between boots and is encrypted. After reading through all of your comments, I was under the impression that this was not a persistent install. Thank you for the clarification. Also its a usb stick, its static.
Maybe on a hard drive you give the boot partition M for grub changes or whatever but on a usb stick i dont really see the need…. Updates, specifically kernel updates can and do happen. That being said, at one time creating a MB boot partition did not allow the install to finish.
I made it to avoid that issue. At same time save changes persistence? Dear friends, I feel so stupid trying to find that boot partition of my USB stick for a dozen of times….. I successfully get to the point where we launch a GUI of the installer, choose language etc.
Where do I find that M boot partition??? Thank you very much beforehand!!! Hope it helps. So I had this working perfectly for months using the first method. I have updated the kernel etc with apt-get and all worked fine. I get the following and then it drops in to a useless ramfs shell. I told a friend to use your guide as I did when I made my boot-able copy on my 16g flash.
I sent everyone that asks me how I made my Flash run to your guide Most unfamiliar with Linux or Backtrack. Just a thought for helping out first timers and such. All in all, Great Job on the revisions and making this guide as simply and fast as possible.
Thank you for the wonderful tutorial. But I have a problem.. I have an 8GB usb memory. In my first attempt I did cancel the process during install. When I tried re-installing I had 7. I can not seem to get my MB partition back..
Besides the problem is the inconsistency causes failures in the backtrack and on windows..
0コメント