http://bugs.winehq.org/show_bug.cgi?id=60214 Erik Hill <erik.hill0987@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|bcrypt: |bcrypt: |BCryptExportKey/BCryptImpor |BCryptExportKey/BCryptImpor |tKeyPair do not support |tKeyPair lack |BCRYPT_OPAQUE_KEY_BLOB for |BCRYPT_OPAQUE_KEY_BLOB |asymmetric keys, breaking |support for asymmetric keys |modern Steam login | --- Comment #1 from Erik Hill <erik.hill0987@gmail.com> --- Correction to this report. I over-attributed the cause. The OpaqueKeyBlob export gap itself is real (the fixme is definitive, and opaque asymmetric export/import is genuinely unimplemented). But I did NOT prove this gap is what breaks modern Steam login, and I should not have framed it that way. Gcenx, who maintains the macOS Wine packages, has the CURRENT Steam client working with a rendering fix alone: a small steamwebhelper wrapper forcing --in-process-gpu so DXMT's Metal renderer handles the in-process swapchain. That suggests the rendering path, not this crypto gap, may be the actual login blocker. My attempt to isolate which wall gates login was inconclusive: with DXMT + the in-process-gpu wrapper on stock 11.15, rendering failed a different way (GPU context lost) before login was ever attempted, so the crypto path never ran. I have retitled this to describe the verifiable API gap rather than assert a Steam root cause. Apologies for the noise; the opaque asymmetric export/import is still a genuine gap worth closing on its own merits. -- 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.