Skip to content

feat: expose sqlite headers metadata (WPB-27928) - #5169

Open
yamilmedina wants to merge 2 commits into
security-providers-info-screenfrom
feat/add-sqlcipherinfo
Open

feat: expose sqlite headers metadata (WPB-27928)#5169
yamilmedina wants to merge 2 commits into
security-providers-info-screenfrom
feat/add-sqlcipherinfo

Conversation

@yamilmedina

@yamilmedina yamilmedina commented Aug 12, 2026

Copy link
Copy Markdown
Collaborator

https://wearezeta.atlassian.net/browse/WPB-27928


PR Submission Checklist for internal contributors

  • The PR Title

    • conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
    • contains a reference JIRA issue number like SQPIT-764
    • answers the question: If merged, this PR will: ... ³
  • The PR Description

    • is free of optional paragraphs and you have filled the relevant parts to the best of your ability

What's new in this PR?

  • Expose from kalium the SQLite headers for sqlcipher version usage. Available only through debug builds
  • Allows custom builds to override the should encrypt db config for db, so it is available for debug builds as well.
    • The current behavior in the predefined flavors is maintained, so the flag is kept disabled.

Dependencies (Optional)

A PR following in Kalium

How to Test

Open in a debug build, the debug screen and security providers item, to see the metadata listed.

Attachments (Optional)

Screenshot 2026-08-12 at 15 36 26

PR Post Submission Checklist for internal contributors (Optional)

  • Wire's Github Workflow has automatically linked the PR to a JIRA issue

PR Post Merge Checklist for internal contributors

  • If any soft of configuration variable was introduced by this PR, it has been added to the relevant documents and the CI jobs have been updated.

References
  1. https://sparkbox.com/foundry/semantic_commit_messages
  2. https://github.com/wireapp/.github#usage
  3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants