How to fix the SSL/https problem?

[Schuttwegraeumer]

i use a application that use a https connection to load a file at startup.
but since update to 1.1.43 the SSL part dont work.
How to fix it, quange the crypt32.dll with a real crypt32.dll from a windows dont work here.

[Schuttwegraeumer]

If I start the programm with $:wine app i got this:

err:wininet:NETCON_secure_connect SSL_connect failed: 12157

[Schuttwegraeumer]

No solution?

[dimesio]

Run a regression test and file a bug if one hasn't already been filed. http://wiki.winehq.org/RegressionTesting

[Schuttwegraeumer]

Is it nessesary to compile wine?
I use the repository and i have the problem with this version of wine on Ubuntu 32bit 9.10, 10.04 and Ubuntu 64bit 10.04.

[James McKenzie]

Schuttwegraeumer wrote:

Is it nessesary to compile wine?
I use the repository and i have the problem with this version of wine on Ubuntu 32bit 9.10, 10.04 and Ubuntu 64bit 10.04.

If you want to do a regression test, yes you have to compile it. This
is something you should do if you expect the problem to be resolved. We
are volunteers (for the most part) and our time to work on this project
is very limited.

What you state above is that the problem definitely exists in Wine.

If you can open a bug report and provide as much detail as possible,
this is a good start. This way, if you cannot do a regression test,
someone else might be able to.

Thank you.

James McKenzie

[Schuttwegraeumer]

The 1.1.42 is default in Ubuntu 10.04.
But there is a 1.0.1 in the default repostitory too.
I am back to 1.0.1 now.
I dont know why Ubuntu use the unstable instead of the stable as default.

[James Mckenzie]

The 1.1.42 is default in Ubuntu 10.04.
But there is a 1.0.1 in the default repostitory too.
I am back to 1.0.1 now.
I dont know why Ubuntu use the unstable instead of the stable as default.

Three reasons:

The stable version is over 1 1/2 years old.
There are many bug fixes in the unstable.
but most importantly: We asked them to do it.

We don't take bug reports on Wine 1.0.1 anymore and the response you will receive is to move to the unstable and then test again.

Now to what I ASKED YOU TO DO: Conduct a regression test with the current version and the last known good version. This will point out what piece of code that was added to Wine that caused this function to stop working. Then a developer (or two) can start fixing it. Without the test, it is a long painful and not likely to happen fix.

Remember, most of us out here are volunteers, working on this project in what little spare time we have to fully create a Windows32 and Windows64 API that allows you to run your favorite programs on Linux/UNIX.

James McKenzie

[Schuttwegraeumer]

The stable version is over 1 1/2 years old.
There are many bug fixes in the unstable.
but most importantly: We asked them to do it.

We don't take bug reports on Wine 1.0.1 anymore and the response you will receive is to move to the unstable and then test again.

Now to what I ASKED YOU TO DO: Conduct a regression test with the current version and the last known good version. This will point out what piece of code that was added to Wine that caused this function to stop working. Then a developer (or two) can start fixing it. Without the test, it is a long painful and not likely to happen fix.

Remember, most of us out here are volunteers, working on this project in what little spare time we have to fully create a Windows32 and Windows64 API that allows you to run your favorite programs on Linux/UNIX.

James McKenzie

I am debugging a checkinstall problem at the moment.
thats important for the test with wine because i will NEVER make a "make install".
Installing without using the APT system is not allowed on my system.
I think howtos with "make install" in it should be prohibited by law

PS: I cannot belief that i am the only user with SSL Problems

[lahmbi5678]

It should be possible to run wine from the directory, where it was built. see
http://wiki.jswindle.com/index.php/Adva ... ource_tree
and the following section. I don't know if it still works that way, but you should give it a try.

[lahmbi5678]

Thinking about it, for the regression test described under http://wiki.winehq.org/RegressionTesting you don't have to "make install". If you just want to test older wine releaes, it will be much easier to download the compiled packages, from http://sourceforge.net/projects/wine/files/ or http://wine.budgetdedicated.com/archive/index.html.

[James McKenzie]

Schuttwegraeumer wrote:

James Mckenzie wrote:

The stable version is over 1 1/2 years old.
There are many bug fixes in the unstable.
but most importantly: We asked them to do it.

We don't take bug reports on Wine 1.0.1 anymore and the response you will receive is to move to the unstable and then test again.

Now to what I ASKED YOU TO DO: Conduct a regression test with the current version and the last known good version. This will point out what piece of code that was added to Wine that caused this function to stop working. Then a developer (or two) can start fixing it. Without the test, it is a long painful and not likely to happen fix.

Remember, most of us out here are volunteers, working on this project in what little spare time we have to fully create a Windows32 and Windows64 API that allows you to run your favorite programs on Linux/UNIX.

James McKenzie

I am debugging a checkinstall problem at the moment.
thats important for the test with wine because i will NEVER make a "make install".

Hmmm. All make install does is move the files from your build directory
to the /usr directory structure so it is NOT NECESSARY to use it to run
a home-brewed wine build.

