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
Currently, that MasterASKey cannot be changed. According to the SCION book this key should change every couple of days. The current proposal to do this having at most two keys active (to enable seemless key rollover) and adding a 'keyslot' bit to each HopField that indicates which key slot is used for the hop field.
The text was updated successfully, but these errors were encountered:
Remove MasterASKey from as_conf.yml.
The generator creates two keys in preparation for master key rollover (#1714 )
- `master0.key`
- `master1.key`
Fixes#1718
The BS would be in charge of master key rollover. The BR doesn't actually need the master key, it only needs the hopfield MAC key if i remember correctly. In that case the BS would send a command to the BR saying "update your hopfield MAC key on slot [01]", and the BR needs to persist this to disk to survive restarting the process.
(Such a message would need to be strongly authenticated and encrypted)
Currently, that
MasterASKey
cannot be changed. According to the SCION book this key should change every couple of days. The current proposal to do this having at most two keys active (to enable seemless key rollover) and adding a 'keyslot' bit to eachHopField
that indicates which key slot is used for the hop field.The text was updated successfully, but these errors were encountered: