Consider not storing dev/test keys in repo

[d3zd3z]

Currently, development keys are stored in the repo. As long as the instructions are followed, this should not result in these keys being used in production. However it is possible for this to happen. One way to fix this is to remove these keys, and instead, have all of the systems that used the development keys instead create a set if they are needed. Ideally, this would be created once in a developer's workspace, and the same keys would be reused. This needs to be coordinated across all of the systems that use MCUboot, including the simulator, Zephyr, MyNewt, and the other supported platforms.

[bn-norbit]

#1088 can also address this issue for Zephyr. If the default keys are removed, the user is forced to generate an encryption key and set CONFIG_BOOT_ENCRYPT_KEY_FILE accordingly. The encryption tests can generate a keys on the fly.

[d3zd3z]

Thanks @bn-norbit, This does help this for Zephyr. A challenge with this issue is addressing it for every platform before the keys can be removed. But, maybe when we address it for a given platform, that platform needs to be changed so that it never uses the in-tree keys.

[github-actions]

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.