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
After to clone and go build I ran:
go build
mkdir tls openssl req -x509 -newkey rsa:4096 -keyout tls/key.pem -out tls/cert.pem -days 365 In this command I added the PEM pass phrase
mkdir tls
openssl req -x509 -newkey rsa:4096 -keyout tls/key.pem -out tls/cert.pem -days 365
PEM pass phrase
$ docker run -it -v (pwd)/:/app golang:1.13 bash root@9e73b18f1a60:/app# go build root@9e73b18f1a60:/app# UPSTREAM='http://172.18.0.2' ADDR=':3000' KEY_FILE='tls/key.pem' CERT_FILE='tls/cert.pem' ./vulcain INFO[0000] Vulcain started addr=":3000" protocol=https FATA[0000] tls: failed to parse private key
I think is because vulcain does not know the phrase key
vulcain
The text was updated successfully, but these errors were encountered:
Yes passphrases aren't supported yet!
Sorry, something went wrong.
Hi,
I found one post about this issue https://medium.com/@prateeknischal25/using-encrypted-private-keys-with-golang-server-379919955854
If I have time I will try to backport their solution in vulcain.
Laurent
if you are making self signed certificates for a demo project, then you can use -nodes option while making CA certificate then it won't throw error:
openssl req -x509 -newkey rsa:4096 -days 365 -nodes -keyout ca-key.pem -out ca-cert.pem
No branches or pull requests
After to clone and
go build
I ran:mkdir tls
openssl req -x509 -newkey rsa:4096 -keyout tls/key.pem -out tls/cert.pem -days 365
In this command I added the
PEM pass phrase
I think is because
vulcain
does not know the phrase keyThe text was updated successfully, but these errors were encountered: