Skip to content

Commit ae62afb

Browse files
committed
docs(remove obsolete references):
1 parent db4fb36 commit ae62afb

File tree

4 files changed

+12
-12
lines changed

4 files changed

+12
-12
lines changed

docs/users-manual/application-piv/private-keys.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -112,7 +112,7 @@ YubiKey-formatted private key to a `PrivateKeyInfo` or PEM format.
112112
Unfortunately, PIV does not define its own format of encoding private keys, although
113113
Yubico has defined an encoding that is very similar to the PIV public key format.
114114
However, the SDK's PIV application APIs that work with a private keys require them to be
115-
instances of the [PivPrivateKey](xref:Yubico.YubiKey.Piv.PivPrivateKey) class.
115+
instances of the `PivPrivateKey` class.
116116
Hence, when importing a private key into a YubiKey, your application will need to be able
117117
to "convert" from `PrivateKeyInfo` or PEM to `PivPrivateKey`.
118118

docs/users-manual/application-u2f/u2f-commands.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -111,9 +111,9 @@ All YubiKeys with the FIDO U2F application.
111111

112112
### SDK classes
113113

114-
[GetDeviceInfoCommand](xref:Yubico.YubiKey.U2f.Commands.GetDeviceInfoCommand)
114+
[GetPagedDeviceInfoCommand](xref:Yubico.YubiKey.U2f.Commands.GetPagedDeviceInfoCommand)
115115

116-
[GetDeviceInfoResponse](xref:Yubico.YubiKey.U2f.Commands.GetDeviceInfoResponse)
116+
[GetPagedDeviceInfoResponse](xref:Yubico.YubiKey.U2f.Commands.GetPagedDeviceInfoResponse)
117117

118118
### Input
119119

docs/users-manual/getting-started/whats-new.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -152,12 +152,12 @@ Bug fixes:
152152

153153
Miscellaneous:
154154
- The way that YubiKey device info is read by the SDK has changed, and as a result, the following GetDeviceInfo command classes have been deprecated ([#91](https://github.com/Yubico/Yubico.NET.SDK/pull/91)):
155-
- [Yubico.YubiKey.Management.Commands.GetDeviceInfoCommand](xref:Yubico.YubiKey.Management.Commands.GetDeviceInfoCommand)
156-
- [Yubico.YubiKey.Otp.Commands.GetDeviceInfoCommand](xref:Yubico.YubiKey.Otp.Commands.GetDeviceInfoCommand)
157-
- [Yubico.YubiKey.U2f.Commands.GetDeviceInfoCommand](xref:Yubico.YubiKey.U2f.Commands.GetDeviceInfoCommand)
158-
- [Yubico.YubiKey.Management.Commands.GetDeviceInfoResponse](xref:Yubico.YubiKey.Management.Commands.GetDeviceInfoResponse)
159-
- [Yubico.YubiKey.Otp.Commands.GetDeviceInfoResponse](xref:Yubico.YubiKey.Otp.Commands.GetDeviceInfoResponse)
160-
- [Yubico.YubiKey.U2f.Commands.GetDeviceInfoResponse](xref:Yubico.YubiKey.U2f.Commands.GetDeviceInfoResponse)
155+
- `Yubico.YubiKey.Management.Commands.GetDeviceInfoCommand`
156+
- `Yubico.YubiKey.Otp.Commands.GetDeviceInfoCommand`
157+
- `Yubico.YubiKey.U2f.Commands.GetDeviceInfoCommand`
158+
- `Yubico.YubiKey.Management.Commands.GetDeviceInfoResponse`
159+
- `Yubico.YubiKey.Otp.Commands.GetDeviceInfoResponse`
160+
- `Yubico.YubiKey.U2f.Commands.GetDeviceInfoResponse`
161161
- Integration test guardrails have been added to ensure tests are done only on specified keys. ([#100](https://github.com/Yubico/Yubico.NET.SDK/pull/100)).
162162
- Unit tests were run on all platforms in CI ([#80](https://github.com/Yubico/Yubico.NET.SDK/pull/80)).
163163

@@ -260,8 +260,8 @@ Features:
260260
class.
261261

262262
- **SCP03 architecture**. The process for building an SCP03 connection was updated.
263-
The previous method ([Yubico.YubiKey.YubiKeyDeviceExtensions.WithScp03()](xref:Yubico.YubiKey.YubiKeyDeviceExtensions.WithScp03%28Yubico.YubiKey.YubiKeyDevice%2CYubico.YubiKey.Scp03.StaticKeys%29)) is now deprecated, and
264-
the new method ([Yubico.YubiKey.IYubiKeyDevice.ConnectScp03()](xref:Yubico.YubiKey.IYubiKeyDevice.ConnectScp03%28Yubico.YubiKey.YubiKeyApplication%2CYubico.YubiKey.Scp03.StaticKeys%29)) simply requires passing in the SCP03 key set to the
263+
The previous method (`Yubico.YubiKey.YubiKeyDeviceExtensions.WithScp03()`) is now deprecated, and
264+
the new method (`Yubico.YubiKey.IYubiKeyDevice.ConnectScp03()` simply requires passing in the SCP03 key set to the
265265
PivSession constructor. It is also possible to build an
266266
IYubiKeyConnection that uses SCP03 via [Yubico.YubiKey.Piv.PivSession()](xref:Yubico.YubiKey.Piv.PivSession.%23ctor%28Yubico.YubiKey.IYubiKeyDevice%2CYubico.YubiKey.Scp03.StaticKeys%29).
267267

docs/users-manual/sdk-programming-guide/secure-channel-protocol.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -252,7 +252,7 @@ The next sections will detail specific key management and protocol details for b
252252

253253
### Static keys structure
254254

255-
SCP03 relies on a set of shared, secret, symmetric cryptographic keys. Each key set consists of three 16-byte AES-128 keys encapsulated in the [`StaticKeys`](xref:Yubico.YubiKey.Scp03.StaticKeys) class:
255+
SCP03 relies on a set of shared, secret, symmetric cryptographic keys. Each key set consists of three 16-byte AES-128 keys encapsulated in the [`StaticKeys`](xref:Yubico.YubiKey.Scp.StaticKeys) class:
256256

257257
- Channel encryption key (Key-ENC)
258258
- Channel MAC key (Key-MAC)

0 commit comments

Comments
 (0)