Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,48 @@ grand_parent: Core Areas and APIs
layout: default
---

## The Browser Profile
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there reason to make these now first items in the page? Could think for browser development the logging and building type of things would still be more important.

Copy link
Copy Markdown
Contributor Author

@nephros nephros Apr 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see what you mean. This is more a user guide vs. development documentation.
Would you be open to reorganize the Browser-related pages into e.g.

  • Browser
    • Usage and Configuration
    • Performance Testing
    • Building
    • Debugging

So it is clearer what the pages are for?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well at the moment, or even with these changes, the content here is hardly a user guide. If we wanted such for Browser, think that should go then somewhere around these https://docs.sailfishos.org/Support/Help_Articles/ - though these certificate things could be too low level there. Generally user guide should rather document what's available on the UI.

Fwiw, elsewhere this page is now referred as "browser development page" - https://docs.sailfishos.org/Reference/Core_Areas_and_APIs/Browser/

Is the motivation for adding these texts as app user (not developer) working around not having a direct UI for it?


The Sailfish OS Browser stores its profile at `${HOME}/.local/share/org.sailfishos/browser/.mozilla/`

Some of the operations for configuring this profile given in the official
Mozilla Documentation are supported.

Such as:

### Adding TLS Certificates

User-specific CA or Client TLS certificates can be added to the user-specific certificate store:

For a CA Certificate:

```
export CA_NAME="My Root Authority"
export PEM=/path/to/ca.pem
export MOZILLA_PROFILE="${HOME}/.local/share/org.sailfishos/browser/.mozilla/"
certutil -A -n "$CA_NAME" -t "TC,," -d "${MOZILLA_PROFILE} -i ${PEM}
```

For a Client Certificate:

Usually, client certificates come in a `.pfx` file.
To be able to import it into the Browser, they must first be converted into PEM format.
Refer to the OpenSSL documentation on how to do the conversion.

Once you have the certificate in PEM format, import it as:
```
export CRT_NAME="My Client Cert"
export PEM=/path/to/client.pem
export MOZILLA_PROFILE="${HOME}/.local/share/org.sailfishos/browser/.mozilla/"
certutil -A -n "$CRT_NAME" -t "Pu,," -d "${MOZILLA_PROFILE} -i ${PEM}
```

Note the differences in the parameter to the `-t` option!

The `certutil` utility is provided by the `nss-tools` package.

**Note:** in Sailfish OS releases prior to version 4.x, the Browser profile was stored in ` -d ${HOME}/.mozilla/mozembed/`
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this relevant anymore?


## Console API messages

- EMBED_CONSOLE=1 environment variable be used to log messages to terminal / journal
Expand Down
Loading