https://bugs.winehq.org/show_bug.cgi?id=52330
Bug ID: 52330 Summary: iZotope software authorization process fails Product: Wine-staging Version: 7.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: christian.frech@protonmail.com CC: leslie_alistair@hotmail.com, z.figura12@gmail.com Distribution: ---
Created attachment 71492 --> https://bugs.winehq.org/attachment.cgi?id=71492 journalctl log during authorization process
Authorizing iZotope software will result in an error. According to the iZotope Support, the attempt is visible, but the local application did not recognize that. Also see attachment.
https://bugs.winehq.org/show_bug.cgi?id=52330
Christian Frech christian.frech@protonmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |christian.frech@protonmail. | |com
https://bugs.winehq.org/show_bug.cgi?id=52330
Christian Frech christian.frech@protonmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |ArchLinux
https://bugs.winehq.org/show_bug.cgi?id=52330
Christian Frech christian.frech@protonmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |https://support.izotope.com | |/hc/en-us/articles/36002558 | |6834-Welcome-to-iZotope-Pro | |duct-Portal
https://bugs.winehq.org/show_bug.cgi?id=52330
--- Comment #1 from Zebediah Figura z.figura12@gmail.com --- (In reply to Christian Frech from comment #0)
Authorizing iZotope software will result in an error. According to the iZotope Support, the attempt is visible, but the local application did not recognize that. Also see attachment.
Sorry, can you please clarify what you mean by "the attempt is visible"?
Is this something that can be reproduced by entering a bogus serial number?
Does the bug occur with upstream (non-staging) wine?
https://bugs.winehq.org/show_bug.cgi?id=52330
--- Comment #2 from Christian Frech christian.frech@protonmail.com --- Hi Zebediah,
by "the attempt is visible" I meant, that the analyst from the iZotope support is able to see some communication coming from my client at their back end. So, there is definitely network communication going on, which I suspected at first wouldn't be the case.
A bogus S/N will probably not work, but you can replicate that with a freebie from iZotope (for example: https://www.izotope.com/en/products/vocal-doubler.html). Otherwise I'm happy to provide my serial number. You will need an account and the iZotope Product Portal (both free of charge).
The outcome with wine instead of wine-staging is the same.
https://bugs.winehq.org/show_bug.cgi?id=52330
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Product|Wine-staging |Wine Component|-unknown |-unknown CC|leslie_alistair@hotmail.com |
https://bugs.winehq.org/show_bug.cgi?id=52330
--- Comment #3 from Zebediah Figura z.figura12@gmail.com --- I can't seem to get the Product Portal to display anything, using upstream wine 7.0-rc4. Disabling libglesv2 and installing corefonts doesn't help. Are there other workarounds I need to apply?
https://bugs.winehq.org/show_bug.cgi?id=52330
--- Comment #4 from Zebediah Figura z.figura12@gmail.com --- (In reply to Christian Frech from comment #2)
by "the attempt is visible" I meant, that the analyst from the iZotope support is able to see some communication coming from my client at their back end. So, there is definitely network communication going on, which I suspected at first wouldn't be the case.
That's nice that they were willing to provide support on this issue. Are there any other details from the support ticket that can be shared, by chance?
https://bugs.winehq.org/show_bug.cgi?id=52330
--- Comment #5 from Christian Frech christian.frech@protonmail.com --- Created attachment 71496 --> https://bugs.winehq.org/attachment.cgi?id=71496 Transcript of live chat with iZotope support
https://bugs.winehq.org/show_bug.cgi?id=52330
--- Comment #6 from Christian Frech christian.frech@protonmail.com --- (In reply to Zebediah Figura from comment #4)
(In reply to Christian Frech from comment #2)
by "the attempt is visible" I meant, that the analyst from the iZotope support is able to see some communication coming from my client at their back end. So, there is definitely network communication going on, which I suspected at first wouldn't be the case.
That's nice that they were willing to provide support on this issue. Are there any other details from the support ticket that can be shared, by chance?
I attached the transcript, but I don't think it will be of any help. I have not applied any workaround to get the iZotope Product Portal working. I always work with vanilla setups, if possible.
Maybe it's because I have the google noto-fonts (AUR: noto-fonts) installed? I will attach a text file with all packages I have installed and a screenshot what it should look like.
https://bugs.winehq.org/show_bug.cgi?id=52330
--- Comment #7 from Christian Frech christian.frech@protonmail.com --- Created attachment 71497 --> https://bugs.winehq.org/attachment.cgi?id=71497 Printout of all installed packages on my system
https://bugs.winehq.org/show_bug.cgi?id=52330
--- Comment #8 from Christian Frech christian.frech@protonmail.com --- Created attachment 71498 --> https://bugs.winehq.org/attachment.cgi?id=71498 Product Portal first time login
https://bugs.winehq.org/show_bug.cgi?id=52330
--- Comment #9 from Christian Frech christian.frech@protonmail.com --- Created attachment 71499 --> https://bugs.winehq.org/attachment.cgi?id=71499 Overview when signed in
https://bugs.winehq.org/show_bug.cgi?id=52330
--- Comment #10 from Zebediah Figura z.figura12@gmail.com --- I mean things like winetricks verbs or registry changes, though; have you applied any of those?
https://bugs.winehq.org/show_bug.cgi?id=52330
--- Comment #11 from Christian Frech christian.frech@protonmail.com --- (In reply to Zebediah Figura from comment #10)
I mean things like winetricks verbs or registry changes, though; have you applied any of those?
Nope, all left as is. I have winetricks installed, but I never used it. If you tell me your platform and your wine version I'm happy to try this in a VM or on a dedicated machine.
https://bugs.winehq.org/show_bug.cgi?id=52330
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |hans@meelstraat.net Component|-unknown |crypt32
--- Comment #12 from Zebediah Figura z.figura12@gmail.com --- I managed to get it to run with just `winetricks corefonts` and also starting the start menu .lnk rather than trying to manually run the executable. Not sure if one of those alone was necessary.
Anyway, I can reproduce an error trying to authorize the free serial for Vocal Doubler. +crypt plus some extra traces yields this:
0114:0118:trace:crypt:PFXImportCertStore pfx 000000000011BE70, password L"", flags 0. 0114:0118:trace:crypt:gnutls_log <9> salt.size: 8 0114:0118:trace:crypt:gnutls_log <9> iterationCount: 2048 0114:0118:trace:crypt:gnutls_log <3> ASSERT: pkcs12.c[gnutls_pkcs12_simple_parse]:1688 GnuTLS error: The requested data were not available.
I'm not an expert in certificate nonsense, but from what I can tell, it fails because we are trying to pass a PKCS #12 blob to gnutls_pkcs12_simple_parse() that doesn't actually have a private key in it, only a certificate.
Given that (and assuming that PFXImportCertStore() is supposed to handle this), I guess the question is whether gnutls_pkcs12_simple_parse() is supposed to handle this—the documentation is not exactly clear—and if not I guess we need to parse things more manually.
Hans, would you mind checking this diagnosis to make sure it sounds sane?
https://bugs.winehq.org/show_bug.cgi?id=52330
--- Comment #13 from Hans Leidekker hans@meelstraat.net --- (In reply to Zebediah Figura from comment #12)
Given that (and assuming that PFXImportCertStore() is supposed to handle this), I guess the question is whether gnutls_pkcs12_simple_parse() is supposed to handle this—the documentation is not exactly clear—and if not I guess we need to parse things more manually.
Hans, would you mind checking this diagnosis to make sure it sounds sane?
GnuTLS source confirms that it expects to find a private key in the PKCS12 blob. Maybe they would accept a patch to make the key optional. If not it may be possible to decode the blob using the lower level PKCS12 Bag functions. Otherwise we'll have to do it all by hand I guess.
https://bugs.winehq.org/show_bug.cgi?id=52330
Jonathan Romano jonathan@luxaritas.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jonathan@luxaritas.com