blocks|key|668854|text|仅仅比较公众的IP是不够的。你只会让少数几个国家和有一个外部IP的公司投一票。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|668855|最好的方法是使用多种方法来检测假选票。|668856|如果用户登录，|668857|与登录绑定，如果不设置浏览器cookie，则绑定|unordered-list-item|668858|。|668859|不允许以非常快的速度从同一个IP+%2B相同-cookie中投票.如果来自同一个IP的选票以非常快的速度来，|668860|就会加一个卡。|668861|668862|为了匿名IP，只需做IP的密钥散列。|668863|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|H|7|X|8|@]|9|@]|A|$]]|$1|K|3|L|5|H|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|Z|8|@]|9|@]|A|$]]|$1|O|3|J|5|6|7|10|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|11|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|S|$]]

Comparing public IPs wont be enough. You will let only one vote from few countries and from corporates, which have one external IPs.

Best way to do it is use multiple methods to detect the fake votes. 

<ul>
<li>If users are logged in vote is tied to login, </li>
<li>if not set a browser cookie. </li>
<li>Do not allow votes from same IP + same-cookie at very fast rate. </li>
<li>Put a captcha if votes are coming at very fast rate from same IP.</li>
</ul>

For anonymizing the IP just make keyed hash of IP.

blocks|key|668823|text|我在过去做过一些投票功能，我使用IP作为唯一的约束。缺点是人们可以共享公共知识产权。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|668824|你可以把cookie和IP结合起来。这一切都取决于投票的重要性，如果人们是否作弊。|668825|我会使用一个简单的MD5哈希。|668826|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I've done some voting functionaly in the past and I've used IP as the unique constraint. The drawback is that people may share public IP. 

You could combine cookie and IP. It all depends of the importance of the voting if people are cheating or not.

I would use a simple MD5 hash.

blocks|key|690303|text|为了防止公共网站中的投票操作，比较IP地址是否就足够了？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|690304|690305|这将阻止许多支持NAT网关的人投票，一旦有人在网关后面投票。你真的想这么做吗？|690306|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|H|8|@]|9|@]|A|$]]|$1|C|3|D|5|6|7|I|8|@]|9|@]|A|$]]|$1|E|3|-4|5|6|7|J|8|@]|9|@]|A|$]]]|F|$]]

<blockquote>
 To prevent voting manipulation in a public web site, is it enough to compare IP addresses for equality?
</blockquote>

That will prevent lots of people who are behind NAT gateways from voting, once someone behind the gateway has voted. Do you really want to do that?

blocks|key|2809367|text|我会对IP地址进行散列，在每次民意测验中，我都会保留一份已投票的人的哈希列表，以及一份答案列表。不要把答案和散列相结合。那样的话，你的哈希效果到底有多好也不重要。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2809368|除了存储ip之外，您还可以考虑在客户机上放置一个cookie，例如，对于那些连接到不同的网络，从而能够从不同的ip上进行投票的人来说，比如笔记本电脑。|2809369|也要意识到，允许ip投票一次，就是允许NAT或代理背后的人投票一次。这可能意味着整个公司只能投票一次。你需要考虑一下你是否可以接受。|2809370|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I would hash the IP adress, and for each poll, keep a list of hashes of people who have voted, and a list of answers. Don't couple the answer with the hash. That way, it doesn't even matter how good your hashing is exactly.

You could consider in addition to storing the ip, also putting a cookie on the client, for people with laptops for instance, who connect to different networks and thereby are able to vote from different ip's.

Also realize that by allowing an ip to vote once, you're allowing people behind a NAT or proxy to vote once. That could mean that an entire company can only vote once. You need to consider whether that's acceptable to you.

blocks|key|668906|text|我认为防止投票欺诈的最好方法是使用认证方法。但是你需要一些没有认证的公共网站。嗯?|type|unstyled|depth|inlineStyleRanges|entityRanges|data|668907|那么您的想法是正确的，IP验证，将IP地址保存在一个带有散列的表中。|668908|//+Verify+in+the+table+if+this+IP+visitor+exists

