If your private key is not encrypted (and you don't want it to be), you can comment out `ssl_password_file /etc/ssl/private/keys.pass;` in `nginx/nginx.conf`.
If your private key is not encrypted (and you don't want it to be), you can comment out `ssl_password_file /etc/ssl/private/keys.pass;` in `nginx/nginx.conf`.
## Add a new language (locale)
1. Add a new language in PwnDoc -> Data -> Custom Data -> Languages. Set `locale` to short string (country/language code is ideal).
2. Add the `locale` to list `LOCALES` in file `config.py`.
## Add a section to audit
1. Add a new custom section in: PwnDoc -> Data -> Custom Data -> Custom Sections. Sections can be in any order.
2. Add to section to a audit type in: PwnDoc -> Data -> Custom Data -> Audit Types -> List of Audit Type (button edit) -> _Audit type name_ (e.g. _Example audit type_) -> Sections. Then save.
3. Add a field to custom section: PwnDoc -> Data -> Custom Data -> Custom Fields -> Select view -> Audit Section -> Select Section. Then add any components, for example Editor. Add some label and click button add.
4. Add output to docx template. Templating is described elsewhere in the wiki.
This applies only to new audits.
## Add authors to label work assignments
To make it easier to identify which analyst should work on which Finding, we're using the field _Vulnerability type_ to indicate it. You can add your own authors (or any different label for Findings) in PwnDoc UI: PwnDoc -> Data -> Custom Data -> Custom Fields -> Vulnerability types. They are locale specific, so if your analyst knows multiple languages, you need to add him several times.
Vulnerability types are not used anywhere in Import Automator - it's just and visual indicator in PwnDoc UI.
