davmac

4 ms·

1.
by davmac 9y ago
late reply, I know - I only just saw this discussion - I didn't post this story to HN myself. However: I recently wrote a blog post discussion why I created Dasynq, here: https://davmac.wordpress.com/2017/12/1
2.
by davmac 10y ago
Also: > More importantly, this is an error which can happen purely on the client side. You don't need to compromise the node itself, you just need to compromise some peer between the client you wish to attack and the node. This is a
3.
by davmac 10y ago
> Or somebody closes your socket. There are several ways in which this can happen, most of them undesirable Please tell me how a third party can close an anonymous socket connection between two processes (because if there really is a way
4.
by davmac 10y ago
> Sadly, the author failed to read on the history of kdbus and AF_BUS On the contrary, I've been following their development from the beginning, with some interest. > This is more or less what dbus currently does Actually D-Bus m
5.
by davmac 10y ago
> This is exactly how D-Bus works right now Let me clarify: this is exactly how D-Bus conceptually works right now. In practice of course D-Bus acts as a multiplexor for the communications also. It is, however, possible to send one half
6.
by davmac 10y ago
> Choice quote It's strange to me how often that particular quote, which was intended to be more humorous than anything (ok - I understand if most people don't think it's funny; that doesn't mean it wasn't meant
7.
by davmac 10y ago
> Also some of the suggestions are downright dangerous You give only one example, which I've rebutted below. I disagree with the assertion as a whole. > this is another failure state that you add to every single connection, and w