From 4244c91e2788bc34862dbef7a72ad45a6a2bd5bd Mon Sep 17 00:00:00 2001
From: Christopher Tate <ctate@google.com>
Date: Wed, 8 Feb 2017 14:26:50 -0800
Subject: [PATCH] Whitelist LocalTransport here in the framework sysconfig

This shouldn't properly be emplaced as a side-effect of partner-
specific configurations; so now we don't do that any more.

Bug 35151478
Test: verify whitelist contents with 'bmgr whitelist'

Change-Id: I854ddfdbcec1def882b24f5ea7955b28d4789806
---
 data/etc/framework-sysconfig.xml | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/data/etc/framework-sysconfig.xml b/data/etc/framework-sysconfig.xml
index 62ef25b1af0d2..7fafef7546699 100644
--- a/data/etc/framework-sysconfig.xml
+++ b/data/etc/framework-sysconfig.xml
@@ -23,4 +23,9 @@
     <allow-implicit-broadcast action="android.intent.action.PACKAGE_CHANGED" />
     <allow-implicit-broadcast action="android.intent.action.MEDIA_SCANNER_SCAN_FILE" />
 
+    <!-- Whitelist of what components are permitted as backup data transports.  The
+         'service' attribute here is a flattened ComponentName string. -->
+    <backup-transport-whitelisted-service
+        service="android/com.android.internal.backup.LocalTransportService" />
+
 </config>