Ask Your Question

Revision history [back]

RFC8613 Object Security for Constrained RESTful Environments defines the Coap Option number 9 as OSCORE Option. Wireshark seems to use the number 21 instead. Is there a never Wireshark version that will follow RFC8613?

RFC8613 Object Security for Constrained RESTful Environments defines the Coap Option number 9 as OSCORE Option. Wireshark seems to use the number 21 instead. Is there a never Wireshark version that will follow RFC8613?

RFC8613 Object Security for Constrained RESTful Environments defines the Coap Option number 9 as OSCORE Option. Wireshark seems to use the number 21 instead. Is there a never Wireshark version that will follow RFC8613?

RFC8613 Object Security for Constrained RESTful Environments defines the Coap Option number 9 as OSCORE Option. Wireshark seems to use the number 21 instead. Is there a never Wireshark version that will follow RFC8613?

RFC8613 Object Security for Constrained RESTful Environments defines the Coap Option number 9 as OSCORE Option. Wireshark seems to use the number 21 instead. Is there a never newer Wireshark version that will follow RFC8613?

RFC8613 Object Security for Constrained RESTful Environments defines the Coap Option number 9 as OSCORE Option. Wireshark seems to use the number 21 instead. Is there a never newer Wireshark version that will follow RFC8613?

RFC8613 Object Security for Constrained RESTful Environments defines the Coap Option number 9 as OSCORE Option. Wireshark seems to use the number 21 instead. Is there a newer Wireshark version that will follow RFC8613?

RFC8613 Object Security for Constrained RESTful Environments defines the Coap Option number 9 as OSCORE Option. Wireshark seems to use the number 21 instead. Is there a newer Wireshark version that will follow RFC8613?

RFC8613 Object Security for Constrained RESTful Environments (OSCORE) defines the Coap Option number 9 as OSCORE Option. Wireshark seems to use the number 21 instead. Is there a newer Wireshark version that will follow RFC8613?

RFC8613 Object Security for Constrained RESTful Environments (OSCORE) defines the Coap Option number 9 as OSCORE Option. Wireshark seems to use the number 21 instead. Is there a newer Wireshark version that will follow RFC8613?

RFC8613 Object Security for Constrained RESTful Environments (OSCORE) defines the Coap Option number 9 as OSCORE Option. Wireshark seems to use the number 21 instead. Is there a newer Wireshark version that will follow RFC8613?

RFC8613 Object Security for Constrained RESTful Environments (OSCORE) defines the Coap Option number 9 as OSCORE Option. Wireshark seems to use the number 21 instead. Is there a newer Wireshark version that will follow RFC8613?

About Wireshark

Version 3.2.1 (v3.2.1-0-gbf38a67724d0)

RFC8613 Object Security for Constrained RESTful Environments (OSCORE) defines the Coap Option number 9 as OSCORE Option. Wireshark seems to use the number 21 instead. Is there a newer Wireshark version that will follow RFC8613?

RFC8613 Object Security for Constrained RESTful Environments (OSCORE) defines the Coap Option number 9 as OSCORE Option. Wireshark seems to use the number 21 instead. Is there a newer Wireshark version that will follow RFC8613?

About Wireshark

Version 3.2.1 (v3.2.1-0-gbf38a67724d0)

Coap Message

