Le 16/06/2021 à 16:36, David Perry a écrit :
Sorry to drag up an old topic, but I've been thinking about this:
Message: 5
Date: Sat, 29 May 2021 09:32:29 +0200
From: Anders Broman
[...]
I wasn't around for that discussion so I don't know the reasons, but how
does this sound as a refined
On Wed, Jun 16, 2021 at 2:48 PM Anders Broman via Wireshark-dev
wrote:
>
>
>
> -Original Message-
> From: Wireshark-dev On Behalf Of Isaac
> Boukris
> Sent: den 16 juni 2021 12:52
> To: wireshark-dev@wireshark.org
> Subject: [Wireshark-dev] ASN1: How to display an octet-string as UTF16
Sorry to drag up an old topic, but I've been thinking about this:
Message: 5
Date: Sat, 29 May 2021 09:32:29 +0200
From: Anders Broman
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Calling a dissector: Type for data
parameter
Message-ID:
Content-Type:
-Original Message-
From: Wireshark-dev On Behalf Of Isaac
Boukris
Sent: den 16 juni 2021 12:52
To: wireshark-dev@wireshark.org
Subject: [Wireshark-dev] ASN1: How to display an octet-string as UTF16 LE
Hello,
I'd like to add the following asn1 struct to the credssp dissector
Hello,
I'd like to add the following asn1 struct to the credssp dissector
(following MR 3020):
TSRemoteGuardPackageCred ::= SEQUENCE {
packageName [0] OCTET STRING,
credBuffer [1] OCTET STRING
}
It gets displayed like this:
logonCred
packageName:
