Joan,

Hi, are you using the FreeRDP code base to do your parsing?

Since you say you can detect the CR PDU "more usually" instead of every
time, it sounds quite possible that you are parsing the PDU (or protocol in
general) incorrectly, perhaps getting lost somewhere else in the stream.
Some versions of Windows have slightly out-of-spec CR PDU formats, but the
TPKT headers won't be wrong. Another thing to consider is that if a Windows
RDP client is trying to connect using SSL/TLS, the client may hang up after
it receives the server certificate (so it can present it to the user), then
reconnect again and continue through the entire connection sequence - this
can be confusing

> Maybe should I check other PDU before the x.224?

The CR PDU is the first PDU in the connection sequence, there isn't an
earlier one. Think of T.123 and X.224, etc., as layers in the PDU
structure, as opposed to types of incoming PDUs

Eric

On Mon, Oct 17, 2022 at 1:15 PM Joan Torres via FreeRDP-devel <
freerdp-devel@lists.sourceforge.net> wrote:

> Hello.
> I'm trying to peek the first bytes on a new connection to peek the x.224
> Connection Request PDU to see if there is a routing token.
> Most of the time it works, but sometimes when peeking I don't get the
> expected TPK header with the expected version byte
> on 3 and so on...
>
> I can detect properly the x.224 Connection Request PDU more usually when a
> freerdp client is connecting, but when I get a Windows
> RDP client, on most of the attempts the first bytes are different.
>
> I can't figure out what I am missing.
>
> Please, anyone knows if this makes sense and I am missing something?
> Maybe should I check other PDU before the x.224?
>
> Joan Torres
>
> _______________________________________________
> FreeRDP-devel mailing list
> FreeRDP-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freerdp-devel
>


-- 
☸

_______________________________________________
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Reply via email to