/explore
|
You are here 
|
gist.github.com | ||
| | | | |
squanderingti.me
|
|
| | | | | A handy explanation for the fields in a digital certificate. | |
| | | | |
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. | |
| | | | |
zaries.wordpress.com
|
|
| | | | | There are thousands of articles and entries in stackexchange but none of them worked for me out of the box. So after hours of battling with this issue here is my short recipe. Create the Root Key: openssl genrsa -out rootCA.key 2048 Self-sign this root certificate: openssl req -x509 -new -nodes -key rootCA.key -sha256 -days... | |
| | | | |
malgregator.com
|
|
| | | Leverage PKCS#11 support in curl to authenticate with the Vault's TLS Certificates Auth Method | ||
