Show the SHA-256 checksum in the "registered for" field (optionally)

[serrq]

Please agree to the following

• I have searched existing issues for duplicates
• I agree to follow this project's Code of Conduct

Summary

Licenses must having a unique "name" to be able to recognize them when one owns more than one.

Motivation

If I buy three Android licenses I will have the necessity to give them a name in order to have three different entries in my password manager.

How to give a "name" to a license? Pretty simple:

License Key: abcdefghilmno

SHA-256: d1bf0c925ec44e073f18df0d70857be56578f43f6c150f119e931e85a3ae5cb4

The SHA-256 is the license name.

This avoid to put your license key in the "username" (transparent) field in the password manager and to show my email in the "registered for" field in the app.

Considered Alternatives

No response

Anything else?

No response

[serrq]

Of course, this feature should be performed on all the platforms.

[SailReal]

I do not really understand why a user should have three different license keys.
The email address is exactly the identification field we want.

[serrq]

It is pretty simple: I don't want show my personal info (my email address) in "registered for" field.

Privacy.

[serrq]

I do not really understand why a user should have three different license keys.

A user could having three Android smartphones, for example.

One of these, it is of his (not owned) company.

[SailReal]

It is pretty simple: I don't want show my personal info (my email address) in "registered for" field.

Privacy.

If we have a pin-protected application, as suggested in #574, I see no huge problem in seeing the email address when going to an application's settings page.

I do not really understand why a user should have three different license keys.

A user could having three Android smartphones, for example.

One of these, it is of his (not owned) company.

Using your personal password manager in a business context is strongly discouraged, as is using your business password manager for personal use, so I still struggle to see this point.

[serrq]

Using your personal password manager

There is no "personal" password manager approach.

Instead there are two databases and different devices.

Database only for personal use.

Database only for business use.

Your pin not solve the case to anonymize that field. Your app however attempts to link an account to encrypted data.

Just to be clear, my data have to be encrypted even without an account.

I don't see any reason because in "registered for" has to find info linked to me. Even if those data are mine.

It seems like you intentionally wanted to leave a way to connect the data to me.

If it is for the license, you can simply turn it into hash (after the user has provided a valid license string).