Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Encrypted check breaks storing of PGP keys #38

Open
hiasr opened this issue Jan 8, 2025 · 0 comments
Open

Encrypted check breaks storing of PGP keys #38

hiasr opened this issue Jan 8, 2025 · 0 comments

Comments

@hiasr
Copy link

hiasr commented Jan 8, 2025

The current implementation only encrypts a field when it is not armored, due to the is_encrypted check.
This causes difficult to debug issues when trying to store keys, which also start with ----BEGIN but of course are not encrypted.

What is the reason for this check? I would think the most logical behaviour is to always encrypt, if users want to encrypt the data themselves they should use the normal Django fields.
Would be willing to contribute but wanted to know if this change is wanted!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant