The update client has been overhauled and published under an MIT license at github.com/AndroidHardeni.
It's essentially feature complete other than implementing streaming update support, which mostly involves setting up scripts to make signed update zips with only the metadata.
Conversation
Replying to
I build an aosp_crosshatch successful without the updateclient, which costs me all weekend (need new cpu) on a pull of your platform_manifest. Is your intended use for own builds to fork the updateclient (and therefor also platform_manifest) and change the update url?
1
Replying to
Yes, otherwise it's going to be repeatedly downloading incompatible updates from the official server over and over again. They'll fail to pass signature validation and will get deleted and downloaded again just as would happen with a corrupt update package.
It's not intended that anyone other than people working on development are building this yet. There's no hardening integrated yet and I haven't implemented workarounds to deal with people building it without either removing the Updater or pointing it at their own update server.