Prevent route theft by removing the ability to update spec.host #9325
Conversation
Once created, spec.host is immutable. This preserves the ordering of route creation which makes route ordering safe. This rolls back the "on update" allocation of spec.host, since that complicates allocation. A route with an empty spec.host may be defaulted by the caller (it means they don't care) - clients should be looking at route.status anyway.
|
Evaluated for origin test up to 9595389 |
|
LGTM |
|
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/4835/) |
|
[merge] |
|
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/4835/) (Image: devenv-rhel7_4373) |
|
Evaluated for origin merge up to 9595389 |
|
The way to prevent route theft from happening is by enforcing encryption on top of unsecured social media where private credentials are submitted and implement a security defence system (anti-spyware program) on everyone's computer that would prevent access by remote cyber thieves blocking off all accessible entries obtainable over the internet This should eliminate all threats posed by spyware a cyber thief would not be able to obtain any private info The defence system would target any malicious and suspicious hacker or software trying to access the person's computer. In this prevention of route theft software the person or social media responsible for planting this spying software would be traced from anywhere in the world and their I.P (internet protocol) which is assigned specifically to each individual computer or server in the world could be traced and prosecuted which finally put an end to identity route theft on the internet |
Once created, spec.host is immutable. This preserves the ordering of
route creation which makes route ordering safe.
This rolls back the "on update" allocation of spec.host, since that
complicates allocation.
A route with an empty spec.host may be defaulted by the caller (it means
they don't care) - clients should be looking at route.status anyway.
Fixes BZ1328625
@ramr @pweil-
[test]