[Mono-bugs] [Bug 80175][Nor] New - SSL ClientSessionCache always removes ClientSessionInfo objects

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by bugzilla at woy.nl.

http://bugzilla.ximian.com/show_bug.cgi?id=80175

--- shadow/80175	2006-12-07 05:53:56.000000000 -0500
+++ shadow/80175.tmp.19459	2006-12-07 05:53:56.000000000 -0500
@@ -0,0 +1,56 @@
+Bug#: 80175
+Product: Mono: Class Libraries
+Version: unspecified
+OS: All
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: Mono.Security
+AssignedTo: sebastien at ximian.com                            
+ReportedBy: bugzilla at woy.nl               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: SSL ClientSessionCache always removes ClientSessionInfo objects
+
+Please fill in this template when reporting a bug, unless you know what 
+you are doing.
+Description of Problem:
+The ClientSessionCache doesn't work properly because every 
+ClientSessionInfo item is removed from the cache before it can be used 
+because the method filling the ClientSessionInfo object data first checks 
+the validity but that check always retuns false because the data ( 
+masterSecret ) is not yet set. This results in removing the info from the 
+cache.
+
+
+Steps to reproduce the problem:
+1. Make a connection with SSL to a server wich supports Session Resumption
+2. Within 3 minutes re-connect to the server. See that the SessionId of 
+the previous version is not re-used for Session Resumption
+3. 
+
+Actual Results:
+The Session is not Resumed
+
+Expected Results:
+The Session Should be Resumed
+
+How often does this happen? 
+Always
+
+Additional Information:
+
+In ClientSessionCache SetContextInCache is responsible for filling the 
+data in the ClientSessionInfo. This method uses the FromContext method to 
+aquire the right ClientSessionInfo. The FromContext method removes the 
+ClientSessionInfo object from the cache when it is not valid. But the 
+first time this is done the masterSecret field is not yet filled in so it 
+is not valid. This results in always removing the ClientSessionInfo from 
+the Cache wich in turn results in a non-functional SessionCache.
+
+I uploaded a Patch generated with RapidSVN to http://woy.nl/patch/
+ClientSessionCache.patch