Amazon EC2 实例 ID - 为什么要进行异或？
根据 Guy Rosen 和 < a href="http://blog.rightscale.com/2009/10/05/amazon-usage-estimates/" rel="nofollow">RightScale Amazon EC2 实例 ID 包含针对第一个和第一个的两个 XOR后半段的《Inner ID》又三人对抗各自的不变。
我知道我们不会确切地知道亚马逊这样做的原因。然而，从一般角度来看，有没有人实现或见过这种异或，为什么要实现这种异或？
唯一的目的是帮助混淆 ID 吗？
According to Guy Rosen and RightScale the Amazon EC2 instance IDs contain two XORs against the first and second half of the "Inner ID" and all three against their own constant.
I understand that we won't know exactly why Amazon does this. However, from a general perspective, has anyone implemented or seen this sort of XOR and why would this XOR be implemented?
Is the only purpose to help obfuscate the ID?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
考虑到它显然对阻止人们弄清楚它几乎没有什么作用，通过简单的二元运算符进行混淆似乎有点愚蠢。我认为罗森先生偶然发现了它的一种可能用途，我能想到的唯一另一种用途是某种形式的资源跟踪。
当然，在亚马逊的某人告诉我们之前，这一切都只是纯粹的猜测。
Obfuscation via a straightforward binary operator seems a little silly considering how little it apparently worked to prevent people from figuring it out. I would assume that Mr. Rosen stumbled across one possible use for it, the only other I can think of is some form of resource tracking.
Of course, until someone from Amazon tells us this will all be pure idle speculation.