47ng / 47ng/prisma-field-encryption

Issue related to decrypt

Offen
#12 3 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
TypeScript
Sterne
306
Forks
40
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

The library is used to encrypt data, but the basic structure is in the form of "v1.aesgcm256.~~~~~.~~~~~~~". However, if the content is decoded using online decrypt in the "AES-256-GCM" mode, the content cannot be confirmed normally.

We are concerned about problems that may arise in the future. For example, although the library has been developed and later converted, the encryption method has been changed, but the encryption of existing encrypted data cannot be broken.

First of all, if the current encryption is normal, the data will come out in a structure called "v1.aesgcm256.~~~~~.~~~~~~~", is that correct?

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

The issue is about the encryption format 'v1.aesgcm256' and decryption failures with external tools. Start by examining the encryption/decryption logic in the library, likely in the middleware or core encryption module. Check the format parsing and AES-GCM implementation. Verify against existing encrypted data to understand the expected output structure and why external decryption fails.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
typescript
Bereich
databases, security
Issue-Typ
Bug
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Veraltet
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
25/100

Neue Issues direkt in Ihr Postfach

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