Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.misc > #3420

Re: TrueCrypt killed off

From "tdk" <forum.tdk@squte.com>
Newsgroups comp.misc
Subject Re: TrueCrypt killed off
Date 2014-05-30 12:26 -0500
Organization solani.org
Message-ID <6218#28004@usenet.squte.com> (permalink)
References <lm7d9t$8uv$10@dont-email.me> <6218#27920@usenet.squte.com> <lmabrq$qsa$1@dont-email.me>

Show all headers | View raw


>Will FreeOTFE even run on 64-bit Windows?
yes, I use it on 64 bit Windows 7.

 From the help file:

=========================================================================================

In order to protect its revenue streams generated by DRM protected content,  
Microsoft saw fit to require all drivers running under the 64 bit (x64)  
version of Windows Vista and Windows 7 be digitally signed by Microsoft's  
root certificate.

Understandably, this presents a /major problem/ for the overwhelming majority  
of free software projects which make use of kernel mode drivers which, for  
obvious reasons, don't such a have a digital certificate (read: /haven't paid  
Microsoft, or one of their resellers, for such a certificate/) to sign their  
drivers with.

For the same reason, FreeOTFE's drivers are not currently signed with a  
Microsoft certificate.

Fortunately, there are a number of methods of loading unsigned drivers under  
Windows Vista x64/Windows 7 x64, /without/ having to /pay/ for a digital  
certificate, and these are summarised below.

*As a consequence, it /is/ possible to use FreeOTFE under Vista x64/Windows 7  
x64 by using the methods shown as be successful below*

A more long term solution (Microsoft signing) is being investigated.

------------------------------------------------------------------------------
.... Summary of Different Methods

Below is a table summarising the different methods of configuring Windows  
Vista x64/Windows 7 x64 to allow it to run FreeOTFE.

For most users, Method 3: TESTSIGNING ON [1] is recommended

MethodResults"Test Mode"
on wallpaperJunk messages
shown on manual startRecommended?1. NOINTEGRITYCHECKS ON  
[2]IneffectiveNoYesNo2. DDISABLE_INTEGRITY_CHECKS [3]May workNoYes�3.  
TESTSIGNING ON [4]WorksYesNo*Yes*4. <F8> while booting [5]WorksNoYes�5.  
ReadyDriver Plus [6]WorksNoYes�6. EasyBCD [7]May workNoYesNo7. Signing with  
a Microsoft certificate [8]WorksNoNo�
.. "Test Mode" on wallpaper

The method with "Yes" marked in this column indicates that the words "Test  
Mode" will be shown in each of the four corners of the desktop wallpaper.  
This is largely a cosmetic issue, and can be resolved using the directions  
indicated in the description of this method.

.. Junk messages shown on manual start

Those methods with "Yes" marked in this column indicate that MS Windows will  
pop up a message stating: "Windows requires a digitally signed driver" for  
each and every driver loaded - even though the drivers /are/ digitally signed  
(albeit using self-certification).

If the drivers are started automatically on booting, these messages will  
/not/ appear.

However, if the FreeOTFE drivers are started from the GUI (e.g. by starting  
portable mode). Since FreeOTFE's flexible architecture employs multiple  
drivers, this is hardly ideal as the user gets peppered with junk messages  
telling them what they're doing - as if they didn't already know!

The number of these messages shown can be minimised by removing all unused  
hash and cypher drivers.

[snip]

.... Method 3: TESTSIGNING ON

Instructions:

 1) Open an elevated command prompt by /either/:
     * Clicking the "Start" button on the Windows taskbar, type CMD in the
       /search box/, and then press <CTRL+SHIFT+ENTER> to run CMD with
       administrator privileges), /or/
     * Locating "cmd.exe" under C:\Windows\System32 in Windows Explorer,
       rightclicking on this executable and selecting "Run as Administrator"
       from the context menu
    
 2) Click "continue" or enter the administrator's password as appropriate and
    click "OK", when asked for permission to continue.
 3) In the command prompt window which appears, type:
    >bcdedit.exe /set TESTSIGNING ON
 4) Reboot the PC

/This method is probably the best solution,/ and allows FreeOTFE to run  
correctly. However, it does have a trivial side effect: The words "Test Mode"  
are shown in the four corners of the Desktop wallpaper after rebooting.

Although only a cosmetic issue, the words "Test Mode" may be removed from  
your background by using one the following methods:

 * Remove and Erase Desktop "Evaluation Copy", "Test Mode" or "Safe Mode"
   Watermark in 64-bit (x64) Vista [9]
 * Get Rid Of and Remove Evaluation Copy Watermark in Vista After
   Installating SP1 [10]
 * Remove and Disable Windows Vista Evaluation Watermark from Desktop [11]

=========================================================================================

I found this method "TESTSIGNING ON" woked for me. Portable mode also doesn't  
work well in Windows 7.


[1] #Method_3
[2] #Method_1
[3] #Method_2
[4] #Method_3
[5] #Method_4
[6] #Method_5
[7] #Method_6
[8] #Method_7
[9] http://www.mydigitallife.info/2008/01/09/remove-and-erase-desktop-evaluation-copy-test-mode-or-safe-mode-watermark-in-64-bit-x64-vista/
[10] http://www.mydigitallife.info/2007/11/03/get-rid-of-and-remove-evaluation-copy-watermark-in-vista-after-installating-sp1/
[11] http://www.mydigitallife.info/2006/11/23/remove-and-disable-windows-vista-evaluation-watermark-from-desktop/
-- 
regards
~tdk
View this thread at http://squte.com/node/6218#comment-28004

Back to comp.misc | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

TrueCrypt killed off Scion <a.b@nospam.invalid> - 2014-05-29 13:39 +0000
  Re: TrueCrypt killed off Hils <hils@saynotospam.net> - 2014-05-29 14:57 +0100
  Re: TrueCrypt killed off Mike Easter <MikeE@ster.invalid> - 2014-05-29 07:14 -0700
  Re: TrueCrypt killed off Paul Sture <nospam@sture.ch> - 2014-05-29 19:53 +0200
    Re: TrueCrypt killed off Oregonian Haruspex <bob_davis_retired@yahoo.com> - 2014-06-09 23:35 +0000
  Re: TrueCrypt killed off "tdk" <forum.tdk@squte.com> - 2014-05-30 07:39 -0500
    Re: 'Re: TrueCrypt killed off' "tdk" <forum.tdk@squte.com> - 2014-05-30 08:45 -0500
      Re: 'Re: TrueCrypt killed off' Mike Easter <MikeE@ster.invalid> - 2014-05-30 10:02 -0700
    Re: TrueCrypt killed off scott@alfter.diespammersdie.us (Scott Alfter) - 2014-05-30 16:32 +0000
      Re: TrueCrypt killed off "tdk" <forum.tdk@squte.com> - 2014-05-30 12:26 -0500
        Re: 'Re: TrueCrypt killed off' "tdk" <forum.tdk@squte.com> - 2014-05-30 12:41 -0500

csiph-web