HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
drduh
macOS-Security-and-Privacy-Guide
Shell2015–2024
drduh / macOS-Security-and-Privacy-Guide

macOS-Security-and-Privacy-Guide

Community guide to securing and improving privacy on macOS.

34Distinct people
37Mentions
0Explicit recommenders
22.6KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Community guide to securing and improving privacy on macOS.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year37 dated mentions

Observed mentions: 2015-08-31 04:01:17 UTC to 2024-01-28 13:19:46 UTC.

024682015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 5 mentions; 3 submissions, 2 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC532
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC725
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC514
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC817
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC615
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC202
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101

What Hacker News says

37 sources
I usually maintain a little git repository `.dotfiles` with all my personal preferences and config files. Although it is designed to be made public, I didn't do it - I was too scared I forgot something :-) In this repo I also created subdirectories for automated setup scripts for different operating systems. It looks something like this: docker ... custom docker files and scripts etc git .gitconfig .gitignore_global ssh hosts.d config vim vimrc zsh ... (multiple config files and dirs, e.g. powerlevel10k) linux artix setup.sh fedora setup.sh ubuntu setup.sh macos setup.sh common_functions.sh All I need to do is install git, check out the repo and run the setup script of the current system - works for linux and macOS, although I don't use ma
Read the rest
cOS that much any more. These Scripts are designed to be run multiple times without damaging anything. Works out pretty well. For macOS I tried to automate as much as possible (via `brew` and `brew --cask` and for settings via `defaults write`), similar to all these repositories using this technique: https://dotfiles.github.io/inspiration/ Additionally from time to time I try to lookup hardening guides like this: https://github.com/drduh/macOS-Security-and-Privacy-Guide
In Ask HN: How do you setup a new Mac?
- 1Password - Fastmail (block images in email, which are often used for tracking) - Privacy.com 1Password integrates with both of the above, so that any time I sign up for a new service it will get a random, unique email from Fastmail (masked email), a unique credit card from privacy.com, and I use 1Password to generate not only a unique, strong password but also a unique username (hence my current username here, squeegee_scream). - sync.com for online storage. it's e2ee - MFA everywhere it's available - 1Blocker - nextdns - use privacy-respecting alternative frontends: - use invidious instead of youtube - libreddit or teddit instead of reddit - nitter instead of twitter - macos, following https://github.com/drduh/macOS-Security-and-Privacy-Guide for hardening (I haven't compared this to other hardening guides, but doing some
Read the rest
thing is better than nothing) - rotate my usernames on social sites on a regular basis. I'm really only active on reddit and HN, but I'm still concerned about being doxxed - avoid buying things from amazon - Signal app for communication as often as possible
In Ask HN: What do you do for online privacy?
macOS Mail.app -> Preferences -> Viewing -> Uncheck "Load remote content in messages" Privacy defaults come down to usability vs. privacy; Apple making this so easy to toggle is fine by me as I care about privacy and tracking. Now, it would be great if every macOS application walked you through privacy settings right after installation in the same way that I am offered a tour of the new features. Since there is no such "privacy tour", the community has discussed ways in which macOS can be hardened [1], [2]. 1. https://github.com/drduh/macOS-Security-and-Privacy-Guide 2. https://news.ycombinator.com/item?id=18099835
In Spy pixels in emails 'have become endemic'
Not OP but one example is bridged networking. I discovered this while trying Parallels Lite from the App Store. I was used to being prompted for every connection attempt VirtualBox was making but I was not getting any when using Parallels. I contacted Little Snitch's support and they acknowledged the issue but said that there's not much they can do because Little Snitch works on "application level" and Parallels uses bridged mode of networking that Little Snitch is unable to intercept. Note that the Lite version of Parallels doesn't require any kernel extensions (even on older macOS releases). If an application is running as root, you are similarly able to use the lower level APIs and completely "bypass" Little Snitch. I cannot find a good alternative source for this other than the Security and Privacy Guide [0]: It is worth noting that t
Read the rest
hese firewalls can be bypassed by programs running as root or through OS vulnerabilities (pdf), but they are still worth having - just don't expect absolute protection. [0] https://github.com/drduh/macOS-Security-and-Privacy-Guide#th...
In Apple's apps bypass firewalls like LittleSnitch and LuLu on macOS Big Sur
tptacek's criticisms are quite valid. However, "it's not good" seems oversimplified to me? I found lots of interesting information in this. For example: information about the activation process for Macs, importance of setting a firmware password, disable some of the Spotlight services, and binary whitelisting through Santa. The repo also has the most comprehensive discussion I've seen about evicting FileVault keys from RAM on sleep: https://github.com/drduh/macOS-Security-and-Privacy-Guide/is... Also, I'm not sure if this has been changed more recently than the comment you linked, but it seems like they actually don't recommend AV software anymore: "Therefore, the best anti-virus is Common Sense 2020. See discussion in issue #44." I grant you that having someone follow this top to bottom might be bad, but to say "it's not good" seems t
Read the rest
o both lack nuance and also to discard some useful, hard work done in good faith.
In macOS Security and Privacy Guide
i've increasingly been having issues with hands off![0] on my machine (intermittent high cpu usage, regular kernel panics), and was actually looking at this guide a while back to decide whether i should switch to pf instead[1]. but pf seems to require much more configuration and management. anyone have experience/pointers in this regard? [0] i used to use little snitch many years ago, but ran into similar issues with it over time (maybe it's better now). [1] https://github.com/drduh/macOS-Security-and-Privacy-Guide#ke...
In macOS Security and Privacy Guide

Showing the 15 most recent of 37 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.