19 lines
1.4 KiB
Markdown
19 lines
1.4 KiB
Markdown
A Chappaai host is a gateway to accessing other hosts. It is a safeguard against admin error.
|
|
|
|
## Etymology
|
|
Chappaai hosts are named to follow the non-English naming of the Stargate network by the other denizens of the galaxy.
|
|
|
|
They are the first line of defense against administrative error -- similar to the way that [Stargate Command](https://stargate.fandom.com/wiki/Stargate_Command) was for Earth. They prevent admins from being locked out of correcting their changes and are connected to everything in the ecosystem. They also control DNS, which allows a sort of subliminal control of the entire ecosystem. This prevents infiltration by infections (similar to Goauld) and in fact can be the extinction of any DNS-enabled malware in the ecosystem by sinkholing the Command-and-Control.
|
|
|
|
## Capacity and Components
|
|
A Chappaai host needs minimal CPU or memory.
|
|
|
|
## Hosted Services and Entities
|
|
Chappaai should host a Pihole installation and [SSH](../Services/SSH.md). It should be linked by NAT to an obscure port to the outside world.
|
|
|
|
## Connections
|
|
Any host should be able to connect to a Chappaai with SSH and X11, and it should be able to dial to any service provider.
|
|
|
|
## Additional Reference
|
|
Chappaai hosts should be deployed alongside any Hypervisor. They can be as simple as a Pi-hole with SSH access, and they should be allowed to receive SSH connections from a non-tcp/22/ssh port.
|