update!: Windows guide #1659
update!: Windows guide #1659
Conversation
|
🎊 PR Preview 6865c06 has been successfully built and deployed to https://privacyguides-privacyguides-org-preview-pr-1659.surge.sh 🕐 Build time: 74.102s
🤖 By surge-preview |
dngray
added
c:os
jonaharagon
force-pushed
the
main
branch
2 times, most recently
from
b5ff399 to
b9612de
Compare
✅ Deploy Preview for privacyguides ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
Please don't ping a bunch of contributors or leave multiple consecutive comments on this PR. This guide is a work in progress. |
|
Okay, Jonah. But in my Opinion I have finished what I could do.So, Merging is totally upto you. I could add stuff if wanted. |
|
This pull request has been mentioned on Privacy Guides. There might be relevant details there: |
|
This pull request has been mentioned on Privacy Guides. There might be relevant details there: https://discuss.privacyguides.net/t/recommending-apple-products/10815/9 |
|
This pull request has been mentioned on Privacy Guides. There might be relevant details there: |
|
I am at some point going to have another look at this, we should incorporate https://github.com/privacyguides/privacyguides.org/pull/1979/files into it as an tip. |
|
This discussion https://github.com/privacyguides/privacyguides.org/discussions/1281 brought up that we should remind users to update their systems. We should probably have some mention about BIOS updates too, https://github.com/privacyguides/privacyguides.org/discussions/1280 as not all systems this comes through Windows Update. Of course there will only be only general instructions as different vendors use different update tools on Windows. |
jonaharagon
force-pushed
the
main
branch
2 times, most recently
from
67e4d9a to
2150385
Compare
|
@dngray - Not a problem. I have to rework a lot on this as I haven't updated it more than a year and I haven't made my writing visible yet on the preview. Need to add it in mkdocs.yml If you merge the other one first, Maybe I will modify this one as some suggestions to it. Let's see. I hope, I could start working on this before you come back to Windows section. @oppressor1761 - Shall we two work on this together or separately - Totally your choice ? |
|
I'm working on merging this one together, it will be based off #2606 (then when that is merged we can look at merging this one). |
dngray
force-pushed
the
Windows
branch
3 times, most recently
from
8714b3c to
a7e8eff
Compare
|
I pushed to it, before, but haven't made any changes, it will require some time to go over. I haven't read it in detail |
|
Since #2591 added a dedicated page for Group Policies, I suggest moving the GP instructions in "Security policies for Bitlocker" to the aforementioned page, and adding an internal link to the BitLocker section of the GP page in its place. Other group policy recommendations introduced in this PR can also be moved to the dedicated GP page. |
That's exactly what I had in mind in regard to #2437 (comment). I haven't yet gone over this PR and read it, in entirety just getting the structure right of what should be where as it is huge. |
There was a problem hiding this comment.
I haven't used Windows for quite a while now so, for this PR, I can offer suggestions only regarding grammar, formatting, and consistency with other parts of the Privacy Guides site.
Aside from my earlier suggestion about consolidating Group Policy recommendations, other parts of the PR caught my eye, which I commented on below.
|
|
||
| ## Security Improvements | ||
|
|
||
| - Use [PeaZip](https://peazip.github.io/) archiver instead of 7-zip as it disables [Mark of the Web(MoW)](https://nolongerset.com/mark-of-the-web-details/) [support by default](https://github.com/nmantani/archiver-MOTW-support-comparison#*2) leading to execution of malicious instantly after extracting. |
There was a problem hiding this comment.
I don't think that this guide (which will be housed in the Knowledge Base) should include tool recommendations that are not native to the OS.
Besides, the linked resource about Mark of the Web mentions that the unzipping tool built in to Windows preserves the MOTW.
There was a problem hiding this comment.
Well, At then time, 7Zip or Windows didn't preserve MoTW. I don't remember quite well.
|
|
||
| - Use [PeaZip](https://peazip.github.io/) archiver instead of 7-zip as it disables [Mark of the Web(MoW)](https://nolongerset.com/mark-of-the-web-details/) [support by default](https://github.com/nmantani/archiver-MOTW-support-comparison#*2) leading to execution of malicious instantly after extracting. | ||
|
|
||
| - Using MS edge or brave over Firefox. Edge is recommended with MDAG mode for secure browsing if security is your priority. Brave is recommeded if content blocking is important for you (Brave shields) |
There was a problem hiding this comment.
There's already a page for desktop browser recommendations on the site.
There was a problem hiding this comment.
You are right. Will remove it since MDAG is gonna be killed by microsoft afaik.
|
|
||
| ## Apps | ||
|
|
||
| - Avoid any types of Cleaning software at all cost. As Microsoft is working on its own implementation specfically designed for windows. |
There was a problem hiding this comment.
Including a brief explanation of why people using Windows should avoid cleaning software would be useful here.
Also, is the native implementation of cleaning software you're referring to called "Microsoft PC Manager"? From these forum posts, it looks like Windows users have to download it from the Microsoft Store themselves and the software isn't available in all geographical regions.
This is refresh commit made due to merge conflicts that came when trying to sync the fork
This is done with respect to comment by 128bitpotato - https://discuss.privacyguides.net/t/windows-guide/250/81
Co-authored-by: noClaps <[email protected]>
Co-authored-by: noClaps <[email protected]> Co-authored-by: Pa1NarK <[email protected]>
docs/os/windows/windows-overview.md
Outdated
There was a problem hiding this comment.
A lot of the information from this page was adapted to the current Windows Overview in #2591.
Unless someone has specific suggestions on information in this drafted page that should be added to the current Windows Overview on the site, I think this page should be removed to reduce the size of this PR and make it easier for reviewers to go over the PR.
There was a problem hiding this comment.
I haven't looked at this PR in detail, but it should be possible to create several PRs for those various sections from this one.
We can always give @IkelAtomig credit for the ones which were heavily based on this one, perhaps splitting them up would make it more workable?
|
Ah, Should I do anything because I kind of orphaned this PR. I would be glad if some parts of it are made into the site and my name is in the footer. That's it. |
|
don't close it. The other one will do that when it is merged, and yes you're on it as co-author, so you'd get the same credit in your git activity. |
|
I want it to be on the privacyguides site. Greedy me. |
|
@IkelAtomig on second thoughts, I think it might be better if we split this off onto three PRs, one for each page (sandboxing, privacy, hardening), as long as you're the author, of each it will show your name at the bottom of the page. We need to then just check whether |
|
Alright, just say what to do when you are ready. |
Closes: #1380
This is a successor to #1380 Pull request by me. Things that are there will follow here but in a paced manner with concise information.
I have stated the reason in the old one for its closure.
If you are suggesting big Changes, make a PR other than that do Code reviews.
Do not comment about your suggestions in this PR as I want it clean and don't want it confusing either for me or to the contributors. So, Suggest them in Issue #166. I am following it.
There will be no ETA for this. I will work on this in my Free time and try finish ASAP.