Send MCS_CONNECT_RESPONSE (but correct?)

diff --git a/mcs.c b/mcs.c
index 24a2e767166ccd35b0630c376562ea7ac99cdad6..9e6740f950022ab63751722393ebf82f16f4efee 100644 (file)
--- a/mcs.c
+++ b/mcs.c
@@ -156,13 +156,31 @@ mcs_send_connect_response()
 {
        STREAM s;
 
 {
        STREAM s;
 

-       s = iso_init(2048);  // FIXME
+       s = iso_init(80);  // FIXME

 
 

-       ber_out_header(s, MCS_CONNECT_RESPONSE, 2048);
+       ber_out_header(s, MCS_CONNECT_RESPONSE, 80);

        ber_out_header(s, BER_TAG_RESULT, 1);
        ber_out_header(s, BER_TAG_RESULT, 1);

-       out_uint8(s, 1);  // success
+       out_uint8(s, 0);
+
+       ber_out_header(s, BER_TAG_INTEGER, 1);
+       out_uint8(s, 1);  // connect id
+       
+       mcs_out_domain_params(s, 34, 2, 0, 0xffff);  // dumdidum?
+
+       ber_out_header(s, BER_TAG_OCTET_STRING, 28);
+
+       out_uint8s(s, 21);   // ick
+       out_uint8(s, 0);
+
+       // server info -- we claim to support RDP5
+       out_uint16_le(s, SEC_TAG_SRV_INFO);
+       out_uint16_le(s, 6);  // length
+       out_uint16_le(s, 5);
+
+       // aiee, no crypto info yet! :-)

        
        s_mark_end(s);
        
        s_mark_end(s);

+       printf("LEN: %u\n", s->p - s->data);

        iso_send(s);
 
 }
        iso_send(s);
 
 }