Do I include certification keys in github?

[modest garden]

Yeah i mean its pretty straightforward question, do i include public/private rsa keys when dealing with spring auth?
if so is it possible to automate the generation somehow?

[plush orbit]

<@&1004656351647117403> please have a look, thanks.

Here is an AI assisted attempt to answer your question 🤖. Maybe it helps! In any case, a human is on the way 👍. To continue talking to the AI, you can use </chatgpt:1108714622413963314>.

No, you should not include certification keys in your GitHub repository as it can pose a security risk. It is recommended to store your keys securely and not expose them in a public repository.

When dealing with Spring authentication, you can generate public/private RSA keys using tools like OpenSSL or Keytool. These keys should be stored securely and only the public key should be shared with the necessary parties for authentication purposes.

It is possible to automate the generation of keys using scripts or tools that can generate RSA keys programmatically. However, it is important to ensure that the generated keys are stored securely and not exposed in any way that could compromise security.

[modest garden]

so do i just share public key?

[arctic chasm]

you have a public and a private key

also known as the "you can share this" and the "you should not share this" keys

so

[knotty sentinel]

private or public repo's ?

[modest garden]

Public repo

[worn marlin]

A private key has no business in any repo...

[modest garden]

So the contributor will have to generate its own? Isnt there any way to automate this

[knotty sentinel]

Do it in a way like Ethan said higher. If u do need to share a key, u can share it outside the repo, like for example as cli or from a git excluded source

[modest garden]

wdym

[knotty sentinel]

use a sharable key , or find a way to pass it along without it going on the hub. CLI option of load it from a source that's excluded ( gitignore for example ) from the git