Store information encrypted #13
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When dealing with personal data, as if often the case for signups, it would sometimes be useful to be able to store this in an encrypted form, perhaps by GPG encrypting relevant entries to a setup of recipient keys.
This is a hot topic as encrypted storage is indeed useful. But we include this data during the generation of publiccode.eu for example, so its container would have to be able to decrypt the data.
One rather complicated way to circumvent symmetric encryption or locally stored GPG private keys would be to generate a second database with striped data. So all data which is not displayed publicly will be censored and saved in clear text while the one containing sensitive or non-public data will be encrypted.
I would like to question this issue, and especially the prio:high label. If data is used somewhere, it must be accessible, and if it is not used, we should not store it to start with.
True, I think the same. It would also be complicated for the publiccode.eu website to access this data.
Will remove the high prio. Thanks for raising the issue!
Related to #25, I suggest to close this issue.
I agree, thanks for flagging