Skip to content

Releases: michelp/pgsodium

v3.0.7

22 Nov 14:52
a8aea8e
Compare
Choose a tag to compare

What's Changed

  • Non-extension owners can label newly created tables, not just use them. by @michelp in #36
  • get keys by names and ids by @michelp in #38
  • fix: crash on macos 13.0.1 by @burmecia in #39
  • Feat/rebuild only session user objects by @michelp in #40

New Contributors

Full Changelog: v3.0.6...v3.0.7

v3.0.6

21 Oct 16:10
Compare
Choose a tag to compare
tighten event trigger conditions, disable/enable event trigger when g…

…enerating views, fix missing drop function so pgsodium can regenerate itself.

v3.0.5

18 Oct 01:32
Compare
Choose a tag to compare

More tests for 3.0.5, support for external keys in pgsodium.key table.

v3.0.4

17 Aug 21:04
ac191f6
Compare
Choose a tag to compare

Any column that can cast to text can be associated with TCE.

v3.0.3

16 Aug 19:49
Compare
Choose a tag to compare
missing sql file.

v3.0.2

08 Aug 22:27
Compare
Choose a tag to compare

Minor bug fixes.

v3.0.1

05 Aug 04:03
06e7ca4
Compare
Choose a tag to compare
Tce support for v3 (#27)

* Transparent Column Encryption support for v3

* better error messaging, insert into base table to encrypt for now.

* extensive tce refactor, lots of test cleanup, triggers now dynamically generaeted on table, not view.

* fix literal string handling for for key_id_column and add test case.

* better key column test and bug fix.

* new begin atomic sql functions.

* go back to using with syntax, make view generation distinct per table per update.

* optional nonce support for column key and row key

* cleanup if checks with coalesce

* nonce test.

* docs for TCE, some cleanup of key creation api as det is the common algorithm.

* more documentation cleanup.

v3.0.0

05 Aug 02:22
06e7ca4
Compare
Choose a tag to compare

This release is NOT b/w compatible with 2.0.2, and will only work with PostgreSQL version 14 or higher. If you wish to use pgsodium with earlier versions you must use a version in the 2.0.x line.

This release contains many changes to the security of pgsodium functions, setting the search_path for plpgsql functions, and making the extension non-relocatable. The extension can be installed into any schema (including public) but it's recommended that you install it into a schema named pgsodium.

This release provides no new libsodium related functionality, but instead provide a new Transparent Column Encryption function described in the documentation.

Release v2.0.2

13 Feb 02:03
Compare
Choose a tag to compare
test release tag.

2.0.1

17 Jan 02:47
Compare
Choose a tag to compare

2.0.1