Hypergrid security and inter-grid trust
Two distinct administrations · Controlling inbound and outbound travel
Two distinct administrations
Every grid retains control of its users, services and policies. Hypergrid allows installations to communicate, not to share administrator privileges or account databases.
Controlling inbound and outbound travel
GatekeeperService supports settings such as ForeignAgentsAllowed and exceptions. UserAgentService can apply ForeignTripsAllowed and restrictions based on account level. Verify exact settings and behavior for the deployed version.
Impersonation and identifiers
A visitor must not gain resident privileges by adopting a name or identifier. Gatekeeper performs identity checks, including certain UUID collisions. Avoid manually changing UUIDs or UUIs to bypass verification.
Objects, scripts and OSSL functions
Creation, import and script permissions remain controlled by the visited grid. Sensitive OSSL functions, HTTP interactions, economy and foreign assets require appropriate policy; enabling Hypergrid is not itself a security solution.
Never expose private ports or secrets
Do not disclose SQL credentials, service keys or friendship relationship secrets. Do not expose private ROBUST or MySQL ports to fix travel. Test changes in a noncritical environment and keep backups.
Explore more Hypergrid guides
- Hypergrid installation and configuration
- Principles and architecture
- Visitor identity
- Cross-grid teleports
- Networking and ports
- Inventory and assets
- Hypergrid friends
- Troubleshooting