Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installation of v0.7.4.1 fails on clean win 7 #4

Open
MarcinOrlowski opened this issue Sep 5, 2016 · 11 comments
Open

Installation of v0.7.4.1 fails on clean win 7 #4

MarcinOrlowski opened this issue Sep 5, 2016 · 11 comments

Comments

@MarcinOrlowski
Copy link

I tried install v0.7.4.1 on clean Win 7 box and installer failed. Installation was as-is, no option disabled in settings. First, the dialog "Unable to find required procedure" shows up (it looks like system dialog as it is transladed), and then when I hit "OK" it shows another dialog:

Failed to install 'C:\Windows\system32\Drivers\truecrypt.sys`. Do you want to continue installing?

@GigabyteProductions
Copy link

This is a regression that's being worked on now.

@MarcinOrlowski
Copy link
Author

Where can I find older builds?

@GigabyteProductions
Copy link

Same place; other branches. I think the last one before 0.7.4.1 is https://github.com/CipherShed/CipherShedBuilds/tree/v0.7.4.0-20151231.

@MarcinOrlowski
Copy link
Author

Thanks. 0.7.4.0 installs fine.

@UIfric
Copy link

UIfric commented Dec 17, 2016

Will ask here... What about Windows 10? Does CipherShed support that new UEFI , I mean - can it encrypt whole system boot partitions with boot authentication?

@GigabyteProductions
Copy link

EFI support is a work in progress with a new installer.

@jult
Copy link

jult commented Apr 25, 2017

I don't think whole system disk encryption is the way to go, to be honest. Volumes (as huge files) that are encrypted are a much better idea, and they can function as RAMdisk at the same time, which can be made advantageous. You should have your system set up so that an opened (decrypted) volume is auto-dismounted (in encrypted state only) when you consider access to your system by untrusted parties a valid danger, be that in hybernation, sleep mode, shutdown etc.

@GigabyteProductions
Copy link

While file containers can be easier, there are a lot of nearly out of control ways that information can leak out of them when the running environment is storing data unencrypted. Some examples include indexing, Windows registry, Windows explorer history, ever storing the data unencrypted (even temporarily), swap files and especially hibernation. Encrypting the entire disk is a security must.

@xaminmo
Copy link

xaminmo commented Jun 22, 2017

FYI, if you unpack 7.4.1 to the install dir, and then install, even with the errors, it puts truecrypt.sys where it needs to be, and seems to work fine.

@xaminmo
Copy link

xaminmo commented Jun 22, 2017

Regarding "Encrypting the entire disk is a security must" really should read "encrypting the entire system..." Because I could encrypt whole drives, but not the system drive, and still run into the same issues pointed out by Kyle.

@GigabyteProductions
Copy link

You are correct. I didn't consider multi-drive configurations at the time of writing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants