We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Requiring HTTPS for non-localhost vault addresses is "too much safety" in certain valid secure network configurations.
Create a vault server somewhere, and setup both machines to be connected via a secure VPN like WireGuard.
Example vault.hcl:
vault.hcl
listener "tcp" { address = "10.13.37.100:8200" tls_disable = 1 }
HTTP traffic over the WireGuard network is encrypted and strongly authenticated, perfectly safely, yet cryptr won't allow this type of connection.
The text was updated successfully, but these errors were encountered:
I too have actually been annoyed by this. PR submitted.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
The problem
Requiring HTTPS for non-localhost vault addresses is "too much safety" in certain valid secure network configurations.
Details
Create a vault server somewhere, and setup both machines to be connected via a secure VPN like WireGuard.
Example
vault.hcl
:HTTP traffic over the WireGuard network is encrypted and strongly authenticated, perfectly safely, yet cryptr won't allow this type of connection.
The text was updated successfully, but these errors were encountered: