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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

Decrypt all authorization tokens on macOS without user authentication

37 点作者 apas超过 8 年前

5 条评论

AdamJacobMuller超过 8 年前
Very cool project and definitely a cool find.<p>Interestingly though, I do get a security dialog when this happens. There is an &quot;always allow&quot; option there, so perhaps I just never clicked that in the past.
yladiz超过 8 年前
Although I think the claim is a little misleading as I was presented a security dialog box when I ran the command in the script -- &quot;security find-generic-password -ws &#x27;iCloud&#x27; | awk {&#x27;print $1&#x27;}&quot; -- I do think that the idea of &quot;always allowing&quot; access to some important part of your security is a broken model. They should at most allow for a short period of time in which the access is granted, after which the access is revoked, kind of like sudo. When I was presented with &quot;Always Allow&quot;, &quot;Deny&quot; and &quot;Allow&quot; as my options, I can easily see how this could happen to someone who just clicks &quot;Always Allow&quot; because in their head they think, &quot;Not this shit again, go away.&quot;
grzm超过 8 年前
Is this zero-day? Was any of this submitted to Apple prior to release on github?
评论 #12887493 未加载
leblancfg超过 8 年前
At first glance, this seems irresponsible from the part of the author. Contact Apple first and let them know, only release your repo if you don&#x27;t get an answer, and make sure to let the world know in your README.md.<p>The engineers at Apple are just as human as you are.
评论 #12887606 未加载
mfrager超过 8 年前
Ouch! This looks really bad. If&#x2F;when Apple fixes this it may require all 3rd-party software that accesses the keychain to be updated. However that&#x27;s not for sure. We will have to wait and see.