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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

Ask HN: What do you use for passwords on encrypted attachments

1 点作者 mtbkrdave大约 6 年前
Yes, yes, there are plenty of more-secure ways of getting files from point A to point B today, but once in a while a curmudgeonly vendor or someone&#x27;s misguidedly-heavy-handed policy push us into having to send a sensitive attachment by email.<p>So, you zip it up with a password or generate an encrypted PDF - but what to use for the password? Absent a side channel to send the password through, you have to use some shared bit of knowledge. Same applies for sending a secure ProtonMail message to a non-PM address.<p>Most recently I used the message ID of the first message in a separate email thread with the same recipient - but there&#x27;s no guarantee he still has that message or would have any clue how to get at the headers and track down the ID. I&#x27;ve used invoice numbers plus total dollar amounts on most-recent bills in the past, or strings from design files sent in cleartext previously.<p>Of course there&#x27;s always a phone call and a sufficiently-simplistic password.<p>What&#x27;s your favorite means of conveying a file password alongside the file?

2 条评论

ziddoap大约 6 年前
If I have to send it this way, any out-of-band communication is generally fine with me although I do prefer phone (out-of-band verification and no transmission over net).<p>Assuming your no side-channel requirement means no phone call available, I&#x27;d probably send with PGP. If its a pushy vendor, I&#x27;ll be pushy back (company&#x2F;position allows me to be pushy, ymmv). Worst case would be resorting to something like: &quot;Password is the invoice number from XX&#x2F;YY date and the first item code on the invoice&quot; or something sufficently complex.
krrrh大约 6 年前
<a href="https:&#x2F;&#x2F;onetimesecret.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;onetimesecret.com&#x2F;</a>