Explore >> Select a destination
|
You are here 
|
current.workingdirectory.net | ||
| | | | |
younes.codes
|
|
| | | | | Learn how to run Rails over HTTPS on localhost, in development environment. | |
| | | | |
gist.github.com
|
|
| | | | | Self Signed Certificate with Custom Root CA. GitHub Gist: instantly share code, notes, and snippets. | |
| | | | |
www.sudo.ws
|
|
| | | | | Using sudo_logsrvd to centrally collect sudo session recordings from your network is a huge step forward in security: users cannot delete or modify session recordings locally. However, by default, transmission of recordings is not encrypted, making it open to modifications and eavesdropping. Encrypting the connection between sudo and sudo_logsrvd can eliminate these problems. Larger environments usually either have in-house PKI tooling in place, or colleagues who know all openssl options off the top of their heads. However, small and medium enterprises often lack the infrastructure or knowledge to work with TLS certificates. | |
| | | | |
dadrian.io
|
|
| | | This post is about HTTPS (X.509) certificates used on the web1. It has two parts: Certificates explained without cryptography Certificates explained with cryptography The explanation with cryptography depends on the explanation without cryptography, so you'll want to either read both, or only read Part 1. Certificates and certification authorities, explained without cryptography Websites use certificates to prove that they're the "real" website2, and not an imposter. The certificate is used to bootstrap ... | ||
