Home Page
RABiD BUNNY FEVER
K.T.K

  • April 12, 2021, 08:39:47 PM *
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

Official site launch very soon, hurrah!


Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - R1

Pages: [1]
1
Posts / Re: My New Boot Loader
« on: May 22, 2013, 09:03:40 PM »
That's no problem at all, unfortunately I know the feeling.

I used the drivemapping as you described and it worked just like you said it would, but only using one of my USB sticks :-(.

When I tried it using my Datasur AES USB stick I had the problems that I described previously.

Anyway I have now found a slightly different solution using an Android app called Drivedroid which allows you to create bootable virtual USB sticks on your phone!
This in combination with Diskcryptor is working well for me.

If you feel like compiling your own kernel then you can use Drivedroid as a virtual CD drive to!

As an added layer of security I keep the USB images encrypted on the phone using an app called Cryptonite that implements EncFS, this in turn is cloud synced via Dropbox (and soon Ownsync)

All in all I feel pretty good about my security now, but that's not stopping me from feeling it necessary to set up QubesOS as a management station.

It seems that a tin foil hat wearing geeks work is never done  ;D

2
Posts / Re: My New Boot Loader
« on: March 01, 2013, 03:15:10 AM »
Hello again Jeffrey,

so.....I've been having problems  ;D

basically I have got this to work only on a USB stick where I have "flipped" the removable bit so that the USB stick reads as a USB HDD.
On a standard USB depending on which method I use I get one of two behaviours:
  • The truecrypt rescue disk boots and after typing in the password it says "Booting" but then nothing happens
  • The truecrypt rescue disk boots and after typing in the password it says "Incorrect password" !?!
Oddly enough when trying the other rescue disk options they do not affect anything, i.e. if I ask it to restore the original Win 7 bootloader it says that it's done it but it hasn't.

Any thoughts, I was going to give a blow by blow account of all the different ways I've tried this, screenshots and all but I thought I'd answer your questions as they come  :P


3
Posts / Re: My New Boot Loader
« on: February 11, 2013, 10:51:45 PM »
First let me thank you for your efforts!
Muchly appreciated  :)

Sorry been so late getting back to you by the way, I've been battling with DD-WRT on an old router........but that's another story!

I plan on using this method on all my systems (once it works!) and as one of them will be using UEFI the last part of your post is perfect.
Saying that I may just use Qubes on the UEFI capable laptop as it's the only one of my systems with Vt-d & TPM and Qubes has some sort of "Anti evil maid" system.

Wish I got into Linux earlier as my life would be much easier now I'm all security conscious  :-[

Anyway I'm going to try those map commands and I'll let you know how I get on.

Thanks again

4
Posts / Re: My New Boot Loader
« on: February 02, 2013, 12:01:57 AM »
Hi Jeffrey,

I came across your article on how you moved your boot  loader to a USB whilst trying to find out why I'm having problems doing  the same  :-[

I am running Windows 7 x64 from a 40GB SSD with a 4x 500GB in a Raid-0 array which I use for storage.
I have fully encrypted both my logical drives using Truecrypt, the RAID drive is mounted when the PC starts as a "System favorite"
I then create rescue disk iso that I add to my bootable USB Dongle using a program called XBoot  which uses Grub4DOS.
I can access the Truecrypt Rescue disk via the USB Dongle.
All good so far, everything works!  :D

Unfortunately when I try to enter the password for my Truecrypt encrypted system it tells me that there are no bootable partitions then (confusingly) says "Booting" but nothing happens  ???

You indicated that you had a problem and was hoping that this is the problem that you overcame using some magical Grub4DOS fu!

Hope you can help

Pages: [1]