Re: Encryption algorithm in TLS
Peter Gutmann <[email protected]> Mon, 25 Feb 2013 13:52:21 +1300
| Newsgroups | gmane.comp.encryption.cryptlib |
|---|---|
| Message-ID | <[email protected]> |
David Pierre <[email protected]> writes: >Hi, is there a practical way to change the encryption algorithm ? As far as I >understand the library, data are encrypted with 3-DES in each TLS session. I >would try to use AES, or to not use encryption at all. Could I do that >changing cryptlib code, or with an option ? Is this requesting too much >change to be available ? The algorithms used in TLS are controlled by a complex set of lookup tables, at the moment the code defaults to preferring 3DES over AES for legacy reasons (there's code out there that still tries to start an SSLv2 handshake, although at least support for that is disable by default in cryptlib). If you want to prefer AES, look at session/ssl_suites.c, and for something like cipherSuiteDH (line 62) just swap the entries for 3DES and AES so the AES ones come first. If you want it used throughout all the suites you'll have to do the swap for all the other tables as well. (Note also all the code comments there on some of the voodoo that's necessary for things to work smoothly). Peter. _______________________________________________ Cryptlib mailing list [email protected] via Mail: [email protected] Archive: ftp://ftp.franken.de/pub/crypt/cryptlib/archives/ http://news.gmane.org/gmane.comp.encryption.cryptlib Posts from non-subscribed addresses are blocked to prevent spam, please subscribe in order to post messages.