aboutsummaryrefslogtreecommitdiff
path: root/guix-reconfigure.sh (follow)
Commit message (Collapse)AuthorAgeFilesLines
* git mv guix-reconfigure.sh remote-guix-reconfigure.shEuAndreh2021-01-101-8/+0
|
* Remove code comments.EuAndreh2020-12-091-1/+1
|
* guix-reconfigure.sh: Delete from remote ~/sync/EuAndreh2020-12-051-1/+1
|
* guix-reconfigure.sh: Sync remotely to sync/EuAndreh2020-12-051-2/+2
|
* ci-build.sh: Remove server-specific PREFIX path of logfileEuAndreh2020-11-291-1/+1
|
* rsync the full folder to home instead of file by fileEuAndreh2020-11-161-1/+1
|
* guix-reconfigure.sh: Remove un-needed (for now) envsubst call and shrink ssh ↵EuAndreh2020-11-161-3/+4
| | | | commands
* Add base Guix configuration and start switching to itEuAndreh2020-11-161-0/+7
- remove NixOS stateVersion from .envrc; - add guix-reconfigure.sh; - add vps.scm with initial Guix system configuration; - update vps.tf to use the new "base-guix" snapshot. The "base-guix" image doesn't need a password. The "andreh" users has one, but it is configured for not requiring it when running commands as "sudo". The expected minimal steps one has to go through for privilege scalation is via the SSH private key, and accessing the VPS via SSH. Since password login is disabled and root can't login via SSH either, only the private SSH key allows access to the server. After that, the attacker will be able to run commands as root.