Offloading Cryptography with the Vault Transit Engine
Stop leaking keys in config files. Learn how to use the Vault Transit engine to offload cryptographic operations, ensuring plaintext keys never leave your secure vault.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Stop leaking keys in config files. Learn how to use the Vault Transit engine to offload cryptographic operations, ensuring plaintext keys never leave your secure vault.
Learn how to replace vulnerable password-based SSH access with Ed25519 public key authentication to secure your remote servers and streamline management.
Learn how to use OpenSSL to extract public key fingerprints for TLS pinning, mitigating MitM attacks by bypassing the system trust store.
A technical guide on choosing between AES-GCM and AES-CBC in OpenSSL, comparing AEAD security, hardware performance, and the risks of nonce reuse versus padding oracles.
Key Exchange Negotiation Failure During the initial SSH handshake, the client and server must agree on a mutually supported key exchange (KEX) algorithm. If the intersection of the supported algorithm lists is empty, the connection is aborted before authentication occurs. This behavior is common when connecting modern OpenSSH clients (version 8.8 or 9.0+) to
TLS Certificate Chain Validation in Zig The std.crypto.tls implementation in the Zig standard library handles the TLS handshake but does not include built-in RFC-5280 certificate chain verification. By default, the client accepts any presented certificate unless a custom validation callback is provided by the developer. When building a secure client, there i