AGWA / AGWA/git-crypt

Committing file in .gitattributes but with no added keys commits plaintext

Offen
#123 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
C++
Sterne
9.9k
Forks
544
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

With version 0.5.0, I clone a repo with a `.gitattributes` file that matches a missing file. The repo has no added PGP keys. Even if I run `git-crypt init`, if I add the previous missing file and commit it, it's committed in plain text (which can be checked by cloning this local repo again somewhere else and running `git-crypt status -e` there).

I know that committing such file is pointless without added keys, but to avoid incidents, git-crypt could check before committing a supposedly encrypted file that it won't be encrypted, and produce an error.

Thank you!

Beitragsleitfaden

Beitragsleitfaden öffnen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.