Lenticular Cloud/Account: Difference between revisions

From Milliways
No edit summary
No edit summary
Line 30: Line 30:
<h1>Services</h1>
<h1>Services</h1>


<h2>Enable/Disable</h2>
Each service can be activated and deactivated.
Each service can be activated and deactivated.
<h2>Master-Password</h2>
The master password is the password mean to login into https://account.milliways.info.
If this checkbox is enabled, this password is also valid for the current service.
<h2>Password</h2>
Each password has a Id to identify the hashed passwords.


Normally you can have multiple "password" for each service, this can be uses as access tokens for different devices.
Normally you can have multiple "password" for each service, this can be uses as access tokens for different devices.


Eg. generate a random password(`$ pwgen 32` ), add it to the service, copy it to the device, access
Eg. generate a random password(`$ pwgen 32` ), add it to the service, copy it to the device, access

Revision as of 05:34, 29 August 2018

Registration

Each registration has to be approved by an admin to prevent spamers and unexpected access to the infrastructure.

Stored Data

Passwords

The passwords are stored as salted sha-512, what is a good enought secure hash. Moderner hashes like bcrypt,.. are not supported by Open-LDAP.

Alt Email

This is an email to contact the user outside this cloud system. Also password reset will be send there, so please take care about the security of this given email-address.

Public GPG/PGP key

The GPG key is used to secure the communication to the alt-email. So a password reset is much easier for an administrator, because he can verify the user by a additional factor.

Last modified

The last modification of the user account

Account Created

Date when the account is created.

Services

Enable/Disable

Each service can be activated and deactivated.

Master-Password

The master password is the password mean to login into https://account.milliways.info. If this checkbox is enabled, this password is also valid for the current service.

Password

Each password has a Id to identify the hashed passwords.

Normally you can have multiple "password" for each service, this can be uses as access tokens for different devices.

Eg. generate a random password(`$ pwgen 32` ), add it to the service, copy it to the device, access