3 ms·
I know perfectly well how BlastDoor works, and I think maybe you are not the audience that this is intended for. This is not a "Why don't they just". It is an e
by extreme_eagle 5y ago
I know perfectly well how BlastDoor works, and I think maybe you are not the audience that this is intended for. This is not a "Why don't they just". It is an exact solution which resolves the issue in a way which is radically alternative to the current structure. They are trying to abstract the parsing, what must be done is prevent it entirely and relegate the flow of messages to the user-side. Assume that the attacker will inherently compromise the messaging structure and make it to where they don't have access to it instead.
- runjake 5y agoYeah, I guess I am misunderstanding what you are trying to say, then, because from my interpretation, this more or less sounds like BlastDoor, but with an added user/contact component. Adding the user component sounds like an interesting idea, but you've still got to parse the/a payload to get to that. And if you're looking to a zero trust style model, you definitely don't want security decisions put to users (aka "Grandpa Bob"), as demonstrated by email spam/phishing/malware.
- rdtwo 5y agoMost users aren’t affected by this level of attack but some people need the extra security and can live with the inconvenience