Introduce Versioning to Encrypted Data Format

[campeon23]

Description: Versioning encrypted data formats can significantly simplify future changes or updates to the encryption scheme. By appending a version tag to the data, it becomes more straightforward to support and distinguish between different encryption versions.

Recommendation: Implement a versioning system in the encrypted data format to easily manage and differentiate between data encrypted using different versions or schemes.

Example Fix: A simple implementation could prefix the encrypted data with a version byte or string:

const CURRENT_VERSION = "v1"

func VersionedEncrypt(data []byte, key []byte) ([]byte, error) {
    encryptedData, err := EncryptWithGCM(data, key)
    if err != nil {
        return nil, err
    }
    versionedData := append([]byte(CURRENT_VERSION), encryptedData...)
    return versionedData, nil
}

Acceptance Criteria:

Develop a versioning convention for the encrypted data format. Modify the encryption and decryption functions to handle version prefixes. Ensure backward compatibility by maintaining support for data encrypted using older versions or schemes.

Severity Level: Medium

[campeon23]

Changes made:

• Implemented a versioning convention for the encrypted data structure.
• Modified the encryption and decryption functions to accommodate and manage version prefixes.
• Made certain that there's backward compatibility for data that was encrypted following older versions or different methods.
• Adjustments made to encryption_test.go to ensure it's in line with the newly introduced versioning convention.

If there are further concerns or revisions needed related to this ticket, please feel free to reopen or raise a new ticket for specific issues.