| Commit message (Collapse) | Author |
|---|
|
|
|
Saving hashed passwords should be relatively safe, as long as the hashing
algorithm isn't flawed. Considering, that we use yescrypt with higher
than average parameters ('jFT' instead of 'j9T'), we should be safe for
now.
|
|
|
|
This reverts commit 5a137ce8b8f4b1dcfee03d001938c0fa25df842f.
|
|
resolve conflicts with target branch
|
|
The passwords will be stored in a specific password file, which because it
isn't part of this repository is secure.
Refs: #9
|
|
The names of the settings in the GitHub repository are outdated, this
commit changes the setting name to the real ones.
|
|
I changed the valid ssh-host-keys from both rsa and ed25519 to
only ed25519 and moved them to `/srv/ssh` to make them persistent.
In addition to that, I also increased the rounds for the ed25519 key to
1000.
This fixes the ssh-host-key issue introduced by pull request #5.
Fixes: #5
|
|
This module generat |
