-
-
Notifications
You must be signed in to change notification settings - Fork 195
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
Revamp full disk encryption section #2437
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for privacyguides ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
||
</details> | ||
|
||
While BitLocker is not officially supported on Windows Home, it can be enabled on Home editions with a few extra steps. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have we actually checked to see if this works? It did at one point but this indicates it might not #2407
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question, I did see that issue. To me it read as if it worked except they accidentally did the process on a non-boot drive since their drive letters were weird.
Which is why I added:
+ This guide assumes the drive letter of your operating system drive is "C". If it is not, replace `c:` with the correct drive letter in the following commands.
Though maybe I'm interpreting what they're saying wrong.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was also a thread https://discuss.privacyguides.net/t/enabling-bitlocker-on-the-windows-11-home-edition/13303/ about it. could just check in a VM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(rebased)
19d9058
to
a909cf7
Compare
e124ecf
to
82ab189
Compare
maybe worth nothing: latest cryptsetup 2.7.0 adds SED support: https://mirrors.edge.kernel.org/pub/linux/utils/cryptsetup/v2.7/v2.7.0-ReleaseNotes so it can automatically layer both hw+sw encryption without any extra steps, might as well use it if you have it |
Thanks for sharing, though I'm not knowledgeable enough on LUKS/Linux to feel comfortable writing about that. If you feel it's good information to add then I would encourage you to add on to this PR @SkewedZeppelin |
✅ Your preview is ready!
|
Yes it will. We consolidating that PR with #2452 and then I intend to add original author as co-author. I want to get that one merged as they've worked quite hard on it. Initially the plan was to wait until we did research on LGPO policies that would make relevant privacy improvements. I've decided against that for the time being because it will require considerable resources and can always be added later by someone with specific knowledge in that area. The intention is then to merge this PR after the Windows one though. I think that makes logical sense to do it in that order so we don't have to move things around later and annoy the translators. I am currently proofing/finishing up #2268 which was contributed by someone else, this makes a good first step because explains some of the hardware features available, particularly in Windows. |
0a94f3f
to
d80af39
Compare
https://deploy-preview-2437.preview.privacyguides.dev/en/encryption/#os-full-disk-encryption
Changes in the order they appear:
Up for discussion:
Maybe want to consider removing (or at least testing) the BitLocker on Home guide: Revamp full disk encryption section #2437 (comment)