+...
$ip+=+$_SERVER['REMOTE_ADDRESS'];

if+($ip+==+$row['ip'])+{

+++if+(sha1($ip)+===+'$row[shaip]')+{
+++++++echo+"You+have+already+give+a+vote.";
+++}
}+
else+{

+++//+Start+the+process+here
+++$ip+=+"$_SERVER['REMOTE_ADDRESS']";
+++$shaip+=+sha1($ip);+//+the+own+IP

+++//+Here+inputs+IP+and+HASH+in+your+table
+++mysql_query("INSERT+...");

+++//+Here+fetch+the+data+to+comparison
+++mysql_query("SELECT+...");
}|code-block|syntax|javascript|668909|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I think the best way to prevent vote fraud is with authentication method. But you need something for Public website without authentication. Yeah?

Then your thoughts is right, IP verification, save the IP address in one table with the hash.

<pre><code>// Verify in the table if this IP visitor exists

 ...
$ip = $_SERVER['REMOTE_ADDRESS'];

if ($ip == $row['ip']) {

 if (sha1($ip) === '$row[shaip]') {
 echo "You have already give a vote.";
 }
} 
else {

 // Start the process here
 $ip = "$_SERVER['REMOTE_ADDRESS']";
 $shaip = sha1($ip); // the own IP

 // Here inputs IP and HASH in your table
 mysql_query("INSERT ...");

 // Here fetch the data to comparison
 mysql_query("SELECT ...");
}
</code></pre>

blocks|key|690441|text|显然，用公开盐进行哈希并不能使IP保持私密性(只有40亿人，很容易用暴力来逆转)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|690442|因此，您需要保持salt的私密性，这时它基本上变成了一个关键。因此，您可以使用对称加密，比如AES也是一个秘密密钥，而不是散列。而且不会有明显的差别。但是，对自己(拥有密钥的人)来说，逆转加密比逆转哈希稍微容易一些。|690443|您可以做的另一件事是使用比32位短得多的散列。这样就可以防止IP的逆转，仅仅因为有许多IP匹配一个散列。但当然，每一次投票也会阻止其他一些IP。这是否可以接受取决于您的用例。|690444|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Hashing with a public salt obviously doesn't keep the IPs private(there are only 4 billion of them, easy to brute-force reverse).

So you need to keep the salt private, at which point it basically becomes a key. So instead of hashing you could use a symmetric encryption like AES is a secret key too. And there would be no significant difference. Except that it's slightly easier for yourself(who has the key) to reverse the encryption than to reverse the hash.

One other thing you could do is use a hash significantly shorter than 32 bits. That way you prevent reversing of an IP simply because there are many IPs matching a single hash. But of course each vote then blocks a number of other IPs too. If that's acceptable depends on your use-case.

To fight vote fraud, I need to store IP addresses in my database but I want to make them anonymous. The only information that I need is if two addresses are the same ... I think.

<ul>
<li>To prevent voting manipulation in a public web site, is it enough to compare IP addresses for equality?</li>
<li>For transparency/verification purposes, I'd like to allow users to download the voting data. Therefore, I have to hash the IP addresses in a suitable way. Which hash method do you suggest and why?</li>
</ul>

How can I store an IP address for comparison without revealing it?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

为了打击投票欺诈，我需要在我的数据库中存储IP地址，但我想让它们匿名。我唯一需要的信息是如果两个地址相同..。我认为。为了防止公共网站中的投票操作，为了平等起见，比较IP地址是否足够？为了透明/验证目的，我想允许用户下载投票数据。因此，我必须以适当的方式对IP地址进行散列。您建议采用哪种哈希方法?为什么？

问我如何存储IP地址以供比较而不暴露它？
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我如何存储IP地址以供比较而不暴露它？EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我如何存储IP地址以供比较而不暴露它？
EN