2 ms·
I'd go pretty far in that direction, were I running this service. Something along the lines of "hey, I do my best, but anything that'd significantly impact anyo
by throwanem 10y ago
I'd go pretty far in that direction, were I running this service. Something along the lines of "hey, I do my best, but anything that'd significantly impact anyone's life if it were disclosed accidentally or compromised is best stored offline, with information on how to find it being all that's actually set up to go out via my service." And maybe I wouldn't even be comfortable with that.
Actually, on further reflection, I wouldn't be comfortable running a service like this at all, for reasons amply detailed elsewhere in these comments - in short, it's a great way to paint a target on your chest for everybody from random scammers to state-level actors. I must admit I am considerably impressed by your courage in continuing to do so. Don't get me wrong - I think you must be a madman. But I can respect a very brave madman!
- StavrosK 10y agoI added something here (https://deadmansapphr.appspot.com/help/ https://deadmansapphr.appspot.com/help/), hopefully it's clear enough, but let me know if you have any feedback. I would hate to have people thinking this is secure against the NSA or anything.
- throwanem 10y agoIt's clear as far as it goes, but as I said before, I don't think it goes nearly far enough. It's not just that messages stored with your service aren't secure against state actors - messages stored with your service aren't secure against anyone with the nous to compromise the host(s) on which it runs. And I hope you'll forgive me for saying that, given that you managed to overlook trivial CSRF for a year in the application's request handling code, I'm not entirely sanguine that your host configuration is strongly secure against any, perhaps even most, non-state actors. That's not something I like saying, and I can't imagine it's all that pleasant to hear, either. I wouldn't say it at all if I did not feel it necessary, and I feel it necessary precisely because there seems to be a severe mismatch here between the gravity of any potential compromise of your service and the measures taken to prevent such a compromise from occurring. You know a lot more about the nature and scope of those measures than I do, of course, and it's possible I'm underestimating them here. I do hope that's the case. If it is, please accept my apologies for having spoken harshly where doing so was unwarranted. If it isn't, I hope you'll attend to that situation as best you can without delay. If you're not sure, then for the sake of your users, I hope you'll bring in someone with the capability to evaluate and resolve whatever security issues exist, and do so with as little delay as possible. In any case, you've (perhaps accidentally) put yourself in a position that encourages people to invest a great deal of trust in you, and it seems that many people have done so. Had I put myself in such a position, I would not be comfortable remaining in it if I could not be entirely confident I had either done everything within my power to fulfill that trust, or removed myself from that position without betraying the trust I'd found myself ultimately unable to fulfill. But that's just my own evaluation, and perhaps you feel differently.