Open kroeckx opened 8 months ago
After F2F
It should include details on how people can check that their code is affected or not. This might include things like affected functions, so they can search there code to see if they're affected or not.
Other useful information to add is which commit (per branch) introduced the problem.
I think we need to have a document describing what should all be covered in a security advisory. We've talked about this several times in the past, but I can't actually find an open issue for it.
Some of the things we should consider: