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.

Security & PrivacyLearning & ReferenceMobile & Desktop
Explore on GitHubRead Hacker News discussions
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 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 5:05:26 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

1 sources
sandreas·Jan 28, 2024
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?

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.