Skip to content

fix: avoid deprecated FIDO2 capability query - #26

Open
UglyEgg wants to merge 1 commit into
ProtonVPN:stablefrom
UglyEgg:contrib/fido2-capability
Open

fix: avoid deprecated FIDO2 capability query#26
UglyEgg wants to merge 1 commit into
ProtonVPN:stablefrom
UglyEgg:contrib/fido2-capability

Conversation

@UglyEgg

@UglyEgg UglyEgg commented Sep 13, 2026

Copy link
Copy Markdown

Problem

ProtonVPNAPI.supports_fido2 calls the deprecated is_fido2_lib_available compatibility property. A normal capability check therefore emits a deprecation warning from inside API Core itself.

Change

Read fido2_lib_available and supports_fido2 from the same current session. The deprecated public property remains available for external callers.

Verification

  • All four library-available/registered-key combinations retain the existing Boolean result.
  • The regression test fails if supports_fido2 consults the deprecated property.
  • Complete upstream suite: 471 passed; two unchanged dependency warnings.
  • Flake8 passes on both changed files.

No networking, authentication flow, or public API behavior changes.

Development disclosure: I developed this patch with material assistance from OpenAI Codex under my direction, then reviewed, tested, and signed the final change.

ProtonVPNAPI.supports_fido2 calls its deprecated
is_fido2_lib_available compatibility property, which emits a warning during a
normal capability check.

Read both capability values from the current session instead. Preserve the
existing truth table and keep the deprecated public property available for
external callers.

Cover all four library/key combinations and fail the regression test if the
deprecated property is consulted.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant