1,164 karma · joined October 16, 2020
Thank you for bringing this back into my main memory. Spent so many hours playing this and completely forgot about it.
Quick search turned up a couple of sites where you can play this emulated online!
Not all MQs are the same. Some offer a plethora of options to fit your need (ack policy, replay policy, max outstanding, etc) Give NATS a look: https://nats.io/
In the old days you could look at at raw non-rendered HTML and it would be so simple that you can render it in your head.
With the advent of more sophisticated web frameworks like the one mentioned, that’s no longer the case. The site consists of MBs of scripts and templates that take a gigawatt to render.
Linked your project.
I can choose a password such as 'The name of uncle Robert's favorite movie' (i.e. something that it's easy for her, but hard for everyone else).
OR
I can call her, and say: 'Just sent you a password-protected file. The password is 'Foobar'
OR
I can include the password in the email itself (doesn't protect from an attacker but protects from mail provider snooping/indexing emails).
It doesn't make my communications NSA proof. It adds a little bit of privacy. For the specific use-case, it's more than enough.
Thank you for sharing!
I should really make sure IV/Salt are regenerated automatically after use. (there is a small print warning in the creator about reuse)
Rather than trying to explain why, I provided a reasonably reputable source with a good summary. Read it if you are curious. Or don't. No need to be bite.
Could your time-based scheme be defeated by changing the system clock on the attacker computer?
I trust everything I use to some degree. Otherwise I wouldn't use it in the first place. But the world is not black and white.
Just because I trust something enough to store secret X in it, doesn't mean I should automatically use it to store secret Y.
That would be a very sophisticated attacker. So back to my original point.
Beside. The README states pretty clearly this is 'demo' tech. Learn the trick and use it on your own. Depending on my GitHub tool for your critical secrets is not a good idea.
I'm just sharing a little hack I came up with. I hope some people add it to their toolchain (not my specific implementation, the idea in general).
And offering a bounty seemed like a fun things to do, which may also catch some shallow bugs, reward the hunter, and shame me publicly :-)
To your point, the W3C Crypto library APIs might change, and break my secrets. Unlikely but possible.
I don't know that bringing in a library makes this better: it could use features/constructs of the language that get deprecated and break.
There's other factors to consider (convenience, amount of review a given implementation has gotten, etc).
Overall, agree to disagree. Using a library has slightly different tradeoffs and I can see why you are recommending it. But I stick by my choice to depend on browser APIs.
There's other secrets I'd rather never upload to the cloud, with all the risks that entails. I have various other methods to store and backup those secrets. This tool is part of that toolkit.
Added you to the project README.
(I got a bunch of compliments for this project today, I hope you are enjoying seeing them too given we had the same idea)
- Bitcoin is hard
- Wallets come with sophisticated anonymization built-in
- Don't create the bounty wallet 20 minutes before posting on HN (if that snafu had happened today while this post was on the front page, I would have looked pretty stupid)
Great suggestion!
> not having to debate this myself
eh eh.. good luck with that...
I think the problem is that it can be used "good" and can be used "bad". Some people focus/fixate on the ways you can shoot yourself in the foot with this. Other think of the good use cases it enables.
Thank you for mentioning Argon2, I didn't know about it. https://en.wikipedia.org/wiki/Argon2
> There is no reason not to use Argon2
In this case, the reason for not using Argon2 is that it's not available: https://www.w3.org/TR/WebCryptoAPI/
> Well if this product isn't for mass-market
This is a demo for self-contained HTML encrypted secrets. Do with it what you want. Definitely not a product in the current format.
Thank you.
https://security.stackexchange.com/questions/35818/are-passw...
But I can't expect my mom or girlfriend to learn how to use it.
With PortableSecret I can communicate privately with them, without installing or learning anything new.
But before you hit that limit, your browser may kill the tab because it looks like it's using too many resources. Again hardware/browser/platform specific.
All in all, I'm glad this cannot be used as-is for pirate movies. That would have kept me from releasing it.