Revision as of 09:54, 28 November 2023

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.

Last modified

The last modification of the user account

Account Created

Date when the account is created.

Login Password

The login password is the password mean to login into https://account.milliways.info.

It is also possible to use this password for application with legacy username / password login.

App Token

Each token is able to get access to one or many services.

The tokens are auto generated and can only be seen once.

@@ Line 9: / Line 9: @@
 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.
-<h2>Alt Email</h2>
-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.
-<h2>Public GPG/PGP key</h2>
-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.
 <h2>Last modified</h2>
@@ Line 28: / Line 18: @@
 Date when the account is created.
-<h1>Services</h1>
+<h2>Login Password</h2>
-<h2>Enable/Disable</h2>
-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.
+The login 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>
+It is also possible to use this password for application with legacy username / password login.
-Each password has a Id to identify the hashed passwords.
+<h2>App Token</h2>
-Normally you can have multiple "password" for each service, this can be uses as access tokens for different devices.
+Each token is able to get access to one or many services.
-Eg. generate a random password(`$ pwgen 32` ), add it to the service, copy it to the device, access
+The tokens are auto generated and can only be seen once.