ansible-collection-hardening
rustls
ansible-collection-hardening | rustls | |
---|---|---|
25 | 57 | |
3,687 | 5,456 | |
1.4% | 1.3% | |
9.1 | 9.9 | |
7 days ago | 5 days ago | |
Jinja | Rust | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
ansible-collection-hardening
-
Ask HN: What open-source projects are you currently contributing to and why?
An ansible collection for hardening Linux systems I mostly wrote: https://github.com/dev-sec/ansible-collection-hardening
Another ansible collection to manage Icinga: https://github.com/T-Systems-MMS/ansible-collection-icinga-d...
And the yunohost app for invoice ninja: https://github.com/YunoHost-Apps/invoiceninja5_ynh
-
Ansible - how widely used is it ?
i have some packer builds where itll install ansible, run playbooks locally, then uninstall ansible. such as the the devsec os hardening role: https://github.com/dev-sec/ansible-collection-hardening
- What hardening before forwarding services?
-
Security Harden Ubuntu 22.04
This collection is also interesting https://github.com/dev-sec/ansible-collection-hardening/
-
What you guys use for website protection? We use sentinel one but doesn't cover web related items
Second you want to ensure the os is secure and up to date. Take a look at os hardening best practices, for example this ansible playbook for linux: https://github.com/dev-sec/ansible-collection-hardening
- Ansible for automation/ hardening.
-
How do you document your (whole) setup ? Looking for ideas.
To ensure SSH and other security related things are configured correctly, you can take a look at DevSec which helps you to apply proven security configuration principles. Also there is guides like "Secure Secure Shell" which can help you to better understand what you can do to increase the security of your servers (this one is from 2015 but many aspects are still relevant).
-
Recommendations for advanced material (reading material, courses, etc) on server security?
I learned a lot by using and reading through the source code of these ansible roles: https://github.com/dev-sec/ansible-collection-hardening
-
Ask HN: How to secure Ubuntu VPS in 2022?
Have a look at https://github.com/dev-sec/ansible-collection-hardening
-
SSH Bastion host best practices: How to Build and Deploy a Security-Hardened SSH Bastion Host
You can do much more https://github.com/dev-sec/ansible-collection-hardening/tree/master/roles/ssh_hardening
rustls
- Pingora: HTTP Server and Proxy Library, in Rust, by Cloudflare, Released
- Alternative to openssl for reqwest https with client certs.
- rustls 0.22 is out with pluggable crypto providers and better CRL support
-
Exploring the Rust compiler benchmark suite
The RustTLS project is currently setting up their own CI benchmarking workflow, so I think that you could find some inspiration there: https://github.com/rustls/rustls/issues/1385 and https://github.com/rustls/rustls/issues/1205.
-
What are the scenarios where "Rewrite it in Rust" didn't meet your expectations or couldn't be successfully implemented?
I also studied this question on FFI several weeks ago in terms of "rewrite part of the system in Rust". Unexpected results could be semantic issues (e.g., different error handling methods) or security issues (FFI could be a soundness hole). I suggest going through the issues of libraries that have started rewriting work such as rust-openssl or rustls (This is the one trying to rewrite in whole rust rather than using FFI; however, you will not be able to find the mapping function in the C version and compare them). I hope this helps!
-
A brief guide to choosing TLS crates
Now for rust implementation of tls. Certificates can be loaded in two ways. * Finds and loads certificates using OS specific tools3 * Uses a rust implementation of webpki4 for loading with certificates5
-
Microsoft is busy rewriting core Windows library code in memory-safe Rust
> Ring is mostly C/Assembly
Crypto needs to be written in Assembly to ensure that operations take a constant time, regardless of input. Writing it in a high level language like C or Rust opens you up to the compiler "optimising" routines and making them no longer constant time.
But you already knew this. And you also knew that the security audit (https://github.com/rustls/rustls/blob/master/audit/TLS-01-re...) of ring was favourable
> No issues were found with regards to the cryptographic engineering of rustls or its underlying ring library. A recommendation is provided in TLS-01-001 to optionally supplement the already solid cryptographic library with another cryptographic provider (EverCrypt) with an added benefit of formally verified cryptographic primitives. Overall, it is very clear that the developers of rustls have an extensive knowledge on how to correctly implement the TLS stack whilst avoiding the common pitfalls that surround the TLS ecosystem. This knowledge has translated reliably into an implementation of exceptional quality.
You said
> a standard library with feature flags and editions would make rust ridiculously much more productive
What's the difference between opting into a library with a feature flag and opting in with a line in Cargo.toml? Let's say you want to use the de-facto regex library. Would it really be ridiculously productive if you said you wanted the "regex" feature flag instead of the "regex" crate?
I do agree that the standard library does need a versioning story so they can remove long deprecated functions. Where it gets complicated is if a new method is reintroduced using the same name in a later edition.
-
gRPC with mutual TLS on IPs only
I used the commands listed in the .sh file here: https://github.com/rustls/rustls/tree/main/test-ca to generate keys/certs for a server and a client (with IP.1 records for SANs). I have added the local root CA to the trust store of each VM.
-
rustls 0.21 released with support for IP address server names
This is great news, this was our single biggest annoyance with rustls. One of our cloud providers choses to issue their hosted postgres instances with TLS certificates with IP addresses. Unusual, but valid per the spec, so why not. Apparently a practise that's also popular in kubernetes settings, so I'm somewhat surprised it took 5 years to close the issue, but now I can finally recommend people to use rustls without mentioning any gotchas.
-
Is Rust really safe? How to identify functions that can potentially cause panic
I believe it is more relevant than you think: servers running in containers, web assembler tasks running in browsers, embedded devices and kernels with total control of the system, all have the ability to do something more sensible than plain out SIGABRT or similar, and in many the case is not that the complete system is falling down. For example RustTLS is looking into allowing fallible allocators and as a pretty general-purpose library that seems like a nice feature. I do wish ulimit -v worked in a sensible manner with applications.
What are some alternatives?
debian-cis - PCI-DSS compliant Debian 10/11/12 hardening
rust-native-tls
crowdsec - CrowdSec - the open-source and participative security solution offering crowdsourced protection against malicious IPs and access to the most advanced real-world CTI.
rust-openssl - OpenSSL bindings for Rust
goss - Quick and Easy server testing/validation
mkcert - A simple zero-config tool to make locally trusted development certificates with any names you'd like.
RHEL7-CIS - Ansible role for Red Hat 7 CIS Baseline
ring - Safe, fast, small crypto using Rust
ansible-collection-nginx - Ansible collection for NGINX
webpki - WebPKI X.509 Certificate Validation in Rust
netboot.xyz - Your favorite operating systems in one place. A network-based bootable operating system installer based on iPXE.
rust-crypto - A (mostly) pure-Rust implementation of various cryptographic algorithms.