Meta Issue: Control over private key

[martinheidegger]

For the scientists we work with, the personal identification is very important.
(Who created the data?)

The DAT desktop automatically uses private-/public-keys to create new DATs. This data can be used to clearly identify the creator of the data.

./app/actions/dat-middleware.js#L137
→ dat-node/lib/storage.js#L42
→ dat-storage/index.js#L14
→ dat-secret-storage/index.js#L6

Nobody notices the automatic creation of that key and its importance!

There are several things that would help to make this clearer to the user:

1. Show which private key is used for a dat.
2. Let the user enter a new private key when creating a dat.
3. Let the user select private keys from a list of private keys when creating a dat.

[dkastl]

This sounds good! Actually there is quite a lot happening auto-magically, that a normal user even wouldn't think of. Making this topic public/private keys more understandable will also make users aware, that this exists.