Discussion:
FreeOTFE and 64 bit W7 driver signing problem
(too old to reply)
Todd
2014-05-06 18:59:20 UTC
Permalink
Hi All,

http://sourceforge.net/projects/freeotfe.mirror/

W7 64 bit does not allow you to run unsigned drivers,
except in "Test Mode". This is a problem for Free OTFE
as the drivers are (who knows why) unsigned.

And, the users don't like "Test Mode" showing on the
bottom right of their screen. Turn off the "test mode"
and Free OTFE stops working.

Has anyone come up with a work around?

A way of reading LUKS encrypted flash drives that
has signed drivers?

A way to allow just these unsigned drivers to operate?

Many thanks,
-T
VanguardLH
2014-05-07 00:24:49 UTC
Permalink
Post by Todd
http://sourceforge.net/projects/freeotfe.mirror/
W7 64 bit does not allow you to run unsigned drivers,
except in "Test Mode". This is a problem for Free OTFE
as the drivers are (who knows why) unsigned.
Use free TrueCrypt instead. No drivers required. Has versions for
Windows, Mac OSX, and Linux. Portable version, too.

http://www.truecrypt.org/

Some folks like fewer options (i.e., simpler tool) and prefer the free
BestCrypt Traveller. Also, no drivers required. This is a portable app
but obviously you can run it as a normal app.

http://www.jetico.com/products/free-security-tools/bestcrypt-traveller

I don't know that TrueCrypt will read LUX-encrypted containers. They
typically only read the containers that they generated. You'll probably
have to use test mode in FreeOTFE to mount its container, mount a
container in TrueCrypt and then copy from FreeOTFE to TrueCrypt.
Todd
2014-05-07 01:49:30 UTC
Permalink
Post by VanguardLH
Post by Todd
http://sourceforge.net/projects/freeotfe.mirror/
W7 64 bit does not allow you to run unsigned drivers,
except in "Test Mode". This is a problem for Free OTFE
as the drivers are (who knows why) unsigned.
Use free TrueCrypt instead. No drivers required. Has versions for
Windows, Mac OSX, and Linux. Portable version, too.
http://www.truecrypt.org/
Some folks like fewer options (i.e., simpler tool) and prefer the free
BestCrypt Traveller. Also, no drivers required. This is a portable app
but obviously you can run it as a normal app.
http://www.jetico.com/products/free-security-tools/bestcrypt-traveller
I don't know that TrueCrypt will read LUX-encrypted containers. They
typically only read the containers that they generated. You'll probably
have to use test mode in FreeOTFE to mount its container, mount a
container in TrueCrypt and then copy from FreeOTFE to TrueCrypt.
Hi Vanguard,

My extensive research shows that TrueCrypt and LUKS
are not compatible. I was hoping that TrueCrypt
would at least read LUKS, but no such luck.

I generate the content that goes on these flash drives
with Linux. LUKS is so fantastically well supported in
Linux (and is more secure than true crypt) that I did not
want to move to true crypt. Heck, even my hard drive
and all my backup drives are LUKS encrypted.

I was hoping I could get a way past the driver signing
problem with Windows 7+, 64 bit.

Do you know any way I can tell Windows not to hassle
Free OTFE's unsigned drivers?

Do you know anything else that can read LUKS in
Windows?

Many thanks,
-T
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
the riddle wrapped in an enigma wrapped
in a couple slices of baloney
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Todd
2014-05-07 01:52:17 UTC
Permalink
Post by Todd
Post by VanguardLH
Post by Todd
http://sourceforge.net/projects/freeotfe.mirror/
W7 64 bit does not allow you to run unsigned drivers,
except in "Test Mode". This is a problem for Free OTFE
as the drivers are (who knows why) unsigned.
Use free TrueCrypt instead. No drivers required. Has versions for
Windows, Mac OSX, and Linux. Portable version, too.
http://www.truecrypt.org/
Some folks like fewer options (i.e., simpler tool) and prefer the free
BestCrypt Traveller. Also, no drivers required. This is a portable app
but obviously you can run it as a normal app.
http://www.jetico.com/products/free-security-tools/bestcrypt-traveller
I don't know that TrueCrypt will read LUX-encrypted containers. They
typically only read the containers that they generated. You'll probably
have to use test mode in FreeOTFE to mount its container, mount a
container in TrueCrypt and then copy from FreeOTFE to TrueCrypt.
Hi Vanguard,
My extensive research shows that TrueCrypt and LUKS
are not compatible. I was hoping that TrueCrypt
would at least read LUKS, but no such luck.
I generate the content that goes on these flash drives
with Linux. LUKS is so fantastically well supported in
Linux (and is more secure than true crypt) that I did not
want to move to true crypt. Heck, even my hard drive
and all my backup drives are LUKS encrypted.
I was hoping I could get a way past the driver signing
problem with Windows 7+, 64 bit.
Do you know any way I can tell Windows not to hassle
Free OTFE's unsigned drivers?
Do you know anything else that can read LUKS in
Windows?
I only have to read in Windows, not write. As
a matter of fact, if I can not write all the better!
(Viruses won't jump to the stick.)
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
the riddle wrapped in an enigma wrapped
in a couple slices of baloney
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
VanguardLH
2014-05-07 05:22:57 UTC
Permalink
Post by Todd
I was hoping I could get a way past the driver signing
problem with Windows 7+, 64 bit.
Do you know any way I can tell Windows not to hassle
Free OTFE's unsigned drivers?
I have to wonder if FreeOTFE is dynamically loading its drivers.
Normally you get queried once about an unsigned driver, okay it, and
it's installed and works okay thereafter. If they're dynamically
loading drivers everytime they load their software then it's a new load
each time and why you get prompted each time. Maybe FreeOTFE is
designed as an always-portable application which means they have to load
their driver whenever their software gets executed.

http://msdn.microsoft.com/en-us/library/windows/hardware/ff544865(v=vs.85).aspx
http://msdn.microsoft.com/en-us/library/windows/hardware/ff548231(v=vs.85).aspx

Odd that the project refuses to sign their driver(s). I think this has
been a requirement for kernel-mode packages since around 2006.

http://msdn.microsoft.com/en-us/library/windows/hardware/ff547565(v=vs.85).aspx
http://www.techspot.com/community/topics/how-to-install-use-unsigned-drivers-in-windows-vista-7-x64.127187/

You could hit F8 and disable driver signature enforcement but you'd had
to do that every time you booted Windows. You try the bcedit trick to
see if it sticks between Windows sessions.
Post by Todd
Do you know anything else that can read LUKS in
Windows?
Sorry, but I never even heard of LUKS until this thread. I'd have to go
through the same online research that you would.
Todd
2014-05-08 17:50:18 UTC
Permalink
Post by VanguardLH
Post by Todd
Do you know anything else that can read LUKS in
Windows?
Sorry, but I never even heard of LUKS until this thread. I'd have to go
through the same online research that you would.
I drew a blank. That is why I posted
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
the riddle wrapped in an enigma wrapped
in a couple slices of baloney
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Loading...