mirror of
https://github.com/scylladb/scylladb.git
synced 2026-06-03 21:47:10 +00:00
f8156702de
~2076 files used "Copyright (C) YYYY-present ScyllaDB" while ~88 files used "Copyright (C) YYYY ScyllaDB". This inconsistency leads to unnecessary code review discussions and gradual spread of the less common format. Standardize all ScyllaDB copyright headers to use -present. Fixes SCYLLADB-1984 Closes scylladb/scylladb#29876
38 lines
1.2 KiB
C++
38 lines
1.2 KiB
C++
/*
|
|
* Copyright (C) 2022-present ScyllaDB
|
|
*
|
|
*/
|
|
|
|
/*
|
|
* SPDX-License-Identifier: LicenseRef-ScyllaDB-Source-Available-1.1
|
|
*/
|
|
|
|
#pragma once
|
|
|
|
#include "encryption.hh"
|
|
#include "system_key.hh"
|
|
|
|
namespace encryption {
|
|
|
|
class kms_key_provider_factory : public key_provider_factory {
|
|
public:
|
|
shared_ptr<key_provider> get_provider(encryption_context&, const options&) override;
|
|
};
|
|
|
|
/**
|
|
* As it stands today, given system_key api (gives keys), and
|
|
* what it is used for (config encryption), we cannot provide
|
|
* a KMS system key. This is because:
|
|
*
|
|
* a.) KMS does not allow us to store a named object (key) in a secure(ish) way.
|
|
* We can encrypt/decrypt and create one-off keys for local usage, which are
|
|
* encoded in their own ID (see kms_host), but having a unique key from
|
|
* a "path" is not possible. Esp. due to key rotation, encrypted data preamble
|
|
* etc. We could keep the encrypted key material in a local file, then decrypt
|
|
* it using a named key on startup, but given b.) it is dubious if this is useful.
|
|
* b.) System keys are only used for config encryption. The authentication config for
|
|
* AWS/KMS access is typically one of the things that should be encrypted. Thus
|
|
* we would create a big chicken and egg problem here.
|
|
*/
|
|
}
|