No. Time Source Destination Protocol Length Info 17 2.335661 192.168.43.207 185.48.228.213 OSCORE 83 CON, MID:2, POST, / Frame 17: 83 bytes on wire (664 bits), 83 bytes captured (664 bits) on interface \Device\NPF_{F43FBF10-2A51-4899-AD1DDB3D426FB591}, id 0 Ethernet II, Src: Microsof_bb:d6:95 (f0:6e:0b:bb:d6:95), Dst: XiaomiCo_2d:2b:5e (7c:03:ab:2d:2b:5e) Internet Protocol Version 4, Src: 192.168.43.207, Dst: 185.48.228.213 User Datagram Protocol, Src Port: 53647, Dst Port: 5683 Constrained Application Protocol, Confirmable, POST, MID:2 01.. .... = Version: 1 ..00 .... = Type: Confirmable (0) .... 0000 = Token Length: 0 Code: POST (2) Message ID: 2 Opt Name: #1: Uri-Path: (null) Opt Desc: Type 11, Critical, Unsafe 1011 .... = Opt Delta: 11 .... 0000 = Opt Length: 0 Uri-Path: Opt Name: #2: Object-Security: Key ID:102030405060708090a0b0c0, Key ID Context:(null), Partial IV:01234567 Opt Desc: Type 21, Critical, Safe
1010 .... = Opt Delta: 10
.... 1101 = Opt Length: 13 Opt Length extended: 4 0... .... = Non-compressed COSE message: False .0.. .... = Expanded Flag Byte: False
..0. .... = Signature Present: False ...0 .... = Key ID Context Present: False
.... 1... = Key ID Present: True .... .100 = Partial IV Length: 4 Partial IV: 01234567 Key ID: 102030405060708090a0b0c0 End of options marker: 255
[Uri-Path: /]
Encrypted OSCORE Data Payload Desc: application/octet-stream [Payload Length: 16] Data (16 bytes) 0000 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f ................ Data: 000102030405060708090a0b0c0d0e0f
[Length: 16] Object Security for Constrained RESTful Environments [Expert Info (Warning/Undecoded): Security context not set - can't decrypt] [Security context not set - can't decrypt] [Severity level: Warning] [Group: Undecoded]

RFC8613 Object Security for Constrained RESTful Environments (OSCORE) defines the Coap Option number 9 as OSCORE Option. Wireshark seems to use the number 21 instead. Is there a newer Wireshark version that will follow RFC8613?

RFC8613 Object Security for Constrained RESTful Environments (OSCORE) defines the Coap Option number 9 as OSCORE Option. Wireshark seems to use the number 21 instead. Is there a newer Wireshark version that will follow RFC8613?

About Wireshark

