On Mon, Oct 22, 2012 at 6:42 PM, Merijn Verstraaten <[email protected]> wrote:
> In summary, I think: > The minimal scenario ROUTER needs to be able to deal with to be usable on a > public network is clients setting malicious identities. This means: > - Check whether identity is allowed before letting client connect > - Disconnecting a given identity > - Not allowing connections using an identity that is already connected Merijn, it makes sense but you don't really need to convince anyone. Simply write an issue where you state the lack of identity checking as a problem, try fixing this in the code, send a patch, see what happens. Since we're pretty much done with stable 3.2, it's a good time to do experiments. My advice is to make small, careful steps and get feedback through running code rather than up-front discussion. If you make disruptive changes that annoy people, they'll simply patch them away. Enjoy! -Piieter _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
