From 770dcd33f6ebc5b046a63dc867276b6b39865f8f Mon Sep 17 00:00:00 2001 From: Michiel Hazelhof Date: Sun, 12 Jan 2025 12:14:30 +0100 Subject: [PATCH] Move Manually generating Certificate & Key section in README.md for unified (#220) * Update Dockerfile See #215 and #207 * Move Manually generating Certificate & Key section in README.md See #216 --- README.md | 33 ++++++++++++++++----------------- 1 file changed, 16 insertions(+), 17 deletions(-) diff --git a/README.md b/README.md index e700898..1165535 100644 --- a/README.md +++ b/README.md @@ -14,8 +14,8 @@ Credit to https://github.com/h44z/BitBetter and https://github.com/jakeswenson/B - [Getting Started](#getting-started) - [Dependencies](#dependencies) - [Setting up BitBetter](#setting-up-bitbetter) + - [Optional: Manually generating Certificate & Key](#optional-manually-generating-certificate--key) - [Building BitBetter](#building-bitbetter) - - [Note: Manually generating Certificate & Key](#note-manually-generating-certificate--key) - [Updating Bitwarden and BitBetter](#updating-bitwarden-and-bitbetter) - [Generating Signed Licenses](#generating-signed-licenses) - [Note: Alternative Ways to Generate License](#note-alternative-ways-to-generate-license) @@ -40,6 +40,21 @@ With your dependencies installed, begin the installation of BitBetter by downloa git clone https://github.com/jakeswenson/BitBetter.git ``` +### Optional: Manually generating Certificate & Key + +If you wish to generate your self-signed cert & key manually, you can run the following commands. + +```bash +cd .keys +openssl req -x509 -newkey rsa:4096 -keyout key.pem -out cert.cert -days 36500 -outform DER -passout pass:test +openssl x509 -inform DER -in cert.cert -out cert.pem +openssl pkcs12 -export -out cert.pfx -inkey key.pem -in cert.pem -passin pass:test -passout pass:test +``` + +> Note that the password here must be `test`.[1](#f1) +--- + + ## Building BitBetter Now that you've set up your build environment, we need to specify which servers to start after the work is done. @@ -83,22 +98,6 @@ If you ran the build script, you can **simply run the license gen in interactive **The license generator will spit out a JSON-formatted license which can then be used within the Bitwarden web front-end to license your user or org!** ---- - -### Note: Manually generating Certificate & Key - -If you wish to generate your self-signed cert & key manually, you can run the following commands. -Note that you should never have to do this yourself, but can also be triggered by running the generateKeys.[sh|ps1] script. - -```bash -openssl req -x509 -newkey rsa:4096 -keyout key.pem -out cert.cert -days 36500 -outform DER -passout pass:test -openssl x509 -inform DER -in cert.cert -out cert.pem -openssl pkcs12 -export -out cert.pfx -inkey key.pem -in cert.pem -passin pass:test -passout pass:test -``` - -> Note that the password here must be `test`.[2](#f1) - - --- # FAQ: Questions you might have.