Hi, unfortunately I ran another dist-upgrade this morning on unstable, and now the problem seems to have disappeared.
When I could still see the problem, I could see that gnutls-cli negotiates the same ciphersuite as evolution does, so I assume changing the priority string would not cause any changes. I still have a pcap capture of the traffic, but without the private keys, it would not be very helpful for debugging. I would suggest to close that problem for now, and maybe open it later again should other problems related to AES-NI appear. Best regards, Erik Am Donnerstag, den 04.06.2015, 14:02 +0200 schrieb Andreas Metzler: > On 2015-06-03 Erik Tews <[email protected]> wrote: > > Source: gnutls28 > > Version: 3.3.15-5 > > Severity: important > > > Dear Maintainer, > > > After having updated gnutls to 3.3.15-5, my evolution is unable to > > connect to my imap server on mail.datenzone.de port 993 using imap-ssl. > > However I can still connect to that server using gnutls-cli or icedove. > [...] > > Hello, > > can you reproduce the issue if you you use the same gnutls priority > string with gnutls-cli as evolution. I guess it's using > glib-networking's default value, > NORMAL:%COMPAT:%LATEST_RECORD_VERSION > > cu Andreas
signature.asc
Description: This is a digitally signed message part
