Displaying 3 results from an estimated 3 matches for "another_new_a".
Did you mean:
another_new_aes
2015 Feb 07
3
TLS config check
...too and according to Brcue Schneier years ago AES128 has even
> less problems then AES256 (too lazy for google it again)
>
Well, I am working in the crypto field and was a bit astonished about
this "rant" - so a quick search brought up
https://www.schneier.com/blog/archives/2009/07/another_new_aes.html -
for those who want it more compact
http://crypto.stackexchange.com/questions/5118/is-aes-256-weaker-than-192-and-128-bit-versions.
Bottom line: AES256 *IS* better than AES128 for the intended usage but
it is also true that AES-GCM rules out other AES based block ciphers for
other kinds of...
2019 Oct 28
3
changing cipher for imap clients
When my client connects, I see this in my log:
dovecot: imap-login: TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128
bits)
Whereas, when client connects to my postfix server, I see:
Anonymous TLS connection established from * TLSv1 with cipher
ECDHE-RSA-AES256-SHA (256/256 bits)
how can I tell dovecot to use AES256, instead of AES128 ?
is this set by ssl_cipher_list ? Here are my current
2015 Feb 06
2
TLS config check
According to https://cipherli.st/
> ssl = yes
> ssl_cert = </etc/dovecot.cert
> ssl_key = </etc/dovecot.key
> ssl_protocols = !SSLv2 !SSLv3
> ssl_cipher_list = AES128+EECDH:AES128+EDH
> ssl_prefer_server_ciphers = yes # >Dovecot 2.2.6
> Is what you want.
Ok, so I have changed my ssl_cipher_list to: ssl_cipher_list =
AES128+EECDH:AES128+EDH
Before I made this change