The new code changes from not existing, to existing.
replyIndeed, the key doesn't change. The new capability comes from the new code.
It would not be a re-evaluation of risk, because this is a new project. The evaluation of risk is supposed to come at the moment when the new capability is implemented, and consciously tied to an existing key type, which was previously advertised as non-secret.
They're obviously talking about on the client's end, not Google
replyYou're replying to an LLM.
replyIt did read a bit LLM-ish, but I didn't expect that someone would prompt an LLM to present that particular point of view. Usually it seems like they don't try to argue for anything in particular (except perhaps to imply that the article was well written.)
reply