PacketStation/scripts

scripts

backup/

The nightly pg_dump backup with its systemd timer, and the restore script, for the native VMs (no Docker). See backup/README.md and docs/DEPLOY.md, "Backups on a VM" and "Restore on a VM". The VM install kit itself (units, launcher, install and upgrade) is in deploy/vm/.

Export-PescoCaBundle.ps1

Run on a domain-joined PC. Exports every unexpired PESCO CA certificate from the Windows stores to one PEM bundle and copies it to docker-1 with scp (default target ~/packetstation/test/ca/pesco-ca.pem). Use -Remote for another path and -NoCopy to only write the file. It warns on SHA-1 signed certificates; see docs/DEPLOY.md.

Request-VsqlServerCertificate.ps1

Run elevated on the SQL Server host behind vsql, in Windows PowerShell 5.1 or PowerShell 7. Requests a TLS certificate from PESCO-PSYLOCKE-CA with certreq the way SQL Server requires it (legacy Microsoft RSA SChannel Cryptographic Provider, KeySpec AT_KEYEXCHANGE, RSA 2048, SHA-256, Server Authentication, key usage 0xA0, SANs vsql.pesco.com, vsql and the host FQDN and short name). It installs it and validates it before anything is bound. The validation checks the key provider and KeySpec from the certificate's own key property, the key size, the signature, the dates, the EKU, and the SAN DNS names as whole names. It grants only the selected instances' service accounts read on the private key, then binds the thumbprint and reads it back.

• -WhatIf previews every step and changes nothing. -Confirm asks before each change. Declining enrollment or a key grant cancels the run with nothing bound (exit code 2).
• -CerFile continues a request that was pending. -Thumbprint binds a certificate already installed. -Instances limits the run (DEV, MSSQLSERVER). -RestartInstances restarts them and starts SQL Server Agent again if it ran. The running dependents are written to dependents-<service>.json before the stop and the file is removed once they run again, so after a failed restart the next restart of that service starts them too.
• Each deployment writes a new deploy-<time>.json in C:\ProgramData\PacketStation\vsql-cert with the values it replaced. Instances already bound to the thumbprint are left alone and get no snapshot, so a rerun never hides the useful one. A pending request writes request-<time>.json with its request id. A registry value that cannot be read stops the run; only a value confirmed absent is saved as absent.
• -Rollback restores the newest snapshot not yet rolled back, each instance on its own, verified by reading back, and records it in rollback-<time>.json with which restarts succeeded. A snapshot stays open while an instance is unrestored or its restart failed, so -Rollback -RestartInstances again retries exactly those. -Snapshot picks another. Failures are listed and the run exits with an error.
• Instances are read from the value names of Instance Names\SQL, so a name starting with PS (for example PSREPORTING) is found.

Tests: scripts/tests/Request-VsqlServerCertificate.Tests.ps1 (Pester 5) fakes the host (instances, services, registry, machine store, certreq, icacls) and uses real throwaway certificates in Cert:\CurrentUser\My. Run it on both PowerShell versions:

Install-Module Pester -RequiredVersion 5.7.1 -Scope CurrentUser -SkipPublisherCheck
Invoke-Pester -Path scripts	ests -Output Detailed

The run procedure is in docs/DEPLOY.md, under the vsql known issue. Gitea issue 5 tracks the switch to VISUAL_ENCRYPT=yes.