Hi Bruno,
Apologies for the delay; covid paid me a visit recently and took me away
from this discussion for a bit.
I'm fine with adding specific examples to help flesh out the questions we
want to think about while writing/reviewing KIPs, but IMO it's important to
emphasize that they are not
Hi Chris,
Thanks for the clarifications!
I am in favor to formulate the questions more concretely, like:
Does the KIP access the file system or execute code on the machine
running Kafka or one of its components?
Does the KIP introduce new components that need to be secured separately?
Hi Luke and Bruno,
Thanks for taking a look! Happy to provide some examples here to clarify
the points, and if they seem useful enough, we can also add them to the
template.
> Does it make Kafka or any of its components (brokers, clients, Kafka
Connect, Kafka Streams, Mirror Maker 2, etc.) less
Hi Chris,
Thank you for the proposal!
Could you add some examples to each of your points?
I think that would make it easier to discussion them.
Best,
Bruno
On 12.01.23 03:15, Luke Chen wrote:
Hi Chris,
I like this idea.
Thanks for raising this!
One question to the template bullet:
• Does
Hi Chris,
I like this idea.
Thanks for raising this!
One question to the template bullet:
• Does it make Kafka or any of its components more difficult to run in a
fully-secured fashion?
I don't quite understand what it means. Could you elaborate on it?
Thank you.
Luke
On Wed, Jan 11, 2023 at
Hi all,
I'd like to propose augmenting the KIP template with a "Security
Implications" section. Similar to the recently-added "test plan" section,
the purpose here is to draw explicit attention to the security impact of
the changes in the KIP during the design and discussion phase. On top of
