Skip to content

Secrets guidelines #40

@MarkoSagadin

Description

@MarkoSagadin

Context

"Secrets" is an umbrella term for various confidential documents/files, such as:

  • WiFi passwords
  • Login credentials
  • Bootloader keys
  • SSh keys
  • etc.

Currently we lack clear guidelines that would tell developers how to handle such secrets in their repositories.

The purpose of this issue is to provide place for discussion about this topic and to define a set of clear guidelines on how to handle secrets.

Required steps / Implementation details

  • Research existing good practices related to handling confidential information.
  • Write down a clear list of rules what is not allowed to be checked into the git and what should be handled elsewhere.
  • Provide enough info and resources so that developers will have enough knowledge to recognize the possibly problematic security situation and seek help.

Definition of Done

Section in guidelines is written and reviewed.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions