Re: Bad Agent on encrypted disk

[Michael Salmon <lonestarr13 () gmail com>]

My previous company used PGP whole disk encryption, when all else failed we
needed to use a boot disk to decrypt the drive before we could proceed.  I
don't know much about SafeDisk and I'm not sure if you or your IT dept saw
this already but I think it may be your best solution:
http://ubcd4win.com/forum/index.php?showtopic=11191.  Create a BartPE disk
to mount and decrypt the drive.  Maybe you could use PXE boot with this
solution to speed up the process?

Maybe someone else here has more experience with SafeBoot and a better
solution.  Good luck!

On Oct 5, 2010 9:13 PM, "Grymoire" <pauldotcom () grymoire com> wrote:


We have a problem. We use a full disk encryption product that is
installed in the BIOS. The systems are Windows XP. The product is
SafeBoot 4.2.

Our IT department deployed a new agent on all laptops too aggressively,
This is what happens
               The system boots up
               The user gives the BIOS username and password
               The Login console shows
               2 seconds passes
               A Blue Screen appears.

I'm trying to think of a way to intercept the login process,
and delete the bad file/program, so we can fis the systems.

Some systems use SafeBook 4.3, and we have a solution for that.
But SafeBoot 4.2 doesn't even have a "Safe Mode" to boot up.

Any ideas? Our IT department has not come up with a solution, and we
have a lot of unhappy users with unrecoverable disks.
_______________________________________________
Pauldotcom mailing list
Pauldotcom () mail pauldotcom com
http://mail.pauldotcom.com/cgi-bin/mailman/listinfo/pauldotcom
Main Web Site: http://pauldotcom.com

_______________________________________________
Pauldotcom mailing list
Pauldotcom () mail pauldotcom com
http://mail.pauldotcom.com/cgi-bin/mailman/listinfo/pauldotcom
Main Web Site: http://pauldotcom.com