Version 3.2.1 (v3.2.1-0-gbf38a67724d0)

  • Coap Message

    No. Time
    Source
    >     Destination Protocol Length Length > Info > > 17 2.335661 192.168.43.207 185.48.228.213 OSCORE 83 CON, MID:2, POST, / > > Frame 17: 83 bytes on wire (664 bits), bits), > 83 bytes captured (664 bits) on interface \Device\NPF_{F43FBF10-2A51-4899-AD1DDB3D426FB591}, on > interface > \Device\NPF_{F43FBF10-2A51-4899-AD1DDB3D426FB591}, > id 0 0 Ethernet II, Src: Src: > Microsof_bb:d6:95 (f0:6e:0b:bb:d6:95), (f0:6e:0b:bb:d6:95), > Dst: XiaomiCo_2d:2b:5e (7c:03:ab:2d:2b:5e) XiaomiCo_2d:2b:5e > (7c:03:ab:2d:2b:5e) Internet Protocol Protocol > Version 4, Src: 192.168.43.207, Dst: 185.48.228.213 Dst: > 185.48.228.213 User Datagram Protocol, Src Port: 53647, Dst Port: Port: 5683 > Constrained Application Protocol, Protocol, > Confirmable, POST, MID:2 > 01.. .... = Version: 1 > ..00 .... = Type: Confirmable (0) > .... 0000 = Token Length: 0 > Code: POST (2) > Message ID: 2 > Opt Name: #1: Uri-Path: (null) > Opt Desc: Type 11, Critical, Unsafe > 1011 .... = Opt Delta: 11 > .... 0000 = Opt Length: 0 > Uri-Path: > Opt Name: #2: Object-Security: Key ID:102030405060708090a0b0c0, Key ID Key ID > Context:(null), Partial IV:01234567 > Opt Desc: Type 21, Critical, Safe
    > 1010 .... = Opt Delta: 10
    > .... 1101 = Opt Length: 13 > Opt Length extended: 4 > 0... .... = Non-compressed COSE message: False > .0.. .... = Expanded Flag Byte: False
    > ..0. .... = Signature Present: False > ...0 .... = Key ID Context Present: False
    > .... 1... = Key ID Present: True > .... .100 = Partial IV Length: 4 > Partial IV: 01234567 > Key ID: 102030405060708090a0b0c0 > End of options marker: 255
    > [Uri-Path: /]
    > Encrypted OSCORE Data > Payload Desc: application/octet-stream > [Payload Length: 16] Data (16 bytes) bytes) 0000 00 01 02 03 04 05 06 07 06 07 > 08 09 0a 0b 0c 0d 0e 0f
    >     ................ Data: Data: > 000102030405060708090a0b0c0d0e0f
    > [Length: 16] Object Security for for > Constrained RESTful Environments Environments
    >     [Expert Info (Warning/Undecoded): (Warning/Undecoded): > Security context not set - can't can't > decrypt] > [Security context not set - can't decrypt] > [Severity level: Warning] > [Group: Undecoded]

RFC8613 Object Security for Constrained RESTful Environments (OSCORE) defines the Coap Option number 9 as OSCORE Option. Wireshark seems to use the number 21 instead. Is there a newer Wireshark version that will follow RFC8613?

RFC8613 Object Security for Constrained RESTful Environments (OSCORE) defines the Coap Option number 9 as OSCORE Option. Wireshark seems to use the number 21 instead. Is there a newer Wireshark version that will follow RFC8613?

About Wireshark

Version 3.2.1 (v3.2.1-0-gbf38a67724d0)

  • Coap Message

    No. Time
    Source
    >     Destination Protocol Length > Info > > Length Info

    17 2.335661 192.168.43.207 185.48.228.213 OSCORE 83 CON, MID:2, POST, / > > /

    Frame 17: 83 bytes on wire (664 bits), > bits), 83 bytes captured (664 bits) on > interface > \Device\NPF_{F43FBF10-2A51-4899-AD1DDB3D426FB591}, > on interface \Device\NPF_{F43FBF10-2A51-4899-AD1DDB3D426FB591}, id 0 0

    Ethernet II, Src: > Src: Microsof_bb:d6:95 (f0:6e:0b:bb:d6:95), > (f0:6e:0b:bb:d6:95), Dst: XiaomiCo_2d:2b:5e > (7c:03:ab:2d:2b:5e) XiaomiCo_2d:2b:5e (7c:03:ab:2d:2b:5e)

    Internet Protocol > Protocol Version 4, Src: 192.168.43.207, Dst: > 185.48.228.213 Dst: 185.48.228.213

    User Datagram Protocol, Src Port: 53647, Dst Port: Port: 5683 >

    Constrained Application Protocol, > Protocol, Confirmable, POST, MID:2 > MID:2

    01.. .... = Version: 1 > 1

    ..00 .... = Type: Confirmable (0) > (0)

    .... 0000 = Token Length: 0 > 0

    Code: POST (2) > (2)

    Message ID: 2 > 2

    Opt Name: #1: Uri-Path: (null) > (null)

    Opt Desc: Type 11, Critical, Unsafe > Unsafe

    1011 .... = Opt Delta: 11 >

    .... 0000 = Opt Length: 0 > 0

    Uri-Path: >

    Opt Name: #2: Object-Security: Key ID:102030405060708090a0b0c0, Key ID > Key ID Context:(null), Partial IV:01234567 > IV:01234567

    Opt Desc: Type 21, Critical, Safe
    >     Safe

    1010 .... = Opt Delta: 10
    >

    .... 1101 = Opt Length: 13 > 13

    Opt Length extended: 4 > 4

    0... .... = Non-compressed COSE message: False > False

    .0.. .... = Expanded Flag Byte: False
    >

    ..0. .... = Signature Present: False >

    ...0 .... = Key ID Context Present: False
    >     False

    .... 1... = Key ID Present: True >

    .... .100 = Partial IV Length: 4 > 4

    Partial IV: 01234567 >

    Key ID: 102030405060708090a0b0c0 > 102030405060708090a0b0c0

    End of options marker: 255
    >     255

    [Uri-Path: /]
    >

    Encrypted OSCORE Data > Data

    Payload Desc: application/octet-stream > application/octet-stream

    [Payload Length: 16]

    Data (16 bytes) bytes)

    0000 00 01 02 03 04 05 06 07 > 06 07 08 09 0a 0b 0c 0d 0e 0f
    > ................ Data: > 000102030405060708090a0b0c0d0e0f
    >     ................

    Data: 000102030405060708090a0b0c0d0e0f

    [Length: 16] Object Security for > for Constrained RESTful Environments
    >     Environments

    [Expert Info (Warning/Undecoded): > (Warning/Undecoded): Security context not set - can't > decrypt] > can't decrypt]

    [Security context not set - can't decrypt] > decrypt]

    [Severity level: Warning] > Warning]

    [Group: Undecoded]
click to hide/show revision 10
None

updated 2020-03-23 01:05:56 +0000

Guy Harris gravatar image

RFC8613 Object Security for Constrained RESTful Environments (OSCORE) defines the Coap Option number 9 as OSCORE Option. Wireshark seems to use the number 21 instead. Is there a newer Wireshark version that will follow RFC8613?

RFC8613 Object Security for Constrained RESTful Environments (OSCORE) defines the Coap Option number 9 as OSCORE Option. Wireshark seems to use the number 21 instead. Is there a newer Wireshark version that will follow RFC8613?

About Wireshark

Version 3.2.1 (v3.2.1-0-gbf38a67724d0)

 No.     Time           Source                Destination           Protocol Length Info
 
Info
      17 2.335661       192.168.43.207        185.48.228.213        OSCORE   83     CON, MID:2, POST, /
 
/
 Frame 17: 83 bytes on wire (664 bits), 83 bytes captured (664 bits) on interface \Device\NPF_{F43FBF10-2A51-4899-AD1DDB3D426FB591}, id 0
 
0
 Ethernet II, Src: Microsof_bb:d6:95 (f0:6e:0b:bb:d6:95), Dst: XiaomiCo_2d:2b:5e (7c:03:ab:2d:2b:5e)
 
(7c:03:ab:2d:2b:5e)
 Internet Protocol Version 4, Src: 192.168.43.207, Dst: 185.48.228.213
 
185.48.228.213
 User Datagram Protocol, Src Port: 53647, Dst Port: 5683 
 
  Constrained Application Protocol, Confirmable, POST, MID:2
 
MID:2
     01.. .... = Version: 1
 
1
     ..00 .... = Type: Confirmable (0)
 
(0)
     .... 0000 = Token Length: 0
 
0
     Code: POST (2)
 
(2)
     Message ID: 2
 
2
     Opt Name: #1: Uri-Path: (null)
 
(null)
         Opt Desc: Type 11, Critical, Unsafe
 
Unsafe
         1011 .... = Opt Delta: 11 
 
          .... 0000 = Opt Length: 0
 
0
         Uri-Path: 
 
      Opt Name: #2: Object-Security: Key ID:102030405060708090a0b0c0, Key ID Context:(null), Partial IV:01234567
 
IV:01234567
         Opt Desc: Type 21, Critical, Safe
 
Safe    
         1010 .... = Opt Delta: 10  
 
          .... 1101 = Opt Length: 13
 
13 
         Opt Length extended: 4
 
4
         0... .... = Non-compressed COSE message: False
 
False
         .0.. .... = Expanded Flag Byte: False    
 
          ..0. .... = Signature Present: False 
 
          ...0 .... = Key ID Context Present: False
 
False  
         .... 1... = Key ID Present: True 
 
          .... .100 = Partial IV Length: 4
 
4 
         Partial IV: 01234567 
 
          Key ID: 102030405060708090a0b0c0
 
102030405060708090a0b0c0
     End of options marker: 255
 
255  
     [Uri-Path: /]  
 
      Encrypted OSCORE Data
 
Data
         Payload Desc: application/octet-stream
 
application/octet-stream
         [Payload Length: 16] 
 
  Data (16 bytes)
 
bytes)
 0000  00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f   ................
 
................ 
    Data: 000102030405060708090a0b0c0d0e0f
 
000102030405060708090a0b0c0d0e0f  
    [Length: 16] Object Security for Constrained RESTful Environments
 
Environments
    [Expert Info (Warning/Undecoded): Security context not set - can't decrypt]
 
decrypt]
         [Security context not set - can't decrypt]
 
decrypt]
         [Severity level: Warning]
 
Warning]
         [Group: Undecoded]
Undecoded]