Explore >> Select a destination
|
You are here 
|
gist.github.com | ||
| | | | |
www.integralist.co.uk
|
|
| | | | | ||
| | | | |
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. | |
| | | | |
wejn.org
|
|
| | | | | A tale how running your own x509 root CA - for internal services - changed in the last 20 years. | |
| | | | |
labanskoller.se
|
|
| | | This is an attachment to the blog post about the broken attestation certificate chain in YubiKey 4.3 and YubiKey NEO. Headers are mine and not part of the original conversation. Long commands have been split to multiple lines using \ to fit the blog. All indications of time are given in two time zones: CEST where I was sitting and PDT where Yubico Support was sitting. Initial Report on Wrong Commands in Documentation From me to Yubico Support: | ||
