有人能够在 RDP 客户端中使用快速路径更新 PDU 吗？
我正在与朋友一起开发 RDP 客户端作为宠物项目，我们正在尝试让快速路径更新发挥作用，因为 rdesktop 到目前为止还不支持此功能。握手后，在解密开始失败之前，我们能够处理大约 20-21 个快速路径 PDU。这是因为 RDP 服务器正在加密 20 个字节并丢弃 RC4 密钥流。如果我在正确的时间和地点使用客户端解密密钥流中的 20 个字节，则我的所有快速路径更新都能够被解密。不幸的是，这个“正确的时间和地点”会根据 RDP 服务器发送的数据包顺序而变化。
我想知道两件事：
- 是否有人能够在其 RDP 客户端（开源或其他方式）中成功获得快速路径更新？显然，MSTSC 不算数:-)
- 有没有人见过 20 字节的这个问题或者知道它发生的任何原因？
任何帮助将不胜感激。
I'm working on an RDP client with a friend as a pet project and we're trying to get fast-path updates to work since rdesktop hasn't supported this so far. We're able to process around 20-21 fast-path PDUs after the handshake before decryption starts failing. This is because somewhere in there, the RDP server is encrypting 20 bytes and throwing off the RC4 keystream. If I consume 20 bytes from the client decryption keystream at the right time and place, all my fast-path updates are able to be decrypted. Unfortunately, this "right time and place" changes depending on the sequence of packets the RDP server is sending.
I was wondering 2 things:
- Has anyone been able to successfully get fast-path updates working in their RDP client, open source or otherwise? Obviously, MSTSC doesn't count :-)
- Has anyone seen this issue with the 20 bytes or know of any reason why it occurs?
Any help would be much appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论