Tweaking RAIDar's Java jre

StephenB wrote:

chirpa wrote: ReadyCloud and the other cloud services are optional, and easily disabled. From what I've seen, even when 'disabled' they are still phoning home constantly. Try on a 6.0, not using any 'cloud' apps, and check 'lsof -i' on a console, readycloud.netgear.com is still connected constantly, even when setup wizard in an Offline mode. They are enabled on my system right now, and there are connections to readycloud.netgear.com, red.netgear.com, and a couple of connections into the amazon cloud. When I have a chance I'll disable them all, and take another look.

With all cloud services disabled, there is still an https connection to readycloud.

rcbrokerd 1257  root    2u  IPv4   4759      0t0  TCP RN102:54808->readycloud.netgear.com:https (ESTABLISHED)

Adding ReadyNAS remote gives the following additional connections:

leafp2p   1216  root    5u  IPv4  12898      0t0  TCP RN102:34638->206.16.42.237:https (ESTABLISHED)
leafp2p   1216  root    6u  IPv4  12899      0t0  TCP RN102:34639->206.16.42.237:https (ESTABLISHED)
leafp2p   1216  root   10u  IPv4  12923      0t0  TCP RN102:38102->206.16.42.241:https (ESTABLISHED)
leafp2p   1216  root   11u  IPv4  12925      0t0  TCP RN102:59289->206.16.42.239:https (ESTABLISHED)
...
java      3161  root   44u  IPv6  12861      0t0  TCP RN102:53790->ec2-54-246-176-172.eu-west-1.compute.amazonaws.com:https (ESTABLISHED)

Then adding ReadyNAS Cloud we get a few more

brokerd   4583  root   10u  IPv4  12923      0t0  TCP RN102:38102->206.16.42.241:https (ESTABLISHED)
brokerd   4583  root   11u  IPv4  12925      0t0  TCP RN102:59289->206.16.42.239:https (ESTABLISHED)
hook.sh   4584  root   10u  IPv4  12923      0t0  TCP RN102:38102->206.16.42.241:https (ESTABLISHED)
hook.sh   4584  root   11u  IPv4  12925      0t0  TCP RN102:59289->206.16.42.239:https (ESTABLISHED)
...
sleep     4768  root   10u  IPv4  12923      0t0  TCP RN102:38102->206.16.42.241:https (ESTABLISHED)
sleep     4768  root   11u  IPv4  12925      0t0  TCP RN102:59289->206.16.42.239:https (ESTABLISHED)

Finally, adding readydrop:

curl      5267  root    5u  IPv4  19285      0t0  TCP RN102:46458->rds.netgear.com:https (ESTABLISHED)

Antivirus definitions updated during this test, making me wonder if the readycloud connection is being used to push Antivirus updates and notification of new firmware. That is just speculation though.