Installing without using the APT system is not allowed on my system.
I think howtos with "make install" in it should be prohibited by law

Certainly they can be misleading. Remember, most how-tos make assumptions.

PS: I cannot belief that i am the only user with SSL Problems

I have not been able to get a good Wine build on my Mac. No, I don't
want to install through MacPorts nor Fink. They make removing and
reverting builds a massive headache and don't operate per MacOSX best
practices. Zach Drayer used to build an installer that did de-install
and Mike Kronenberg had run into problems making Wine 1.1.43. Also, I
am building custom builds to test some code that will fix about six or
seven programs (most notably the Print Preview for a few programs, like
Word.)

So, you don't need to 'make install' to test a custom or regression build.

And using apt might be a 'good thing' but then again it has been known
to break things as well. No program is perfect.

James McKenzie

[zigstat]

I'm having similar problems getting the Opt-In program for battle net beta testing to work ( i'd imagine, same kinda error ) and I found another post of where others were having this issue and did a WINEDEBUG=+wininet run of it and heres a few lines around about where the error occured, lemme know if posting more would help or where I can go with this, and know I'm not experienced debugger so if you can help me in anyway, be specific or throw up links.. anyway..

Code: Select all

trace:wininet:HTTP_HttpSendRequestW Request header -> L"POST /account/systemsurvey/submit.xml?purpose=sc2beta HTTP/1.1\r\nHost: us.battle.net\r\nUser-Agent: Blizzard Web Client\r\nCache-Control: no-cache\r\nContent-Type: application/x-www-form-urlencoded\r\nContent-Length: 352\r\n\r\n"
trace:wininet:HTTP_OpenConnection -->
trace:wininet:INTERNET_SendCallback  callback(0x42ac80) (0x3 (0x152b40), 004ea0c0, 10 (INTERNET_STATUS_RESOLVING_NAME), 0x147320, 28)
trace:wininet:INTERNET_SendCallback  end callback().
trace:wininet:GetAddress L"us.battle.net"
trace:wininet:INTERNET_SendCallback  callback(0x42ac80) (0x3 (0x152b40), 004ea0c0, 11 (INTERNET_STATUS_NAME_RESOLVED), 0x147320, 14)
trace:wininet:INTERNET_SendCallback  end callback().
trace:wininet:HTTP_ResolveName resolved L"us.battle.net" to 12.129.242.40
trace:wininet:INTERNET_SendCallback  callback(0x42ac80) (0x3 (0x152b40), 004ea0c0, 20 (INTERNET_STATUS_CONNECTING_TO_SERVER), 0x147320, 14)
trace:wininet:INTERNET_SendCallback  end callback().
err:wininet:NETCON_secure_connect SSL_connect failed: 12157
warn:wininet:HTTP_OpenConnection Couldn't connect securely to host
trace:wininet:HTTP_OpenConnection 12157 <--
trace:wininet:INTERNET_SendCallback  callback(0x42ac80) (0x3 (0x152b40), 004ea0c0, 100 (INTERNET_STATUS_REQUEST_COMPLETE), 0xaee97c, 8)
trace:wininet:DllMain 0x7e3b0000,2,(nil)
trace:wininet:INTERNET_SendCallback  end callback().
trace:wininet:HTTP_HttpSendRequestW <--
trace:wininet:WININET_Release object 0x152b40 refcount = 1
trace:wininet:InternetCloseHandle 0x2

The software is taken from:

https://us.battle.net/account/managemen ... rofile.xml

I believe you have to have a battle.net account and possibly some blizzard software of some sort to get the Beta system checker downloaded.

[Schuttwegraeumer]

Now with the final 1.2 the problems still exists.
Its not possible to run my apps with tha actual versions, i use the 1.0 wine.
Is there a plan to enable SSL like in 1.0x?

[dimesio]

Now with the final 1.2 the problems still exists.
Its not possible to run my apps with tha actual versions, i use the 1.0 wine.
Is there a plan to enable SSL like in 1.0x?

You were told when you first posted to run a regression test and file a bug. Which bug is yours?

[vitamin]

Is there a plan to enable SSL like in 1.0x?

No, there will be no more wine-1.x versions. You need to use wine-1.2. If there were some regressions, file bug and perform regression testing.

[Schuttwegraeumer]

schutti@hell:~/Desktop/X/WINE/wine-git$ git bisect start
schutti@hell:~/Desktop/X/WINE/wine-git$ git bisect good wine-1.0.1
schutti@hell:~/Desktop/X/WINE/wine-git$ git bisect bad wine-1.2
Bisecting: a merge base must be tested
[36def4af0ca85a1d0e66b5207056775bcb3b09ff] Release 1.0.
schutti@hell:~/Desktop/X/WINE/wine-git$

[Schuttwegraeumer]

deleted

[Schuttwegraeumer]

Is that usefull?:

