@@ -38,14 +38,13 @@ To authenticate and sign transactions with a Ledger, Bridge must be serving
38over HTTPS on localhost. This requires self-signed certificates. You can do
38over HTTPS on localhost. This requires self-signed certificates. You can do
39this via the following:
39this via the following:
41−* Install [mkcert](https://github.com/FiloSottile/mkcert)
41+* Install [mkcert](https://github.com/FiloSottile/mkcert), and [nss](https://github.com/nss-dev/nss) if you're using Firefox
42* Install a local certificate authority via `mkcert -install`
42* Install a local certificate authority via `mkcert -install`
43* In your `bridge` directory, generate a certificate valid for localhost via
43* In your `bridge` directory, generate a certificate valid for localhost via
44 `mkcert localhost`. This will produce two files: `localhost.pem`, the local
44 `mkcert localhost`. This will produce two files: `localhost.pem`, the local
45 certificate, and `localhost-key.pem`, its corresponding private key.
45 certificate, and `localhost-key.pem`, its corresponding private key.
46* Run `python bridge-https.py`
46* Run `python bridge-https.py`
47−
47+* Navigate to https://localhost:4443 in a web browser
48−Bridge will serve to localhost over HTTPS on port 4443
50### Useful Accounts
49### Useful Accounts