ggershinsky commented on issue #18240: URL: https://github.com/apache/iceberg/issues/18240#issuecomment-6110824634
> why not just just re-create the KEK, unwrap the manifest list with the old KEK and rewrap using the new KEK and then just store the encrypted version of KEK in the table metadata ... The way i understand the proposal is we are just doing the metadata re-encryption, what is the rationale behind that ! The owners of tables that were encrypted a few years ago, are sometimes required to replace the old encryption keys. Like most things in security, this is a "defense in depth" approach, not a silver bullet solution. We add a layer of protection that replaces all old keys (just in case they are compromised/leaked/overused) - but only where this is feasible, meaning all keys except for data file keys (since it's too expensive to re-encrypt the big parquet files). It's not perfect, but tables where this re-wrapping is done, are safer than tables were it was not done. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
