Note the comment about security on the blog? Steps I've taken to simplify security (that could also be adopted by river): 1. Deprecate proxy trust, replace with authenticate service prior to obtaining proxy. 2. proxy codebase jars contain a list of requested permissions to be granted to the jar signer and url (client need not know in advance). 3. Policy file generation, least privilege principles (need to set up command line based output for admin verification of each permission during policy generation). 4 Input validation for serialization. 5. DownloadPermission automatically granted to authenticated registrars (to signer and url, very specific) during multicast discovery.
Need to more work around simplification of certificate management. Regards, Peter. Sent from my Samsung device. Include original message ---- Original message ---- From: Peter <j...@zeus.net.au> Sent: 26/07/2016 10:27:59 am To: dev@river.apache.org <dev@river.apache.org> Subject: another interesting link https://blogs.oracle.com/hinkmond/entry/jini_iot_edition_connecting_the Sent from my Samsung device.
