2 Jan 2002 Status report
-------------------------
 
I. COMPLETION OF THE FIRST STAGE
 
We belive that the last code snapshot is quite satisfactory. The two tasks
aimed by the end of 2001 have been solved:
 
1. Fixed:
OL> When the Kaboodle+VNC to Kaboodle+VNC 
OL> connection closes, the TCP port is not released. So next time the 
OL> connection is established, it must use a different port.
 
2. Redesigned:
OL> Kaboodle+VNC to Kaboodle+VNC MFC-based socket must be
OL> redesigned like Kaboodle to VNC WinAPI-socket.
 
The only one thing that has been left out is item 4.3 of the Spec 
"Modification to auto-detect VNC servers on a LAN".
We are currently working on this problem. It should not take us too
long to complete it. But taking into account New Year holidays we would
like to set the delivery date for this feature for January 14, 2002.
 
II. SSL IMPLEMENTATION
 
We understand your idea about separate implementation 
of the three SSL layers but our final considerations 
will be given after the Christmas:
 
1. Connection layer - supported by what we call Variant A.
 
OL> A. Update the implementation of Kaboodle CSocketTCPIP class so as 
OL> to (a) retain the support of Remote Connection functionality (b) 
OL> and ensure the support of intensive bilateral data streams required 
OL> by VNC tunneling (see the previous report for detail). The 
OL> encryption and key exchange solution are left unchanged.
 
This is to be done first of all and before any SSL part is applied.
 
2. Transport layer - take from SSL later on.
 
3. User authentication - uses your mechanism of "private partnership" and 
"verified partnership":
 
SCB> I've done some work already specifying two key-exchange
SCB> solutions.
 
I suppose this is also a modification of the SSL authentication layer. 
We will need the authentication protocol specification from you.
 
III. HINTS TO TEST KABOODLE+VNC
 
1) Kaboodle+VNC Server machine
      - Launch EF.exe;
      - Right-click _your_ computer icon;
      - Choose "VNC session" tab;
      - Press "Listen..." button. "VNC session" window will show up;
      - Press "Browse..." button and locate your WinVNC.exe file.
         Note that you do it just once;
      - Press "Listen" button to enter the Server mode.
 
2) Kaboodle+VNC Viewer machine
      - Launch EF.exe;
      - Right-click the target computer icon;
      - Choose "VNC session" tab;
      - Press "Start session..." button.
         "VNC session with xxx.xxx.xxx.xxx" window will show up;
      - Press "Browse..." button and locate your VncViewer.exe file.
         You do it just once;
      - Press "View" button to start session.
 
      There is a preprocessor macros in the VncSessionDLG.h file
// #define _SHOW_LOG
which is currently commented out. Uncomment it to watch a detailed 
runtime log of the connection activity.



_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel

Reply via email to