Wednesday 15 May 2013

desktop - Lync RDP parsing -


I am making RDP client for distributing desktops from Microsoft Linux (2010), I was able to get all decrypted RDP streams. From Lync, but it got trapped in the paring, can anyone help me on this? Below are some sections that Lync is sent to my client: 
  8B23AF01112119002B00100065E2EAA3821 ... 8023A207112109001802B081D9848000158 ... 8023B10D11211900AA80454024822000144 ... 8023090B11210EC324C7B00869200003500 ... A023BA101121160035011B004B5CC915604 ... A023781E112107CE7B4100143C420481004 ... A023E326116104DE6609C0952F14A915002 ... 9023F41C1221690A4B0586F7C98C018F978 ... 8023A61B112106009200B486554940400B8 ... A023DD2411210200850305803FB30080348 ... 9023D61612219F4582A002CAB25C2249800 ... A023962011210200480080135BED0019132 ...   
 As my observation, there are some bytes in the stream almost  
 First always  0x80  or  0xA0   
 The second byte should always be  0x23   
 next 2 bytes long (probably correct, like  0xA207 )  
 then always  0x1121   
 for example this stream:  
  80 23 a207 1121 09001802B081D9848000158 ... Do anyone know what to convert those bytes to encode? How to parse these streams correctly?  
 Thank you! In Advanced!   
 
 
 Maybe it will help you. Manage Stream from Lync Server:   

 








Posted by



at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)