Thanks this helped a ton. A thing ive noticed with the hashicorp documentation is that theyll give you all the steps on how do do something without really explaining why or what. This helped clear up a lot of my confusion.
/ is a FORWARD slash. The backslash is used for CPM/DOS/Windows. Internet services that originated on Unix or similar system use forward slashes or just the slash.
Awesome video, thanks!! One thing you missed, though, is that you should not add the intermediate cert as trusted. You should always advise your webserver to send the whole chain. If that's done right, the browser or any other client will be able to validate the whole chain only with the RootCA
The clipboard API is disabled by the browser due to the page not being served over HTTPS. Why use a VM and not a CT that would save you a lot of resources. Why not use hostnames rather than IPs as these should be bound if your local DNS is working correctly something like vault.local should work. Any good cert parser will fully ignore the formating enter spaces etc get ignored. No need to format it with sed. Cool video. A little bit messy
You certainly can. As long as theres no cyclical dependency in which vault requires the cert to operate but you cant get the cert because vault won’t operate. This isn’t an issue to my knowledge.
Thanks this helped a ton. A thing ive noticed with the hashicorp documentation is that theyll give you all the steps on how do do something without really explaining why or what. This helped clear up a lot of my confusion.
/ is a FORWARD slash. The backslash is used for CPM/DOS/Windows. Internet services that originated on Unix or similar system use forward slashes or just the slash.
I have a feeling I mixed up my slashes in this video, didn’t I?
Awesome video, thanks!! One thing you missed, though, is that you should not add the intermediate cert as trusted. You should always advise your webserver to send the whole chain. If that's done right, the browser or any other client will be able to validate the whole chain only with the RootCA
The clipboard API is disabled by the browser due to the page not being served over HTTPS.
Why use a VM and not a CT that would save you a lot of resources.
Why not use hostnames rather than IPs as these should be bound if your local DNS is working correctly something like vault.local should work.
Any good cert parser will fully ignore the formating enter spaces etc get ignored. No need to format it with sed.
Cool video. A little bit messy
Very messy and overcomplicated
After all the steps are done, can you go back and generate a cert for Vault? I have vault running in a docker on Unraid
You certainly can. As long as theres no cyclical dependency in which vault requires the cert to operate but you cant get the cert because vault won’t operate. This isn’t an issue to my knowledge.
What game is that in the background?
Shadow of Mordor?
Final Fantasy 16
I think you have such subscribers but you are not getting any views
Nice shirt
🥳