)]}' { "commit": "433366587d6156c9660cc87a843e9dcef1a58917", "tree": "0f2d5c9f677088ff6b606344486f6b7fda9bf386", "parents": [ "bd30f480c5bf62444d350abd9a81958b0bb81ae8" ], "author": { "name": "David Benjamin", "email": "davidben@google.com", "time": "Thu Mar 03 15:32:29 2016 -0500" }, "committer": { "name": "Adam Langley", "email": "agl@google.com", "time": "Fri Mar 04 19:07:12 2016 +0000" }, "message": "Move AES128 above AES256 by default.\n\nThis is in preparation for adding AES_256_GCM in Chromium below AES_128_GCM.\nFor now, AES_128_GCM is preferable over AES_256_GCM for performance reasons.\n\nWhile I\u0027m here, swap the order of 3DES and RC4. Chromium has already disabled\nRC4, but the default order should probably reflect that until we can delete it\naltogether.\n\nBUG\u003d591516\n\nChange-Id: I1b4df0c0b7897930be726fb8321cee59b5d93a6d\nReviewed-on: https://boringssl-review.googlesource.com/7296\nReviewed-by: Adam Langley \u003cagl@google.com\u003e\n", "tree_diff": [ { "type": "modify", "old_id": "7aa4a6fb83e344a8db4710d271449610953a31e2", "old_mode": 33188, "old_path": "ssl/ssl_cipher.c", "new_id": "9c9a4413d55d7f803e3f1c6b91a980658c7bbb5d", "new_mode": 33188, "new_path": "ssl/ssl_cipher.c" } ] }