gyptazy (@gyptazy@gyptazy.ch)

gyptazy

@gyptazy@gyptazy.ch

Believer in the power of open-source & community-driven innovation.

Former AS20621 NetOp that loves FreeBSD & illumos. Currently mostly in DevOps & developing (Python, Rust). Contributes to #Ansible & #GradenLinux. Evaluating and production usage of #RISCV hardware/software.

Projects:
* BoxyBSD.com - A free VM hosting service to provide some value back to the community.
* manpageblog.org - A static blog generator in manpage design.
* QualvoSec - A security patch management tool.

Blog: ✔ https://gyptazy.ch
GitHub: ✔ https://github.com/gyptazy
X: https://twitter.com/gyptazy

0 ★ 0 ↺

in reply to »

gyptazy » 2024-04-22
@gyptazy@gyptazy.ch

@kta@hostux.social @BoxyBSD@bsd.cafe

see also the FAQ https://boxybsd.com/faq/

It’s running on resource leftovers in my personal infrastructure. VMs may run in QEMU (Linux) or bhyve (FreeBSD).

The process is automated:
- copy template (basic OS install with an RFC1918 address)
- start vm
- replace IP, hostname, remove provisioning ssh key, set password
- poweroff
- adjust networking vswitch etc for the vm in hypervisor
- start vm

Even providing the images, you would not have the possibility to verify if this image is really being used. But you can of course audit from the inside and validate all files/checksums based against your own image.