Danek Duvall wrote: > How does this compare with vino? Vino is a remote desktop based on the RFB (Remote FrameBuffer) protocol used by VNC, while rdesktop uses RDP (Remote Desktop Protocol).
> Don't we have some sort of solution for > RDP and Sun Ray? There is Sun Ray Connector for Windows OS, which currently supports protocol version 5.2, but it is not open source and it's most likely that never be, because of contract with Microsoft. To integrate rdesktop to Indiana distribution it need to be free software. > How are the encryption keys generated and shared? Could you be more specific in this question? I am not sure if you want to know the whole process for RC4 symmetric algorithm, which includes generating and storing keys on the server side (Microsoft Windows Terminal Server services)? The RC4 symmetric algorithm uses the same key stored on the server side do encrypt/decrypt data. > Is there any authentication available? There is domain authentication during the remote connection attempt, which queries domain servers for user authentication. This is possible with rdesktop CLI parameters. Also the standard authentication allows requires username and password, which are authenticated through Windows box. > You mention that RDP prior to version 6 is subject to MITM attacks, but > this project seems to use version 5 by default. Is there a reason we don't > use the more secure version of the protocol? The rdesktop is an open source project. As such it can not use spec for RDP protocol provided by Microsoft, which is distributed under NDA. The protocol used in rdesktop is reverse engineered version from scratch. This implementation can be redistributed under GPL license. Version 6 of the RDP protocol is relatively new and was not yet been reverse engineered. > > Danek -- best Michal Pryc
