What
The internal flow that creates a serving link for a cloud or remote session (linkForServing) now carries along a request value, built from the session's own startup data, and passes it into a new step called signRequest. The signer behind this (previously called Yn, now ns) can then sign either the plain way or in a way that is tied to the specific request, depending on whether a request was given.
Why
This is an internal change to how serve links are signed, tying a signature more closely to the specific session request rather than reusing a generic signature. It has no direct setting or command for readers to use, but it affects the security plumbing behind device-serving links for cloud and remote sessions.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding does not say what user-visible effect, if any, this has, or why request-scoped signing was introduced.