[Bug 45344] New: AcquireCredentialsHandle functions should be implemented inside sspicli
https://bugs.winehq.org/show_bug.cgi?id=45344
Bug ID: 45344 Summary: AcquireCredentialsHandle functions should be implemented inside sspicli Product: Wine Version: 3.9 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: secur32 Assignee: wine-bugs@winehq.org Reporter: dark.shadow4@web.de Distribution: ---
Currently the AcquireCredentialsHandle functions are implemented inside secur32, and sspicli forwards them to secur32. However, when using native secur32, that results in a stack-overflow. Most likely on windows the functions are implemented in sspicli and secur32 forwards them.
Most likely affects other functions, too.
Application I tested it with (needs winXP): https://www.vavoo.tv/software/get?platform=win32&processor=i386&type...
https://bugs.winehq.org/show_bug.cgi?id=45344
--- Comment #1 from Dmitry Timoshkov dmitry@baikal.ru --- Using native secur32.dll under Wine is not going to work for various reasons.
Why do you need that?
https://bugs.winehq.org/show_bug.cgi?id=45344
--- Comment #2 from Fabian Maurer dark.shadow4@web.de ---
Using native secur32.dll under Wine is not going to work for various reasons.
How so? I didn't know, I just tried some native DLLs since I saw FIXMEs related to it - and I didn't expect the native DLLs to result in a stackoverflow.
So you mean that's a non issue? I thought I could just drop in secur32 and it should work.
https://bugs.winehq.org/show_bug.cgi?id=45344
--- Comment #3 from Dmitry Timoshkov dmitry@baikal.ru --- (In reply to Fabian Maurer from comment #2)
How so? I didn't know, I just tried some native DLLs since I saw FIXMEs related to it - and I didn't expect the native DLLs to result in a stackoverflow.
If it breaks you get to keep the pieces.
So you mean that's a non issue? I thought I could just drop in secur32 and it should work.
To avoid too lengthy explanations just consider secur32.dll of the same level as kernel32, user32 and ntdll which can't be replaced.
In general the problems related to using a native DLL shouldn't lead to a winehq bug report, or rather such bug reports should be closed outright.
https://bugs.winehq.org/show_bug.cgi?id=45344
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|NEW |RESOLVED
--- Comment #4 from Fabian Maurer dark.shadow4@web.de ---
In general the problems related to using a native DLL shouldn't lead to a winehq bug report, or rather such bug reports should be closed outright.
A crash when using a native DLL can also indicate a bug inside wine though, like a wrongly called function - already had an issue like that.
To avoid too lengthy explanations just consider secur32.dll of the same level as kernel32, user32 and ntdll which can't be replaced.
I see, thanks for clarification. Then we probably don't care about the forwarding either. Would it make sense to add it to the list of dlls where winecfg warns you about changing the load order?
https://bugs.winehq.org/show_bug.cgi?id=45344
--- Comment #5 from Dmitry Timoshkov dmitry@baikal.ru --- (In reply to Fabian Maurer from comment #4)
Would it make sense to add it to the list of dlls where winecfg warns you about changing the load order?
Sometimes it's useful to let people learn something the hard way :)
https://bugs.winehq.org/show_bug.cgi?id=45344
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #6 from Austin English austinenglish@gmail.com --- (In reply to Dmitry Timoshkov from comment #5)
(In reply to Fabian Maurer from comment #4)
Would it make sense to add it to the list of dlls where winecfg warns you about changing the load order?
Sometimes it's useful to let people learn something the hard way :)
Sure :), but for support reasons it's better to have a warning sign to prevent at least some accidents ;).
https://source.winehq.org/patches/data/148002
https://bugs.winehq.org/show_bug.cgi?id=45344
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |austinenglish@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=45344
--- Comment #7 from Austin English austinenglish@gmail.com --- (In reply to Austin English from comment #6)
(In reply to Dmitry Timoshkov from comment #5)
(In reply to Fabian Maurer from comment #4)
Would it make sense to add it to the list of dlls where winecfg warns you about changing the load order?
Sometimes it's useful to let people learn something the hard way :)
Sure :), but for support reasons it's better to have a warning sign to prevent at least some accidents ;).
https://source.winehq.org/git/wine.git/commitdiff/53cc1da18f3683197fa5e62c2f...
-
wine-bugs＠winehq.org