summaryrefslogtreecommitdiffstats
path: root/lib/puppet/rails/rails_parameter.rb
diff options
context:
space:
mode:
authorDaniel Pittman <daniel@puppetlabs.com>2011-08-04 10:49:59 -0700
committerDaniel Pittman <daniel@puppetlabs.com>2011-08-04 10:50:51 -0700
commit711344836aa1e469876fc511be14e8159e61b0b8 (patch)
treecda7fff4d06c7f3607a84b260fd71adfd9704e3b /lib/puppet/rails/rails_parameter.rb
parentb85f57cc227df16a6f0beedbd4f10befa55b9b3c (diff)
downloadpuppet-711344836aa1e469876fc511be14e8159e61b0b8.tar.gz
puppet-711344836aa1e469876fc511be14e8159e61b0b8.tar.xz
puppet-711344836aa1e469876fc511be14e8159e61b0b8.zip
(#4762) Ensure that clients on the moon can successfully connect.
Previously, we only allowed Puppet Clients at a maximum distance of somewhere between 7,494 and 14,988 kilometers from the master, depending on the variance in local conditions. While this gave us good data security against hostile clients connecting from the dark side of the moon, real world testing shows the moon folks are likely to just take over a local staging host and attack that way. So, instead, allow clients sufficient time they should be comfortable able to connect to a master from the moon. We still refuse clients further out, like Mars, since it seems unlikely that Puppet management over that distance should work. We advise the manned Mars expedition to deploy a local Puppet Master to manage infrastructure in their base, and to watch out for the martians.
Diffstat (limited to 'lib/puppet/rails/rails_parameter.rb')
0 files changed, 0 insertions, 0 deletions