macOS-Security-and-Privacy-Guide VS Peergos

Hi friends, I followed this guide: https://github.com/drduh/macOS-Security-and-Privacy-Guide and some additional steps to protect my macbook from being accessed by unauthorized people. The key steps I did was a full disk encryption and a custom firmware password. This makes it extremely difficult to repurpose my macbook after for example a theft. The reason I want this is that I often study in university or sometimes work in public places, but I also work as a software developer with sensitive consumer data.

https://github.com/drduh/macOS-Security-and-Privacy-Guide/is...

turn on FileVault , turn on the firewall (built in). install Lulu firewall follow this guide and harden the system https://github.com/drduh/macOS-Security-and-Privacy-Guide

I'm looking for a guide to harden MacOS Ventura, preferably including little snitch/lulu blocklist suggestions for MacOS services. I'm aware of dr druh's guide (that currently doesn't seem to be updated for Ventura though) and isn't including a little snitch/lulu blocklist.

- macos, following https://github.com/drduh/macOS-Security-and-Privacy-Guide for hardening (I haven't compared this to other hardening guides, but doing something is better than nothing)

I remember seeing this, I have never followed it so I don't know what it's worth but it's seems quite comprehensive

Would love to hear your thoughts on Peergos - https://peergos.org

https://github.com/peergos/peergos

A good Dropbox alternative is Peergos (founder here). Peergos is an E2EE P2P storage, sharing and application protocol. Fully open source, including the server, self-hostable, no VCs.

https://peergos.org

You can do that with peergos [1]- mount a peergos folder locally using FUSE. Or login to the web interface and share easily and privately.

[1] https://github.com/peergos/peergos

You might be interested in the p2p design of Peergos. You sign up to Peergos[0]. Your initial server is just responsible for storing your data (although you can run as many live mirrors as you like), and clients verify all updates. You can automatically move server (by running a command) and all your data is moved, and old links continue to work, and you keep your social graph and identity.

You can also log in through any instance, including localhost. Links also work on any server because they include a capability to the content in the link.

This is the beauty of content addressing plus public key based addressing.

[0] https://peergos.org

Totally agree! Shameless self promotion: have a look a Peergos - https://github.com/peergos/peergos

Our tech book might be a better starting point for this group: https://book.peergos.org

https://peergos.org

https://book.peergos.org

https://github.com/peergos/peergos

Features:

* audited by Cure53

* protects metadata (directory structure, file name and properties, file sizes, social graph)

* fine grained capability-based access control

* built-in social media

* sandboxed 3rd-party apps: e.g. word doc viewer, calendar, text editor, games etc.

* FUSE bindings

* CLI

* cross platform

* browser client