Bug 4564 - Add a tool to report CSP name for a specific ATR
Summary: Add a tool to report CSP name for a specific ATR
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: | WTS Tools (deprecated) (show other bugs)
Version: 4.0.0
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.10.0
Assignee: Henrik Andersson
Depends on:
Blocks: 4565
  Show dependency treegraph
Reported: 2013-03-25 14:45 CET by Henrik Andersson
Modified: 2019-02-07 15:51 CET (History)
0 users

See Also:
Acceptance Criteria:


Description Henrik Andersson cendio 2013-03-25 14:45:02 CET
In Microsoft's sc_minidriver_spec there is a Smartcard Plug and Play Appendix A, which discusses a "pairing process" for smartcard:

- Get the ATR from the smart card.
  - Iterate through entries in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Calais\SmartCards registry key and do the following:
    - Apply ATRMask subkey value that is stored in the registry to the ATR that was acquired from the smart card.
    - Compare the masked ATR value to the ATR subkey value that is stored in the registry.
    - If the two ATR values match, stop processing and pair the corresponding minidriver with the smart card.

When a match has been made, the Crypt Provider registry key contains the CSP name.

If we go this way we can have tl-run-rdesktop to query the nrpe agent on a WTS server to retrieve the correct CSP name to use for SSO.
Comment 1 Pierre Ossman cendio 2019-02-07 15:43:56 CET
rdesktop (and associated tools) is being removed from the ThinLinc product.

Note You need to log in before you can comment on or make changes to this bug.