Perhaps people just need time to get used to the River 3.0 release codebase before we start moving forward again.
Does anyone need a com.sun.jini compatibility layer to assist migration to River 3.0? I guess we should designate the next release for bugs / patches for the time being. We have a lot of subscribers on dev, just not much participation. I'll announce the release once I've had time to update the website. Regards, Peter. Sent from my Samsung device. Include original message ---- Original message ---- From: Peter <j...@zeus.net.au> Sent: 11/10/2016 06:18:25 pm To: dev@river.apache.org <dev@river.apache.org> Subject: Re: River's Future My apologies, try this. https://www.contrastsecurity.com/security-influencers/java-deserializing-open-source-tool Sent from my Samsung device. Include original message ---- Original message ---- From: "Michał Kłeczek (XPro Sp. z o. o.)" <michal.klec...@xpro.biz> Sent: 11/10/2016 06:07:34 pm To: dev@river.apache.org Subject: Re: River's Future This is interesting but the link is broken. Michal Peter October 11, 2016 at 10:02 AM I'd like to donate atomic input validation for Java serialization to River. At least one security researcher has provided some initial positive feedback. See the comments at the end of this article. https://contrastsecurity.com/security-influencers/java-deserializing-open-source-tool Regards, Peter. Sent from my Samsung device.
