| Commit-Queue | +1 |
if (desktop_environment_options.enable_security_key()) {Yuwei HuangBy moving `SecurityKeyExtension` creation here, it is added unconditionally (if the host option is enabled), bypassing the `security_key_auth_policy_enabled_` check that used to be in `RemotingMe2MeHost`.
Because `SecurityKeyExtensionSession` no longer has access to policies, it will process gnubby control/data messages even if the enterprise policy disables it, potentially causing a policy bypass.
To fix this in the interim before the data channel migration is complete, read the local policy from `local_session_policies_provider_`. This will ensure you are on par with the old behavior.
Done
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Auto-Submit | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
if (security_key_auth_policy_enabled_ &&Yuwei HuangSince `SecurityKeyExtension` lifecycle has been moved to `ClientSession`, `security_key_auth_policy_enabled_` is no longer used to gate the extension.
As mentioned in the TODO above `OnGnubbyAuthPolicyUpdate()`, this callback and the associated host restart logic can likely be completely removed now.
Done
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
auth_handler_->SetSendMessageCallback(base::NullCallback());Just a question: does every caller of GetSendMessageCallback() check the returned value for null before using it?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +2 |
Thanks!
auth_handler_->SetSendMessageCallback(base::NullCallback());Just a question: does every caller of GetSendMessageCallback() check the returned value for null before using it?
It looks like it is only used in tests. Maybe we should add the `ForTesting` suffice, but that's for another day.
https://source.chromium.org/search?q=GetSendMessageCallback%20f:Remoting
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
remoting: Refactor security key pipeline to support different transports
The goal is to allow ClientSession to create
SecurityKeyDataChannelHandler that uses the same underlying
SecurityKeyAuthHandler when the client supports the securityKeyV2
capability.
- Pull SecurityKeyAuthHandler out of SecurityKeyExtension and make
ClientSession own it. This allows SecurityKeyDataChannelHandler to
take WeakPtr<SecurityKeyAuthHandler>.
- Create SecurityKeyExtensionSession inside ClientSession instead of
HostProcess since HostProcess doesn't have access to the
SecurityKeyAuthHandler.
- Remove `send_message_callback` from SecurityKeyAuthHandler::Create
since SecurityKeyExtension and SecurityKeyDataChannelHandler call
SetSendMessageCallback() in their constructor instead.
- Remove `security_key_auth_policy_enabled_`,
HostProcess::OnGnubbyAuthPolicyUpdate and friends, since we now
check the policy for each session, and there is no need to restart
the host upon policy change.
In the next CL, ClientSession will create SecurityKeyDataChannelHandler
after authentication and hook it up to SecurityKeyAuthHandler if the
client supports the securityKeyV2 capability.
TAG=agy
CONV=a74bbced-b6c1-454e-adea-b8a5ad41a1ef
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |