Is there a way to renew a code signing key without having to tell BAM to detach a project from all hosts, wait 24 hours to make sure all hosts detach then tell BAM to attach again in order for all the hosts to get the new key?
Is there something in the works from Boinc that help prevent this in the future?
There has got to be an easier way to do it and not waste all those cycles.

This is (another) unforeseen situation.

Since they did not change the URL as well, there is no way BAM! can tell that a host is already updated. Meaning that it would keep detaching/attaching the hosts until I manually remove the update.

The folks at Lattice said that just Updating might be enough, and I have downloaded work successfully since then, so this seems that it might not be an issue.

A project reset can also sometimes clear this problem. However the only solution that works 100% of the time is detaching and reattaching.

I agree with you guys about updating or resetting.

But, if you have multiple hosts in multiple locations it is not convenient to go around to them all and update/reset them. It would literally take me a whole day to go to all the houses and offices to do it.

That is why I use BAM!

Maybe in the future BAM! will have a secure way to do a push. Till then I guess we are stuck having to do it the long way of forcing a detach and waiting a day then reattaching to update the signing key.