WinTLS: Channel setup failed error

[jakoch]

Hey!

I'm stuck with a WinTLS: Channel setup failed error.
I'm using aria2-1.18.10-win-64bit

The downloads work when executed individually, but as soon as one tries to use multiple downloads the SSL/TLS handshake failures pop up.
My workaround is to avoid parallel downloading and invoke aria2c for each URL.

I'm already using --check-certificate=false.
Are there any other CLI options to avoid this issue?

The issue is reproducible on Travis (Ubuntu) via Wine.
I can not reproduce this on a native Win7 box.
So this could be a Wine/Aria2 compatibility problem...

Cmd used:

aria2c -i downloads.txt --check-certificate=false --split=6 --min-split-size=2M --max-connection-per-server=6 --max-tries=3 --conditional-get=true --auto-file-renaming=false --allow-overwrite=true --http-accept-gzip=true --user-agent=Aria Download

downloads.txt

http://wpn-xm.org/get.php?s=pickle&v=0.4.0
   out=downloads\pickle.phar
http://wpn-xm.org/get.php?s=gogs-x86&v=0.5.9
   out=downloads\gogs.zip

[ERROR] WinTLS: Channel setup failed. Schannel provider did not fulfill requested flags. Excepted: 33180 Actual: 256
[ERROR] CUID#24 - Download aborted. URI=http://wpn-xm.org/get.php?s=pickle&v=0.4.0
Exception: [AbstractCommand.cc:350] errorCode=1 URI=https://github.com/FriendsOfPHP/pickle/releases/download/v0.4.0/pickle.phar
  -> [SocketCore.cc:933] errorCode=1 SSL/TLS handshake failure: Error: 80090304

�[ERROR�] WinTLS: Channel setup failed. Schannel provider did not fulfill requested flags. Excepted: 33180 Actual: 256
 [�ERROR�] CUID#9 - Download aborted. URI=http://wpn-xm.org/get.php?s=gogs-x86&v=0.5.9
Exception: [AbstractCommand.cc:350] errorCode=1 URI=https://github.com/gogits/gogs/releases/download/v0.5.9/windows_386.zip
  -> [SocketCore.cc:933] errorCode=1 SSL/TLS handshake failure: Error: 80090304

Regards, Jens

[nmaier]

You could always build aria2 on your own using the OpenSSL or GnuTLS TLS backend instead of WinTLS... Or use a linux build in the first place...

It seems to me that wine's Schannel implementation is incomplete or buggy, and seeing that this affects the context state flags, working around this would require not checking the channel integrity at all... Which might be actually an option for the --check-certificate=false case. Need to ponder on this.