7 Commits (8a2b8ec3e5d491134c0aaa07531b31b9b49f5561)

Author	SHA1	Message	Date
Zsolt Parragi	8a2b8ec3e5	Access method renaming and conditions (#231) ... * Renamed pg_tde -> pg_tde_basic * The "fork" extension is only visible when it's actally built * Update sysbench tests to use pg_tde_basic	1 year ago
Zsolt Parragi	2a4f0d876d	Renamed master key to principal key (#228) ... This commit contains lots of changes, but it's just a repeated execution of find <...> -exec sed <...>, so everything should work as before.	1 year ago
Zsolt Parragi	c4b549dfda	Updating CI scripts after recent changes (#129) ... This commit removes outdated keyring configuration code, and adds vault support to all runners. Also contains fixes to the vault and file providers.	2 years ago
Muhammad Usama	210c95cf00	Framework for multi-tenancy support (#121) ... * Introducing catalog table for managing key providers This commit introduces a user catalog table, percona_tde.pg_tde_key_provider, within the percona_tde schema, as part of the pg_tde extension. The purpose of this table is to store essential provider information. The catalog accommodates various key providers, present and future, utilizing a JSON type options field to capture provider-specific details. To facilitate the creation of key providers, the commit introduces new SQL interfaces: - pg_tde_add_key_provider(provider_type VARCHAR(10), provider_name VARCHAR(128), options JSON) - pg_tde_add_key_provider_file(provider_name VARCHAR(128), file_path TEXT) - pg_tde_add_key_provider_vault_v2(provider_name VARCHAR(128), vault_token TEXT, vault_url TEXT, vault_mount_path TEXT, vault_ca_path TEXT) Additionally, the commit implements the C interface for catalog interaction, detailed in the 'tde_keyring.h' file. These changes lay the foundation for implementing multi-tenancy in pg_tde by eliminating the necessity of a 'keyring.json' file for configuring a cluster-wide key provider. With this enhancement, each database can have its dedicated key provider, added via SQL interface, removing the need for DBA intervention in TDE setup." * Establishing a Framework for Master Key and Shared Cache Management Up until now, pg_tde relied on a hard-coded master key name, primarily for proof-of-concept purposes. This commit introduces a more robust infrastructure for configuring the master key and managing a dynamic shared memory-based master-key cache to enhance accessibility. For user interaction, a new SQL interface is provided: - pg_tde_set_master_key(master_key_name VARCHAR(255), provider_name VARCHAR(255)); This interface enables users to set a master key for a specific database and make further enhancements toward implementing the multi-tenancy. In addition to the public SQL interface, the commit optimizes the internal master-key API. It introduces straightforward Get and Set functions, handling locking, retrieval, caching, and seamlessly assigning a master key for a database. The commit also introduces a unified internal interface for requesting and utilizing shared memory, contributing to a more cohesive and efficient master key and cache management system. * Revamping the Keyring API Interface and Integrating Master Key This commit unifies the master-key and key-provider modules with the core of pg_tde, marking a significant evolution in the architecture. As part of this integration, the keyring API undergoes substantial changes to enhance flexibility and remove unnecessary components such as the key cache. As a result of the keyring refactoring, the file keyring is also rewritten, offering a template for implementing additional key providers for the extension. The modifications make the keyring API more pluggable, streamlining interactions and paving the way for future enhancements. * An Interface for Informing the Shared Memory Manager about Lock Requirements This commit addresses PostgreSQL core's requirement for upfront information regarding the number of locks the extension needs. Given the connection between locks and the shared memory interface, a new callback routine is introduced. This routine allows modules to specify the number of locks they require. In addition to this functionality, the commit includes code cleanups and adjustments to nomenclature for improved clarity and consistency. * Adjusting test cases * Extension Initialization and Cleanup Mechanism This commit enhances the extension by adding a new mechanism to facilitate cleanup or setup procedures when the extension is installed in a database. The core addition is a function "pg_tde_extension_initialize" invoked upon executing the database's 'CREATE EXTENSION' command. The commit introduces a callback registration mechanism to streamline future development and ensure extensibility. This enables any module to specify a callback function (registered using on_ext_install() ) to be invoked during extension creation. As of this commit, the callback functionality is explicitly utilized by the master key module to handle the cleanup of the master key information file. This file might persist in the database directory if the extension had been previously deleted in the same database. This enhancement paves the way for a more modular and maintainable extension architecture, allowing individual modules to manage their specific setup and cleanup tasks seamlessly." * Adjusting Vault-V2 key provider to use new keyring architecture	2 years ago
Zsolt Parragi	b9cc6db669	Use a custom prefix instead of a hardcoded serverid for keys (#79) ... With this change, key names no longer contain the hardcoded serverid, but instead use a user specifiable and optional prefix. With default settings the prefix is empty, and we generate key names in the format of "<name>-<version>". With a non empty prefix set, the format changes to "<prefix>-<name>-<version>". The test suite is also modified, so that the existing TAP test uses a custom prefix, and the SQL tests use an empty prefix, to test both cases.	2 years ago
Zsolt Parragi	946fd903d2	Fixing SSL warning after server restart ... This commit disables padding for the fork file encryption to fix the above warning, and also contains related test / logging improvements. The meson test runner is also restricted to one process to workaround issues where multiple processes write the same keyring data file, resulting in randomly failing test executions.	2 years ago
Zsolt Parragi	4c95782aa3	Encrypt fork files with master key and improve tests ... Fork file encryption was missing from the previous pull requests, resulting in the server not initializing the keyring on normal executions, and because of this, missing if the keyring configuration wasn't specified at all. Fixes #46	2 years ago