使用用于显示“安全”的指南发票

发布于 2024-10-02 18:36:21 字数 404 浏览 3 评论 0原文

我创建了一个学生管理网站(武术学校)。其中包括给学生开具发票。目前,我的用户可以做到这一点的唯一方法是打印发票并将其交给学生。我想为学生创建一种在线查看发票的方式。

我一直在考虑为学生使用 GUID,并将其用作发票查询字符串的参数。 (http://thesite.com/invoice.php?guid=E3D3D122-5AB6-4405-96EC-7C0579710813)

发票将是只读页面,并且不允许访问其余部分该网站。所以我不担心数据包嗅探(我不相信咖啡店里的一些嗅探流量是一个问题,如果他们只能访问随机的学生发票)。

我担心有人能够猜测或获得一组特定的发票(即竞争对手的所有发票)。

我觉得我要么是疯狂地考虑它,要么这是相对论的标准实践。我只是不确定是哪一个。 SO 是一个很好的健全性检查。

谢谢

I've created a web site for student management (martial arts schools). Which includes invoicing students. Currently the only way my users can do this is by printing the invoices and handing them to the students. I'd like to create a way for the students to go to their invoice online.

I've been considering using GUIDs for the students, and using that as the parameter for the query string to the invoice. (http://thesite.com/invoice.php?guid=E3D3D122-5AB6-4405-96EC-7C0579710813)

The invoice would be a read-only page, and allow no access to the rest of the site. So I'm not to worried about packet sniffing (I don't believe some sniffing traffic in a coffee shop is a concern, if all they have access to is a random student invoice).

I am worried about someone being able to guess, or get to a specific set of invoices (i.e. all the invoices of a competitor).

I feel like I'm either crazy for considering it, or it's a relativity standard practice. I'm just not sure which. And SO is a great sanity check.

Thanks

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

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

发布评论

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

评论(2

冬天旳寂寞 2024-10-09 18:36:21

这实际上是一个良好、安全的过程;当然,您会失去 URL 的可读性,但如果这不是一个大问题,那么这是一个很好的解决方案。这当然是猜不透的。

作为一项附加的安全措施,您可能需要记录发票访问情况。

That's actually a good, secure process; you lose the readability of the URL, of course, but if that's not much of a concern, that's a good solution. It's certainly not guessable.

As an added security measure, you might want to put in place logging of invoice accesses.

山人契 2024-10-09 18:36:21

我会更进一步,将发票存储为受密码保护的 pdf 文档。这实现了几件事:

  • 文档是只读的(网页也是,但最终用户更难更改 pdf),
  • 学生还需要密码才能访问文档中的信息,因此即使有人猜到了 GUID( 检索到文档,他们也无法看到文档中的内容(他们将无法看到金额、所属学校等)
  • 或者更有可能收到邮寄给他们的快捷方式/网址),那么即使 从网络缓存中,没有密码就无法查看
  • 它是打印机友好的
  • 它应该可以在其他设备上轻松查看

I would take it one step further and store the invoice as a password protected pdf document. This achieves several things:

  • the document is read only (a web page is too, but a pdf is harder for the end user to change)
  • the student also requires a password to access the info in the document so even if someone guesses the GUID (or more likely gets a shortcut/url mailed to them) then they can't see what is in the document (they won't be able to see the amount, which school it is for, etc.)
  • even if the document is retrieved from a web cache it isn't viewable without the password
  • it is printer friendly
  • it should be easily viewable on other devices
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文