[Sync] Initial support for encrypting any datatype (no UI hookup yet).

chrome/browser/sync/protocol/nigori_specifics.proto

Index: chrome/browser/sync/protocol/nigori_specifics.proto
diff --git a/chrome/browser/sync/protocol/nigori_specifics.proto b/chrome/browser/sync/protocol/nigori_specifics.proto
index 98ee1b704796adc092e855bb3a4727e244d316c1..e84f8df5752944dbbdd87a55e9e186536b26c3ce 100644
--- a/chrome/browser/sync/protocol/nigori_specifics.proto
+++ b/chrome/browser/sync/protocol/nigori_specifics.proto
@@ -34,6 +34,18 @@ message NigoriSpecifics {
   // True if |encrypted| is encrypted using a passphrase
   // explicitly set by the user.
   optional bool using_explicit_passphrase = 2;
+  
+  // Booleans corresponding to whether a datatype should be encrypted.
+  optional bool encrypt_bookmarks = 3;
+  optional bool encrypt_preferences = 4;
+  optional bool encrypt_passwords = 5;

[tim (not reviewing), 2011/02/15 19:58:04]

I don't think we want this bool?  You can't have passwords without encryption
right...

[Nicolas Zea, 2011/02/15 23:30:51]

Done.

+  optional bool encrypt_autofill_profile = 6;
+  optional bool encrypt_autofill = 7;
+  optional bool encrypt_themes = 8;
+  optional bool encrypt_typed_urls = 9;
+  optional bool encrypt_extensions = 10;
+  optional bool encrypt_sessions = 11;
+  optional bool encrypt_apps = 12;
 }
 
 extend EntitySpecifics {