You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 15, 2021. It is now read-only.
It's bad practice to constantly encrypt with your root key. It puts the key on a network connected process and it uses the key too much thus helping cryptoanalysis. So what we really want to do is have a root key and then follow that with a device key. To do that we need a way for the root key (which is the real identity) to sign the device key. Probably the easiest way to do this is via cert chains. So we need to be able to generate and validate cert chains.
The text was updated successfully, but these errors were encountered:
It's bad practice to constantly encrypt with your root key. It puts the key on a network connected process and it uses the key too much thus helping cryptoanalysis. So what we really want to do is have a root key and then follow that with a device key. To do that we need a way for the root key (which is the real identity) to sign the device key. Probably the easiest way to do this is via cert chains. So we need to be able to generate and validate cert chains.
The text was updated successfully, but these errors were encountered: