From 5f68d2ef09c2625d460013222dd4fa28fff8927f Mon Sep 17 00:00:00 2001 From: Alexandre CHAZAL Date: Thu, 14 Mar 2024 15:32:54 +0100 Subject: [PATCH] fix(xfactor): change wrong image paths --- posts/xfactor2/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/posts/xfactor2/index.md b/posts/xfactor2/index.md index 2222241..4f1fca9 100644 --- a/posts/xfactor2/index.md +++ b/posts/xfactor2/index.md @@ -57,7 +57,7 @@ If you want more informations about CTAP and such, please click [here](https://f ## Packet buildin' Thanks to the dissector, I can now at least see the U2F conversations. -![img](packet-building.png) +![img](./images/packet-building.png) That sure is a lot of _CTAPHID Initialization_ and _CTAPHID Continuation_ packets! Judging from what's being said [here](https://fidoalliance.org/specs/fido-v2.0-id-20180227/fido-client-to-authenticator-protocol-v2.0-id-20180227.html#usb-message-and-packet-structure), an _CTAPHID Initialization packet_ comes first and one or more _CTAPHID Continuation packets_ follow to complete the payload. @@ -83,7 +83,7 @@ Using *Short encoding* would make them fit on 1 byte, but that would reduce the ### Responses Here's a response (that contains data, and that is not always the case): -![img](responses.png) +![img](./images/responses.png) As you can see, a responses are a bit simpler: - **Response data**: **LE** bytes if specified, n bytes if not