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

chrome/browser/sync/protocol/nigori_specifics.proto

 // Copyright (c) 2010 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 //
 // Sync protocol datatype extension for nigori keys.
 
 // Update proto_value_conversions{.h,.cc,_unittest.cc} if you change
 // any fields in this file.
 
 syntax = "proto2";
@@ skipping 16 matching lines @@
 message NigoriKeyBag {
   repeated NigoriKey key = 2;
 }
 
 // Properties of nigori sync object.
 message NigoriSpecifics {
   optional EncryptedData encrypted = 1;
   // 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 {
   optional NigoriSpecifics nigori = 47745;
 }