forked from rdkcentral/rdkservices
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Reason for change: * MM checkNetwork() checks org.rdk.Network active before invoking org.rdk.Network.isConnectedToInternet. checkNetwork() returns false if inactive or isConnectedToInternet fails/is false, so the check is redundant. * MM checkActivatedStatus() checks org.rdk.AuthService active. MM doesn't activate it and org.rdk.AuthService doesn't auto start so this might not work or relies on external factor. Not attempting to fix that. org.rdk.AuthService should be used via QueryInterfaceByCallsign, this suffices to check if it's active. * MM acquires token but never uses it, this code is redundant. * Remove UtilsSecurityToken.h, UtilsSecurityToken.cpp, and SecurityUtil from MM. * RDKShell checks org.rdk.System active. RDKShell doesn't activate it and org.rdk.System doesn't auto start so this might not work or relies on external factor. Not attempting to fix that. org.rdk.System should be used via QueryInterfaceByCallsign, this suffices to check if it's active. * SecurityAgent should be used via QueryInterfaceByCallsign. * RDKShell used 2 variants of getThunderControllerClient(), one variant should be enough. * Remove UtilsSecurityToken.h, UtilsSecurityToken.cpp, and SecurityUtil from RDKShell. * DisplaySettings indefinitely checks org.rdk.HdmiCecSink active. On several platforms org.rdk.HdmiCecSink doesn't exist hence log flooding. DisplaySettings relies on race conditions in org.rdk.HdmiCecSink using sleep(...). Not attempting to fix that. org.rdk.HdmiCecSink should be used via QueryInterfaceByCallsign, this suffices to check if it's active. * DisplaySettings attempts to activate org.rdk.HdmiCecSink. This looks like design flaw. DisplaySettings activates org.rdk.HdmiCecSink in blocking way. Not attempting to fix that. Controller IDispatcher interface can activate. * DisplaySettings attempts to activate org.rdk.HdmiCecSink twice in onTimer(), the second one is redundant because timer will reschedule. * Remove UtilsSecurityToken.h, UtilsSecurityToken.cpp, and SecurityUtil from DisplaySettings. * Delete UtilsSecurityToken.h, UtilsSecurityToken.cpp. Test Procedure: * MM logs "AuthService is active". * RDKShell logs "SystemService is already activated". * RDKShell logs "RDKShell got security token". * RDKShell regression test. * DisplaySettings logs "org.rdk.HdmiCecSink is active". Risks: Low Signed-off-by: Nikita Poltorapavlo <[email protected]>
- Loading branch information
1 parent
3e4f0b1
commit 2126ff9
Showing
11 changed files
with
137 additions
and
315 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.