schutti@hell:~/Desktop/X/WINE/wine-git$ git bisect start
schutti@hell:~/Desktop/X/WINE/wine-git$ git bisect good wine-1.0
schutti@hell:~/Desktop/X/WINE/wine-git$ git bisect bad wine-1.2
Bisecting: 11529 revisions left to test after this (roughly 14 steps)
[5f581975dcf83f4f32432137990c72c26b415e3b] wined3d: Introduce surface_init() to handle most of the surface initialization.
schutti@hell:~/Desktop/X/WINE/wine-git$

[John Drescher]

Is that usefull?:

No.

schutti@hell:~/Desktop/X/WINE/wine-git$ git bisect start
schutti@hell:~/Desktop/X/WINE/wine-git$ git bisect good wine-1.0
schutti@hell:~/Desktop/X/WINE/wine-git$ git bisect bad wine-1.2
Bisecting: 11529 revisions left to test after this (roughly 14 steps)
[5f581975dcf83f4f32432137990c72c26b415e3b] wined3d: Introduce surface_init() to handle most of the surface initialization.
schutti@hell:~/Desktop/X/WINE/wine-git$

You need to bisect, compile the bisected wine, then test, then bisect
again till you get to the revision that caused the issue.

John

[James Mckenzie]

Schuttwegraeumer <[email protected]> wrote:

Sent: Aug 3, 2010 11:21 AM
To: [email protected]
Subject: [Wine] Re: How to fix the SSL/https problem?

Is that usefull?:

If you want us to tell you that you are doing this right, yes. For location of errors, no.

schutti@hell:~/Desktop/X/WINE/wine-git$ git bisect start
schutti@hell:~/Desktop/X/WINE/wine-git$ git bisect good wine-1.0

Wow. This is a long time ago (over two years if I'm correct).

schutti@hell:~/Desktop/X/WINE/wine-git$ git bisect bad wine-1.2

This was just released....

Bisecting: 11529 revisions left to test after this (roughly 14 steps)

This means there wer about 23000 revisions between the two releases. The number of steps is just about right, however (2*13).

[5f581975dcf83f4f32432137990c72c26b415e3b] wined3d: Introduce surface_init() to handle most of the surface initialization.

This is just the marker for the current commit (revision).

You have a LONG way to go until the problem is found.

If you can run your program after this bisect, then you have to say that the bisect is good to get to the next revision. If it does not work you have to say that the bisect is bad.

This may take a while, depending on how fast you can configure/make/test program (and you may have to re-install it as well.)

Good luck. When you do find the bad commit, you will have an additional step which is to build Wine 1.2 without the commit. Regression testing states how.

James McKenzie

[Schuttwegraeumer]

That's not really helpfull here.
I never made my own builts because it was not nessesary.
to set up the build environment is not easy for a beginner like me.
It looks like i am the only user with this problem.
that means that the bug will not be found and fixed in usefull time.

I will stop the bug search for a while because the 1.0.1 works well for me.

[Frédéric Delanoy]

On Wed, Aug 4, 2010 at 11:47, Schuttwegraeumer
<[email protected]> wrote:

That's not really helpfull here.  
I never made my own builts because it was not nessesary.

You might try wine 1.3.0 to see if that changes something, and/or use
another WINEPREFIX (check the FAQ
for instructions, particularly sections 7.x) before doing all
regression testing.

to set up the build environment is not easy for a beginner like me.
It looks like i am the only user with this problem.
that means that the bug will not be found and fixed in usefull time.

Well the bug won't be fixed soon if you're the only one with the
problem, and you're not willing to assist with regression testing.
Remember wine is a volunteers project.
If you have problems following the regression docs / if they are not
clear, you can/should always report them, so we can make them better.

I will stop the bug search for a while because the 1.0.1 works well for me.

That's your choice, although 1.2/1.3.0 will probably work better for
many other applications.

Frédéric

[Tw3aky]

In any case, your not the only one with the problem, Schuttwegraeumer, me thinks, cause i'm having it too. Can't be sure though, cause the error appears for me in the winhttp module.

Code: Select all

err:winhttp:netconn_secure_connect couldn't verify server certificate (12157)

This happens when a game i'm trying to get working on OS X 10.6, namely Anno 1404 (a.k.a Dawn of Discovery), tries to connect my online profile.

It appears the latest version (9.0.1) of Codeweavers 'CrossOver Games' has the same issue, cause i couldn't get that part working either. After some reading up on this matter, i realized i'ld have some compiling to do anyway, so decided to install wine with macports and give it a try and see if it worked this way. But no luck.

A pitty you didn't get through the hassle of the regression tests and file a bug report, cause imo you were going pretty well there.

Anyway, as i don't have any reference of a version of wine that does work for this game, i will do some more testing in the next couple of days and if i do find a working version, read up on the regression tests part and file a bug-report myself.

Keep you posted...

[Tw3aky]

Btw, if anyone could give me some tips, they are most welcome.
Also, there appears to be a difference in the spellilng of netcon in the error
message. Notice the netcon in Schuttwegraeumer code snippet and the netconn in mine.