As a user I can clearly see, which parts of an resource are encrypted and which are not

Q1. What is the problem that you are trying to solve?
Users normally are not aware of data security. They think, if they use a secure password-software, everything is encrypted. So they would enter risky data in not encrypted fields.

Q2 - Who is impacted?
Every user who did not read the manual or the source code carefully.

Q3 - Why is it important and/or urgent?
Secret data could be exposed when it is stored in de DB. For example a URI containing a secret.

Q4 - What is your proposed solution? (optional)

  • As with the description it is already possible one can choose to encrypt other fields (except the name),
  • or: put an Icon in front of ever field showing encryption-state,
  • or: encrypt all field per default (except the name)
  • and update the user manual, denoting which fields are encrypted and how to store sensitive data correctly.

Q5. Community support
People can vote for this idea to show traction:

  • :ok_woman: Must have: this is critical for me to have this
  • :raising_hand_woman: Should have: this is important for me to have this
  • :tipping_hand_woman: Could have: this could be nice to have
  • :no_good_woman: Won’t have: we should not schedule this (explain why)

0 voters