Built to hold sensitive documentation.
Operating procedures, infrastructure diagrams, incident reports: Lore assumes your documents are confidential, and that nobody should see what they are not allowed to see.
Already in place
Protected accounts
Passwords hashed with Argon2id, rate-limited sign-in attempts followed by a lockout, server-side sessions that everyone can end remotely, no default password.
Audit log
Sign-ins, failed sign-ins, password and email changes, invitations, roles, members and organization settings are recorded. Browsing it in the administration comes in v0.1, along with document operations.
Checked on every change
Automated tests check accounts, sessions and who may call the administration API, on every code change.
Your data stays with you
Lore runs in your infrastructure, with PostgreSQL. Nothing is sent outside without your decision.
Open, auditable code
The code is public. Your security teams can review it, test it and build it themselves.
Coming in the next releases
These protections arrive with the features they protect.
Permissions first v0.1
Permissions will be enforced in every query, before sorting and pagination. Not a title, not an excerpt, not a result count will give away an inaccessible document.
Truly unfindable v0.1
A document you cannot access will return the same response as a document that does not exist. Even its existence will stay confidential.
Untrusted files kept apart v0.1
Text extraction will run in a separate process: a booby-trapped file will not be able to bring the application down.
An assistant under control v0.3
Off by default. Once enabled, it will only receive the passages the person asking is allowed to read.
Report a vulnerability
Never report a vulnerability in a public issue. Use GitHub’s private vulnerability reporting: we acknowledge your report, keep you informed and credit you if you wish.
For a useful report
- A description of the problem and its impact.
- The steps to reproduce it, or a proof of concept.
- The affected version or commit.