Page MenuHomePhabricator

Add `cluster.addresses` and require membership before accepting cluster authentication tokens
ClosedPublic

Authored by epriestley on Jan 2 2015, 9:13 PM.
Tags
None
Referenced Files
F15414563: D11159.id26800.diff
Thu, Mar 20, 1:12 AM
F15407679: D11159.id.diff
Tue, Mar 18, 6:56 PM
F15401312: D11159.diff
Mar 17 2025, 4:57 PM
F15378109: D11159.id26778.diff
Mar 13 2025, 12:53 PM
Unknown Object (File)
Feb 21 2025, 1:52 PM
Unknown Object (File)
Feb 21 2025, 10:45 AM
Unknown Object (File)
Feb 11 2025, 5:49 PM
Unknown Object (File)
Feb 8 2025, 12:41 AM
Subscribers

Details

Summary

Ref T2783. Ref T6706.

  • Add cluster.addresses. This is a whitelist of CIDR blocks which define cluster hosts.
  • When we recieve a request that has a cluster-based authentication token, require the cluster to be configured and require the remote address to be a cluster member before we accept it.
    • This provides a general layer of security for these mechanisms.
    • In particular, it means they do not work by default on unconfigured hosts.
  • When cluster addresses are configured, and we receive a request to an address not on the list, reject it.
    • This provides a general layer of security for getting the Ops side of cluster configuration correct.
    • If cluster nodes have public IPs and are listening on them, we'll reject requests.
    • Basically, this means that any requests which bypass the LB get rejected.
Test Plan
  • With addresses not configured, tried to make requests; rejected for using a cluster auth mechanism.
  • With addresses configred wrong, tried to make requests; rejected for sending from (or to) an address outside of the cluster.
  • With addresses configured correctly, made valid requests.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable