The following tree contains a change to Version.java that allows alternate Freenet builds to work transparently with official builds in the network.
A new variable is introduced, networkVersion, which is reported to peers instead of buildNumber. It turns out this was easier to do than rewrite NodeUpdateManager to break the assumption that edition number of the UpdateURI was the same as buildNumber. This tree has the change: https://github.com/justusranvier/fred-staging/commit/41962370ad797844f2015935b14ce9faa284e8fd This tree is a proof of concept which starts out with buildNumber 0 but reports build 1417 to its peers. I have tested it to verify it will discover and download updates from a keyspace I control while connecting seamlessly to opennet and darknet peers which run the official build. https://github.com/justusranvier/fred-staging/commit/482fbe1fc7084072cb7a58cff686ca0a259d245a If you want to test this proof of concept, download this key and save it as freenet.jar: SSK@virOTvBfehYSm3JZGAHI8aUg1mROfclxMRBkvkwYIHc,pSr0VwTMXZEF5TwQMN7fW9cBEB58NzaFGZxurlIL71E,AQACAAE/update-0 Then start it using a freenet.ini without a node.updater.URI line. The node will discover new builds 1 and 2 and will upgrade itself as long as automatic updating is enabled. Any peers of this node will see it reporting version 1417.
0x1B438BF4.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Devl mailing list Devl@freenetproject.org https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
