我应该保护我的公共 GnuPG-Key 链接免受电子邮件爬虫的攻击吗?

发布于 2025-01-07 20:04:41 字数 323 浏览 2 评论 0原文

我猜我的电子邮件地址以某种方式编码在导出的公共 GnuPG-Key 中(如果我错了,请告诉我)。

如果我想在我的主页上上传我的公共 GnuPG-Key,我是否应该混淆该 GnuPG-Key 的链接? (例如使用一些 JavaScript 代码)

因为正常的模糊处理会让机器人从网站中提取模糊信息的成本(在计算时间上)变得昂贵,所以我的主要问题是:它会花费多少(在计算机时间上)从公共 GnuPG-Key 中提取电子邮件?电子邮件爬虫会这样做吗?

PS:在这个帖子中我不想讨论是否有必要花时间进行电子邮件地址混淆的问题。请想象一下,对于这篇文章,保护电子邮件地址免受爬虫攻击非常重要。

I guess my email address is somehow encoded in the exported public GnuPG-Key (Please tell me, if I'm wrong here).

If I want to upload my public GnuPG-Key on my homepage, should I obfuscate the link to this GnuPG-Key? (for example with some code of JavaScript)

Because normal obfuscation wants to make it expensive (in computation time) for a bot to extract the obfuscated information from a website, my main question is: How expensive (in computer time) would it be to extract the email from the public GnuPG-Key? Would an email crawler do this?

PS: In this thread I don't want to discuss the question whether it is necessary to spend time in email address obfuscation or not. Please imagine for this post, that email address protection against crawler is important.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

撑一把青伞 2025-01-14 20:04:41

您认为电子邮件是您的 GnuPG 公钥的一部分是正确的。从手册:

公钥由主签名密钥的公共部分组成,
从属签名和加密子密钥的公共部分,
以及一组用于将公钥与真实密钥关联起来的用户 ID
人。每件作品都有关于其自身的数据。对于一个键,这个数据
包括它的 ID、创建时间、过期时间等。
用户 ID,该数据包括其识别的真实人员的姓名,
可选评论和电子邮件地址

从已发布的密钥中获取这些数据并不是特别昂贵,是的,一些电子邮件爬虫会这样做。阅读有关此问答的一些评论(搜索“垃圾邮件”):

http://security.stackexchange.com/questions/406/how-should-i-distribute-my-public-key

以这种方式收集电子邮件的垃圾邮件发送者可能只会将他们的软件指向众多公钥服务器之一,因此您的页面可能不会受到他们的攻击。当大多数已发布的密钥已经为它们收集在一起时,为什么要抓取整个网络呢?

如果您仍然担心您的电子邮件地址落入坏人之手,那么混淆链接并不麻烦,所以为什么不呢?

You are right about the email being part of your GnuPG public key. From the manual:

A public key consists of the public portion of the master signing key,
the public portions of the subordinate signing and encryption subkeys,
and a set of user IDs used to associate the public key with a real
person. Each piece has data about itself. For a key, this data
includes its ID, when it was created, when it will expire, etc. For a
user ID, this data includes the name of the real person it identifies,
an optional comment, and an email address.

It is not particularly expensive to harvest this data from published keys, and yes, some email crawlers do so. Read some of the comments on this Q&A (search for "spam"):

http://security.stackexchange.com/questions/406/how-should-i-distribute-my-public-key

However, a spammer who intends to harvest emails this way will probably just point their software at one of the many public key servers out there, so your page is probably safe from them. Why crawl the whole web when most keys that are published are already gathered together for them?

If you are still concerned about your email address falling into the wrong hands though, it's not much trouble to obfuscate a link, so why not?

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文