From: Justin F. <ju...@re...> - 2004-04-05 08:34:10
|
I had the same problem with my security usb smart key fob. The problem we have is M$'s CAPI which only supports windows operating systems. CSP is Cryptographic Service Provider, CSP works together with MS CAPI, and vendors write their own CSP, there doesnt exist AFAIK a software PKI. Fortunately, i now have a security device which has hardware encryption on the key fob itself, so it wont be too much of a concern for me. On Saturday 03 April 2004 21:57, Brian Dodge wrote: > Greetings, > I am writing (for fun) an RDP server to complement a VNC server I wrote > which runs on Linux/Solaris (but shares actual desktop unlike VNC on Linux > which is an X server), and Windows as well. I've decoded enough underlying > communications to connect on the iso/mcs layers and partially on the secure > layer with the Windows RDP client. The client however doesn't seem happy > with the RSA public key and/or signature I send it in the user data portion > of the connect-initial response. I am using openssl-libcrypto to generate > the public key, but I don't know how to generate the 72 bytes of signature. > If I use a Microsoft server generated key/signature I get from a wire sniff > in place of my own, the client seems happy and continues on to send me > encrypted rdp data (which I can't decrypt of course sans private key). > Thanks for all your work creating rdesktop, truly a remarkable feat, and I > look forward to sharing my server with you in the future. Thanks, Brian > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > rdesktop-devel mailing list > rde...@li... > https://lists.sourceforge.net/lists/listinfo/rdesktop-devel |