August 2023 - Wine-Bugs - list.winehq.org

[Bug 55402] CMD '!var!' not working in 'if' statement

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55402 --- Comment #3 from Dmitry Sokolov <mr.dmitry.sokolov(a)gmail.com> --- A similar script exists in Visual Studio to init dev env -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

Aug. 4, 2023

[Bug 55402] CMD '!var!' not working in 'if' statement

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55402 --- Comment #2 from Dmitry Sokolov <mr.dmitry.sokolov(a)gmail.com> --- Created attachment 74963 --> https://bugs.winehq.org/attachment.cgi?id=74963 test_delayed_expansion.cmd.exp -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

Aug. 4, 2023

[Bug 55402] CMD '!var!' not working in 'if' statement

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55402 --- Comment #1 from Dmitry Sokolov <mr.dmitry.sokolov(a)gmail.com> --- Created attachment 74962 --> https://bugs.winehq.org/attachment.cgi?id=74962 test_delayed_expansion.cmd -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

Aug. 4, 2023

[Bug 55402] New: CMD '!var!' not working in 'if' statement

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55402 Bug ID: 55402 Summary: CMD '!var!' not working in 'if' statement Product: Wine Version: 8.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: mr.dmitry.sokolov(a)gmail.com Distribution: --- The command not working set var=qwe if "!var!"=="" ... ACTUAL The script (attached) produces wrong output EXPECTED See the output in .exp file (attached) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

Aug. 4, 2023

[Bug 55401] CMD 'for loop' params are not recognized

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55401 --- Comment #3 from Dmitry Sokolov <mr.dmitry.sokolov(a)gmail.com> --- A similar script is existed in Visual Studio Native Tools Command Prompt. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

Aug. 4, 2023

[Bug 55401] CMD 'for loop' params are not recognized

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55401 --- Comment #2 from Dmitry Sokolov <mr.dmitry.sokolov(a)gmail.com> --- Created attachment 74961 --> https://bugs.winehq.org/attachment.cgi?id=74961 test_for_loop_params.cmd.exp -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

Aug. 4, 2023

[Bug 55401] CMD 'for loop' params are not recognized

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55401 --- Comment #1 from Dmitry Sokolov <mr.dmitry.sokolov(a)gmail.com> --- Created attachment 74960 --> https://bugs.winehq.org/attachment.cgi?id=74960 test_for_loop_params.cmd -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

Aug. 4, 2023

[Bug 55401] New: CMD 'for loop' params are not recognized

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55401 Bug ID: 55401 Summary: CMD 'for loop' params are not recognized Product: Wine Version: 8.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: mr.dmitry.sokolov(a)gmail.com Distribution: --- The command not working for %%1 in (..) ACTUAL Cmd script (attached) produces no output. EXPECTED See attached .exp file. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

Aug. 4, 2023

[Bug 55383] Avatar Star Taiwan: Black 3d textures on characters inside game rounds

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55383 Ekiru <qraique(a)protonmail.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Avatar Star Taiwan Black |Avatar Star Taiwan: Black |3d textures on characters |3d textures on characters |inside game rounds |inside game rounds -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

Aug. 4, 2023

[Bug 55304] Kerberos authentication stopped to work after PE wldap32 conversion

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55304 --- Comment #6 from Hans Leidekker <hans(a)meelstraat.net> --- (In reply to Dmitry Timoshkov from comment #2) > (In reply to Hans Leidekker from comment #1) > > SSF is used by ldap_int_sasl_bind() to determine if the SASL security layer > > should be used at all. This page documents it as representing the key size > > for values > 1: > > > > https://docs.oracle.com/cd/E19120-01/open.solaris/819-2145/sasl.intro-44/ > > index.html > > libldap simply checks for a not zero ssf value: > https://github.com/openldap/openldap/blob/master/libraries/libldap/cyrus. > c#L745 That's an implementation detail we shouldn't rely on. > > I don't understand why the trailer size depends on the server since we have > > always depended on a constant trailer size. Is that because of a difference > > between Samba and AD? > > I've tested with Microsoft and Samba servers and both of them use 60 for > actual encryped data, and decrypting with 64 abviously doesn't work. In the > same time QueryContextAttributesA(SECPKG_ATTR_SIZES) returns 64 for the > connection. > > > I can find references for Windows changing from 12000 max token size to > > 48000 but not 48256. Where does it come from? > > It comes from a test that calls QueryContextAttributesA(SECPKG_ATTR_SIZES) > under Windows 10 for the Samba server. Hmm, maybe it's not decrypting in-place? This used to work without querying the trailer size from the context. > > Also note that your changes to sasl_decode() and sasl_encode() break NTLM. > > Do you have a sample code that breaks that could be used for testing > purposes? I modified the wldap32 test to connect to an AD LDAP server and hacked the Kerberos dll to return an error so that Negotiate falls back to NTLM. Essentially it's this: ldap_bind_sA( ld, NULL, (char *)&auth_id, LDAP_AUTH_NEGOTIATE ); -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

Aug. 4, 2023