Author should be grateful for my explanations and attempts here.
Simply because i am finding "holes" in his approach and by doing that in public; i am helping him to improve it in next versions.
So, the best defense and prevention against my previous hack idea would be author to also use bootloader space and to put a "chunk" of his code there too.
So code will not run if bootloader is customized later.
There is plenty of space in bootloader area to add few extra lines.
So, few important calls from the main code may be replaced into bootloader space and invoked from there.
That's more better security!
Simply because i am finding "holes" in his approach and by doing that in public; i am helping him to improve it in next versions.
So, the best defense and prevention against my previous hack idea would be author to also use bootloader space and to put a "chunk" of his code there too.
So code will not run if bootloader is customized later.
There is plenty of space in bootloader area to add few extra lines.
So, few important calls from the main code may be replaced into bootloader space and invoked from there.
That's more better security!

Comment