From 481193a1d67f6cc149aef28c1e81e56dc3c6d195 Mon Sep 17 00:00:00 2001 From: Jeff Alyanak Date: Fri, 17 May 2019 14:27:11 -0400 Subject: [PATCH] Fixed Broken section Links --- README.md | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/README.md b/README.md index 24b9688..c6674d1 100644 --- a/README.md +++ b/README.md @@ -7,24 +7,24 @@ _Beware! BitBetter does janky IL magic to rewrite the bitwarden core dll and ins Credit to https://github.com/h44z/BitBetter and https://github.com/jakeswenson/BitBetter # Table of Contents -1. [Getting Started](#gettingstarted) - + [Pre-requisites](#prereq) - + [Setting up BitBetter](#setup) - + [Building BitBetter](#building) - + [Generating Signed Licenses](#generating) -2. [FAQ](#faq) +1. [Getting Started](#getting-started) + + [Pre-requisites](#pre-requisites) + + [Setting up BitBetter](#setting-up-bitbetter) + + [Building BitBetter](#building-bitbetter) + + [Generating Signed Licenses](#generating-signed-licenses) +2. [FAQ](#faq-questions-you-might-have-) 3. [Footnotes](#footnotes) -# Getting Started +# Getting Started The following instructions are for unix-based systems (Linux, BSD, macOS), it is possible to use a Windows systems assuming you are able to enable and install [WSL](https://docs.microsoft.com/en-us/windows/wsl/install-win10). -## Pre-requisites +## Pre-requisites Aside from docker, which you also need for Bitwarden, BitBetter requires the following: * openssl (probably already installed on most Linux or WSL systems) * dotnet-sdk-2.1 (install instructions can be found [here](https://dotnet.microsoft.com/download/linux-package-manager/rhel/sdk-2.1.604)) -## Setting up BitBetter +## Setting up BitBetter With your pre-requisites installed, begin the installation of BitBetter by downloading it through Github or using the git command: ```bash @@ -51,7 +51,7 @@ openssl pkcs12 -export -out cert.pfx -inkey key.pem -in cert.pem -passin pass:te Note that the password here must be `test`.[1](#f1) -## Building BitBetter +## Building BitBetter Now that you've generated your own own self-signed certificate, you can run the main `BitBetter/build.sh` script to generate a modified version of the `bitwarden/api` docker image. @@ -72,7 +72,7 @@ You'll also want to edit the `/path/to/bwdata/scripts/run.sh` file. In the `func You can now start or restart Bitwarden as normal and the modified api will be used. It is now ready to accept self-issued licenses. -## Generating Signed Licenses +## Generating Signed Licenses There is a tool included in the directory `src/licenseGen/` that will generate new individual and organization licenses. These licenses will be accepted by the modified Bitwarden because they will be signed by the certificate you generated in earlier steps. @@ -93,7 +93,7 @@ You'll need to get a user's GUID in order to generate an invididual li 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! -# FAQ: Questions (you might have?) +# FAQ: Questions (you might have?) I'll work on updates in the next couple weeks, right now, I just wanted something to start with. @@ -111,7 +111,7 @@ To be clear i'm totally happy to give them my money. Offer a perpetual server li I'm still in the testing/evaluating phase. If I am hosting the server/data, let me license the server, period. How many licenses does one user need to have... -# Footnotes +# Footnotes 1 If you wish to change this you'll need to change the value that `src/licenseGen/Program.cs` uses for it's `GenerateUserLicense` and `GenerateOrgLicense` calls, but this is really unnecessary as this certificate does not represent any type of security issue.