s3:smb2_negprot: prefer AES128_CCM if the client supports it
authorStefan Metzmacher <metze@samba.org>
Mon, 17 Aug 2015 06:56:43 +0000 (08:56 +0200)
committerRalph Böhme <slow@samba.org>
Mon, 17 Aug 2015 15:43:36 +0000 (17:43 +0200)
commitbd0ec51cfca2b3baed60d304125079c74815073a
tree5af8806886ad512ea1125933d64a3817d71a6140
parent05dbd3b47a728acada971b545df458ae0e082ec5
s3:smb2_negprot: prefer AES128_CCM if the client supports it

Callgrind showed that we use 28,165,720,719 cpu cycles to send
a 100MB file to a client using aes-ccm.

With aes-gcm this is raises up to 723,094,413,831 cpu cycles.

BUG: https://bugzilla.samba.org/show_bug.cgi?id=11451

Signed-off-by: Stefan Metzmacher <metze@samba.org>
Reviewed-by: Ralph Boehme <slow@samba.org>
source3/smbd/smb2_negprot.c