The git-secrets from benammann

git-secrets's Issues

description tbd

creating the initial config results in an error

implement private / public key encoding

may be more secure than AES ?

docs for git secrets set secret <key> <value> is outdated

old syntax

git-secrets set secret <secretKey> --value <plainValue>: INSECURE: Uses the value directly from the --value parameter

new syntax

git-secrets set secret <secretKey> <secretValue>

rework global secret names and fix lower case issue

allow to change encryption secret on the fly

there should be a command to change the encryption secret on the fly

# changes the encryption secret for all contexts (if not explicitly set in a custom context, see example below)
git secrets set global-secret <newSecretName>

# changes the encryption secret for a specific context
git secrets set global-secret <newSecretName> -c <contextName>

automatically check for a new release

to discuss: automatically check for a new release every week when executing a command.

CLI Descriptions

descriptions and wordings need to be finalized

add docker container ditribution

due #13 the use of a docker container should be quite simple since we do not need to mount the global .git-secrets.yaml

add personalized values like git config values (email, name)

would be a cool feature to personalize the rendered files by git config values

custom inheritence

currently every context inherits from the default context. This should be customizeable using the following config entries

{
  "context": {
    "local": {
      "root": true,
      ...
    },
    "prod": {
      "parent": "local",
      ...
    }
  }
}

branding and documentation

scan for plain passwords in git hook

# scan in staged files
git secrets scan

# scan in all files added to the git repository (auto excludes git ignores)
git secrets scan -a

# scan and print each scanned filepath
git secrets scan -v

Note: when scanning there should be used all available / accessable contexts. If there is no access to context there should be a warning and it's secrets are skipped

implement scan command
skip non-accessable contexts
add documentation

allow to use password managers from gcp / azure / aws as data source

Make sure the encryption is secure

add add some more documentation how it is done

Alias Context

In case you want to be the default context more expressive you should be able to add an alias name to every context

package managers support

we need some more package managers to not force people to install brew on their machines.

curl
go install

Write Config functions failure on missing json structure

add files to render
missing secrets entry on empty context

secure global secret writing

pass plain value via --stdin
otherwise read interactive
update docs

rework cli merge args

New Syntax should be:

export SECRET_1=secretValue
export SECRET_2=secretValue2

gs decode <secretName> --secret globalSecretName=$(SECRET_1) --secret globalSecretName1=$(SECRET_2)

custom render targets

i want to have custom render targets like

# render target env or k8s-secrets using default context
git secrets render env
git secrets render k8s-secrets

# render target k8s-secrets using prod context 
git secrets render k8s-secrets -c prod

# add file to render
git secrets add file <fileIn> <fileOut> -t <myTargetName>

config would look like this

{
// optionally allows to overwrite which context to use. should be overwriteable by -c <contextName>
"useContext": "prod",
"files": [...]
}
````

# Encode a secret and add it to the config (interactive)
git-secrets set secret mySecretKey

# Encode a secret and add it to the config (via --value)
git-secrets set secret mySecretKey --value <plainValue>

# Set a config entry
git-secrets set config myConfigKey myConfigValue

# Set a encoder secret (interactive)
git-secrets set encoderSecret mySecretKey

# Set a encoder secret via --value
git-secrets set encoderSecret mySecretKey --value <plainValue>

# Get a encoder secret
git-secret get encoderSecret mySecretKey

# Get a secret and decode it
git-secrets get secret mySecretKey

# Get a config entry
git-secrets get config myConfigKey

# Add context
git-secrets add context myContextName

# Add a file to render
git-secrets add file <fileIn> <fileOut>

benammann / git-secrets Goto Github PK

git-secrets's Introduction

git-secrets's People

Contributors

Stargazers

Watchers

Forkers

git-secrets's Issues

Recommend Projects

Recommend Topics

Recommend Org