TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

new iOS IAP hack (no jailbreak required)

2 点作者 bignoggins将近 13 年前

1 comment

stevenwei将近 13 年前
Isn't this only an issue if your app is submitting receipt validation requests directly from the device to Apple's validation server? E.g.<p><pre><code> device -&#62; itunes.apple.com/verifyReceipt </code></pre> I thought the best practices for receipt validation involved having your app submit the receipt to your own server first, and then performing the receipt validation with Apple on the server side. E.g.<p><pre><code> device -&#62; yourownserver.com -&#62; itunes.apple.com/verifyReceipt </code></pre> In which case, even if someone man-in-the-middle's apple.com on their device, it doesn't affect the receipt validation that you perform server side. Or am I misunderstanding something and the hack is occurring at a lower level than that?