In such cases (which // is the case for bookmarks created before 2015), this GUID must match the // value inferred from the combination of originator cache GUID and // originator client item ID, see InferGuidForLegacyBookmark(). // If present, it must be the same as originator_client_item_id in lowercase, // unless originator client item ID is not a valid GUID. Introduced in M81, it represents a globally unique and immutable ID. Corresponds to BookmarkNode::date_added() represented as microseconds since // the Windows epoch. optional string legacy_canonicalized_title = 3 Contains legacy title which is truncated and may contain escaped symbols. In components/sync/protocol/sync.proto, each SyncEntity contains EntitySpecifics which is the actual data of each data type. Then the stretched key is used directly as a AES128-CTR-HMAC encryption key.Future clients will receive the salt from the server so that they can derive the same key. The first client generates a random salt and sends it to the server. BIP39 phrase is key-stretched using scrypt(N = 2^13, r = 8, p = 11).The rest of the encryption is handled by Chromium as follows: Instead of letting the user pick a passphrase, which may be weak, we force the passphrase to be the BIP39 encoding of the sync seed. We use the built-in custom passphrase feature from Chromium sync and encrypt everything client-side. Timestamps over 1 day old are considered expired. And every server response contains Sane-Time-Millis header which will update the network time. Timestamp is fetched from network time if network time is not available at the moment, client uses local time. HKDF-SHA512 is used to derive the Ed25519 signing keypair used for authentication to the sync server.Ĭlient will compose a sync server access token following the format base64(timestamp_hex|signed_timestamp_hex|public_key_hex). If another client wants to join the sync chain, they can enter the BIP39 key phrase from the initial client by entering the words manually or scanning a QR code. Uses a Brave-operated sync server so no data is sent to Google serversĪ 'Sync Chain' is configured using a 32-byte random seed generated by the initial client.Doesn't require sign-in to use sync (we use the same 'Sync Chain' concept from v1).Brave Sync version 2 aims to make a wire compatible server side protocol which understands components/sync/protocol/sync.proto used by the official Google sync service.

Brave browser sync