summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/getting-started.md5
-rw-r--r--docs/guide/troubleshooting.md8
2 files changed, 11 insertions, 2 deletions
diff --git a/docs/getting-started.md b/docs/getting-started.md
index d91eb046..692c1e67 100644
--- a/docs/getting-started.md
+++ b/docs/getting-started.md
@@ -27,16 +27,17 @@ The base locations of user folders are:
Contents of the user folder includes:
-- `settings.json`: Advanced settings (see [settings](#settings))
- `lastrun`: A text file containing the directory of the last BinaryNinja binary path -- very useful for plugins to resolve the install locations in non-default settings or on linux.
+- `license.dat`: License file
- `plugins/`: Folder containing all manually installed user plugins
- `repositories/`: Folder containing files and plugins managed by the [Plugin Manager API](https://api.binary.ninja/binaryninja.pluginmanager-module.html)
+- `settings.json`: Advanced settings (see [settings](#settings))
![license popup >](/images/license-popup.png "License Popup")
## License
-When you first run Binary Ninja, it will prompt you for your license key. You should have received your license key via email after your purchase. If not, please contact [support].
+When you first run Binary Ninja, it will prompt you for your license key. You should have received your license key via email after your purchase. If not, please contact [support](https://binary.ninja/support).
Once the license key is installed, you can change it, back it up, or otherwise inspect it simply by looking inside the base of the user folder for `license.dat`.
diff --git a/docs/guide/troubleshooting.md b/docs/guide/troubleshooting.md
index a640d47e..c1b3a910 100644
--- a/docs/guide/troubleshooting.md
+++ b/docs/guide/troubleshooting.md
@@ -72,6 +72,14 @@ $ ln -s libssl.so libssl.so.1.0.0
$ ln -s libcrypto.so libcrypto.so.1.0.0
```
+Alternatively, you might need to (as root):
+
+```
+apt-get install libssl-dev
+ln -s /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.2 /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
+ln -s /usr/lib/x86_64-linux-gnu/libssl.so.1.0.2 /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
+```
+
### Gentoo
One Gentoo user [reported][issue672] a failed SSL certificate when trying to update. The solution was to copy over `/etc/ssl/certs/ca-certificates.crt` from another Linux distribution.