tags: documentation design

The Secrets Cockpit

Sure!:-)

This is a UI which enables free account management using the Secret Management Style.

-> The Code on Github.

Account types

As we all know the concept of an account and we could associate the purpose as quite the same as such account, we will use the word account here. This way a key is for accesssing an account. One specific key will have an id to be externally identifiable. Because the key is the essential part to decrypt and have access to whatever the account should be used for - we distinguish the account types in the way how we handle the keys.

1. Unsafe Keys
2. Floating Keys

The discrimination of those key types is merely for security considerations and important to the Secrets Cockpit for how the keys are generated and if they are allowed to be stored - from the perspective of any secret-management-service no such discrimination exists.

To counter potential confusion about the wordings:

• Key = Secret Key = Private Key
• Id = Public Key

Unsafe Keys

These are keys which are generated on the Browser and often stored in LocalStorage. These are called "unsafe" as everyone having access to your Browser Profile may read the LocalStorage and thus might read these keys. That means the "Unsafe Keys" are similarily safe like any other kind of Access Token - however they are permanent and would have their associated SecretSpace as any other key.

Floating Keys

There are keys to never be stored anywhere. They are generated out of a seedphrase provided by the user and the user must rely on their memory for the retrieval.They also should be strong, very strong. As soon as either the seedphrase or the key is stored somewhere, as same as when the seedphrase is weak - the key should be considered "unsafe" anyways.

Such a key as derived from a strong seedphrase may be used for a Master SecretSpace which is storing other "Unsafe Keys" for mobility.

Aliases

For convenience we have introduced the feature to provide an alias for specific Ids. A Key has the same unique Id anywhere. On top of that you may speficy any arbitrary human readable String for your Account to easily identify it.

(Key -> Id) -> Alias

Outside of the specific instance of the Secret Cockpit these aliases are not known.

Features v0.1

• Define URL to specific secret-manager service to be used
• Section to choose specific input method
• Use input for pasting Unsafe Keys
• Use password input to generate Floating Keys
• Retrieve and inspect SecretSpaces
• Edit Secrets
• Add Secrets
• Delete Secrets
• Add foreign Subspace
• Delete foreign Subspace
• Copy Secrets
• Store Secrets in secretSpace
• Store Unsafe Keys in localStorage
• Store Unsafe Keys in secretSpace
• Store shared Secrets
• Share Secrets
• Use Aliases for Ids
• QR-Code Import
• QR-Code Export
• messagebox for user-feedback
• detect and import stored unsafe keys
• use QR-display and QR-scan on every input field

Features v0.2

• Keylogger Protection
• Data Manager for synchronizing whole local State

Ideas

• Create Secrets Backup File (connect to data-manager)