Explore >> Select a destination
|
You are here 
|
gist.github.com | ||
| | | | |
github.com
|
|
| | | | | Kubernetes website and documentation repo: . Contribute to kubernetes/website development by creating an account on GitHub. | |
| | | | |
www.integralist.co.uk
|
|
| | | | | Introduction Directory Structure Configuration Building Running Verifying Revocation References Conclusion Introduction The purpose of this post is to demonstrate how to configure nginx to use client certificates for authenticated access to your back-end service (in this example: a Ruby/Sinatra application). Note: the focus of this post isn't about Ruby/Sinatra so don't worry if your back-end service is built with another programming language I won't be going into the details of how most of it was set-up... | |
| | | | |
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. | |
| | | | |
blog.polleverywhere.com
|
|
| | | An overview of standard and extended certificates used in code signing, their trust levels, and why extended certificates cost so much more. | ||
