@rmhrisk@WatsonLadd@CrowdStrike@Microsoft I’m guessing it’s closer to arbitrary code execution, but done in a way that allows dynamic loading beyond what the kernel would allow normally, and routing around authenticode using their own authentication.
@AlecMuffett@c7five@mer__edith There’s a out of nuances in that (look at how browsers web APIs for file access work and how access is brokered with a fairly convenient UI, which I would love Word to mimic) but I am not sure what that has to do with the tweet you replied to. Note that “silly” ≠ vulnerability.
@AlecMuffett@c7five@mer__edith That’s not what I’m saying. It’s poor marketing to do silly stuff with cryptography when the product’s primary marketing is driven by the founders’ crypto expertise—especially when even Chrome (the father of Electron) already addressed the same concern, before Electron existed.
@AlecMuffett@c7five@mer__edith Other applications have made better choices for key storage using same tools across the same platforms. I think people do generally expect that higher level of key protection from Signal. However, I would say it hardly matters b/c Electron is an overwhelming security weakness.
@tweagio Really nice. Not sure why all the BUILD files still need to be written by hand. It seems like a tool should be generating the initial versions of them, at least. In the past I got stuck with tests because the test environment isn’t the same uunder Bazel as under `cargo test`.
@nick_r_cameron@aeruhxi I think the intent is you use Arc/Rc primarily for cases where that advice is true, so if you’re using Arc/Rc then there is a presumption that you want to increment reference counts instead of copying. Maybe people are too quick to reach for Arc/Rc, but that’s a different issue.