madaidans-insecurities.github.io VS book

Compare madaidans-insecurities.github.io vs book and see what are their differences.

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
madaidans-insecurities.github.io book
29 3
132 68
- -
0.0 0.0
4 months ago 11 months ago
HTML Dockerfile
- -
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

madaidans-insecurities.github.io

Posts with mentions or reviews of madaidans-insecurities.github.io. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-06-02.

book

Posts with mentions or reviews of book. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-01-15.
  • Ask HN: How do you trust that your personal machine is not compromised?
    6 projects | news.ycombinator.com | 15 Jan 2023
    > For details on how I use Qubes specifically see: https://github.com/hashbang/book/blob/master/content/docs/se...

    How is this not a contradiction?

    >6. Manual PRIVILEGED SYSTEM mutations MUST be approved, witnessed, and recorded

    >7. PRIVILEGED SYSTEM mutatations MUST be automated and repeatable via code

  • Ask HN: What are you doing to secure your software supply chain?
    2 projects | news.ycombinator.com | 16 Dec 2021
    Some of my clients pay to do double review of all dependencies.

    Others go as far as distributed deterministic builds to ensure CI/CD systems themselves are not compromised.

    Here are the latest public iterations of my recommendations.

    https://github.com/talos-systems/rfcs/blob/main/001-software...

    Also here are complimentary practices to ensure the production engineers that must have access to CI/CD systems etc don't themselves become a weak link in the supply chain (which happens a -lot-).

    https://github.com/hashbang/book/blob/master/content/docs/se...

    Shameless plug: My company Distrust (short for Distributed Trust), offers auditing, consulting, and support so companies can avoid single points of failure in their supply chains from third party libs to the hands of end users. Happy to chat with anyone that wants some outside eyes in this area!

What are some alternatives?

When comparing madaidans-insecurities.github.io and book you can also consider the following projects:

ansible-collection-hardening - This Ansible collection provides battle tested hardening for Linux, SSH, nginx, MySQL

mvt - MVT (Mobile Verification Toolkit) helps with conducting forensics of mobile devices in order to find signs of a potential compromise.

iceraven-browser - Iceraven Browser

silverblue-site - Historic website for Fedora Silverblue. Now at https://gitlab.com/fedora/websites-apps/fedora-websites/fedora-websites-3.0

Win32-OpenSSH - Win32 port of OpenSSH

tripwire-open-source - Open Source Tripwire®

qubes-app-split-browser - Tor Browser (or Firefox) in a Qubes OS disposable, with persistent bookmarks and login credentials

rfcs

magic-wormhole - get things from one computer to another, safely [Moved to: https://github.com/magic-wormhole/magic-wormhole]

rustls - A modern TLS library in Rust

itpol - Useful IT policies

panzerlop - Configuration Guides for fixing things in Linux, Proton & KDE