软件的安全电子邮件发送

发布于 2024-07-29 18:19:54 字数 212 浏览 1 评论 0原文

有些人通过 PayPal 购买了我的应用程序( DRM)。 我没有在应用程序中包含更新功能(坏主意)。既然有更新,我想我可以通过电子邮件向所有以前的客户发送他们可以安装的更新版本的链接。 不幸的是,这个想法太开放,无法攻击(只需复制并在论坛上发布链接),因此被拒绝。 我如何向所有购买该应用程序的人发送电子邮件,其中包含不易受到攻击的安全链接?
谢谢,艾萨克

Some people bought my application (which has no DRM) through PayPal. I didn't include update functionality inside the app (bad idea.) Now that there's a update, I thought I could email all previous customers with a link to the updated version they could install. Unfortunately, this idea is too open to attack (just copy and post link on forum) so it was rejected. How can I email everyone who bought the app with a safe link that is not so open to attack?
Thanks, Isaac

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

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

发布评论

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

评论(3

↙厌世 2024-08-05 18:19:54

也许考虑一下:

  • 将更新的包上传到您的网站/ftp。 确保安全。
  • 向每个客户发送登录页面的链接
  • 每个链接都应在查询字符串上包含一个参数 - 也许是一个 GUID,供一次性使用。
  • 要求用户输入他们的电子邮件地址,并确保它与您记录的该电子邮件地址的 GUID 相匹配。
  • 下载后,拒绝使用该电子邮件地址或 GUID 进行任何进一步的下载; 写入小型数据库(即 SQLite)
  • 如果客户需要多次下载,请让他们向您发送电子邮件。 您可以使用新的 GUID 重新向他们发送新的下载链接。 这一切都将与他们的电子邮件地址相关联,以便进行追踪。
  • 也许甚至不要强迫用户给您发送电子邮件。 重新生成新的 GUID,但将用户限制为 2 或 3 个自动生成的 GUID。
  • 您现在已经掌握了谁下载了什么以及下载了多少次的统计信息?

这种模式可以复制到您想要提供下载的所有产品以及每个不同的版本。 如果能够在所有这些情况下利用该方案,那就太好了。

Perhaps consider this:

  • Upload an updated package to your website/ftp. Secure it.
  • Send a link to a login page to each customer
  • Each link should contain a parameter on the querystring - a GUID perhaps, for one time use.
  • Ask the user to enter their email address, and ensure that it matches the GUID you have on record for that email address.
  • Once it has been downloaded, deny any more downloads with that email address or GUID; write to a small DB (i.e. SQLite)
  • If the customer needs to download it more than once, have them email you. You can resend them a new download link with a new GUID. This would be all tied to their email address for traceability.
  • Perhaps don't even force the user to email you. Regenerate a new GUID, but cap the user at 2 or 3 auto-generated GUIDs.
  • You now have stats on who downloaded what and how many times?

This pattern could be replicated to all the products you'd want to offer for download, and each different version. It'd be great to take advantage of this scheme for all those situations.

滥情哥ㄟ 2024-08-05 18:19:54

只需创建一个可以对用户进行身份验证的 Web 应用程序即可。 向您的客户发送电子邮件,以便他们可以注册到您的网站,并创建用户名/密码来下载您的应用程序。 每次有新的更新时,他们都可以进入、验证并下载。
您还可以创建仅有效一次的链接,这也由您的网络应用程序处理。

Just create a web app that can authenticate users. Send an e-mail to your clients so they can register to your website, and create a username/password to download your app. Every time there is a new update, they can just go in, authenticate and download.
You can also create links that are only valid once, this is also handled by your web app.

就是爱搞怪 2024-08-05 18:19:54

您可以使更新安装程序要求安装原始安装程序。 或者,您可以使用安装程序在安装前发送回服务器的 ID 来标记每个下载,以检查该副本之前是否已安装,以防止重新上传。 (可能想要允许一些重新安装)

You could make the update installer require that the original be installed. Or you could tag each download with an id that the installer sends back to the server before install, to check if that copy has been installed before, to prevent reuploads. (probably want to allow for a few reinstalls)

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