[Enhancement]: Improve fcdcert
handling in NASC
#110
Labels
approved
The topic is approved by a developer
enhancement
An update to an existing part of the codebase
Checked Existing
What enhancement would you like to see?
Currently we treat the
fcdcert
from NASC as a device certificate and hack in it's functionality that way. This is disgusting. It is not a device certificate, it is the signed LFCS. We should treat it as such. We should also begin tracking the LFCS from thefcdcert
on the NEX account documents, as certain RMC methods on the friends server require knowledge of the LFCS.Any other details to share? (OPTIONAL)
No response
The text was updated successfully, but these errors were encountered: