Design a secure method to receive secret keys

[yuvipanda]

Description

Sometimes, we need to receive secret info (like OAuth keys!) from community champions / university IT to finish setting up our infrastructure. This needs to be encrypted both at rest and in transit.

Value / benefit

• We can receive secrets in a secret fashion
• We should receive it in a way that allows anyone from the 2i2c team to decrypt it, and isn't tied to anyone in particular

Implementation details

No response

Tasks to complete

• Choose what kinds of transfer options we want to officially recommend
• Work out a process for each and document it

Updates

No response

[choldgraf]

A few options that @yuvipanda recently gave to the team at U. Toronto, and we might consider re-using as "officially recommended" options:

• keybase.io
• age encrypted with a key that we publish in a public space (Yuvi sent https://github.com/yuvipanda.keys). Once encrypted, the encrypted text can be sent via the support chat.
• GPG key (see one blog post for info on how to do this

I feel like the first two options are the most reasonable, though both of them we shouldn't expect a Community Representative to have any background with and we should write documentation to step people through each.

[damianavila]

I feel like the first two options are the most reasonable, though both of them we shouldn't expect a Community Representative to have any background with and we should write documentation to step people through each.

Maybe just the first option is sort of reasonable?

[yuvipanda]

2i2c-org/docs#164 and #1698 add support for age so we can be given secret credentials. This doesn't mean we can't have other setups in the future, but this at least gives us one secure method that is not a single point of failure.

[sgibson91]

I feel like the first two options are the most reasonable, though both of them we shouldn't expect a Community Representative to have any background with and we should write documentation to step people through each.

Maybe just the first option is sort of reasonable?

+1'ing keybase.io as well, since I already use it