Hi Joseph
Setting this variable does not seem to produce any debug output..
setenv("GLOBUS_GSI_GSS_ASSIST_DEBUG_LEVEL",debug_level_string,1);
where debug_level_string is 4
If I just change above to
setenv("GLOBUS_GSSAPI_DEBUG_LEVEL",debug_level_string,1);
I see whole bunch of debug output..
Are you sure this is the right variable?
Thanks
-Neha
On Aug 15, 2008, at 11:20 AM, Joseph Bester wrote:
On Aug 15, 2008, at 11:05 AM, Neha Sharma wrote:
Hi Rachana
This is what I see with the environment variable set
[EMAIL PROTECTED] saz]$ bin/sazclient
globus_l_gsi_gssapi_activate entering
globus_l_gsi_gssapi_activate exiting
globus_i_gsi_gss_cred_read entering
globus_i_gsi_gss_create_cred entering
globus_i_gsi_gssapi_init_ssl_context entering
globus_i_gsi_gssapi_init_ssl_context exiting: major_status=0
globus_i_gsi_gss_create_cred entering
globus_i_gsi_gss_cred_read exiting: major_status=0
gss_acquire_cred exiting: major_status=0
SAZProtocol: Going to establish security context
gss_init_sec_context entering
Creating context w/ Credentials provided.
globus_i_gsi_gss_create_and_fill_context entering
SSL is at 0x9f26620
SSL_set_app_data to callback data 0x9f26290
Ciphers available:
NULL-SHA SSLv3 Kx=RSA Au=RSA Enc=None
Mac=SHA1
NULL-MD5 SSLv3 Kx=RSA Au=RSA Enc=None
Mac=MD5
...
...
gss_create_empty_oid_set entering
gss_create_empty_oid_set exiting: major_status=0
globus_i_gsi_gss_create_and_fill_context exiting: major_status=0
globus_i_gsi_gss_handshake entering
globus_i_gsi_gss_handshake exiting: major_status=1
globus_i_gsi_gss_get_token entering
output token: length = 104
value =
...
...
globus_i_gsi_gss_get_token exiting: major_status=0
init_sec_context:major_status:00000001:gss_state:0
req_flags=00000002:ret_flags=00000000
gss_init_sec_context exiting: major_status=1
gss_release_buffer entering
gss_release_buffer exiting: major_status=0
gss_init_sec_context entering
globus_i_gsi_gss_put_token entering
input token: length = 8614
value =
0000 - 16 03 00 00 4a 02
...
...
21a0 - 00 04 0e ...
21a6 - <SPACES/NULS>
globus_i_gsi_gss_put_token exiting: major_status=0
globus_i_gsi_gss_handshake entering
globus_i_gsi_gss_handshake exiting: major_status=1
globus_i_gsi_gss_get_token entering
output token: length = 17258
value =
0000 - 16 03 00 40 00 0b 00 41-bd 00 41 ba 00 0b aa
30 [EMAIL PROTECTED]
globus_i_gsi_gss_get_token exiting: major_status=0
init_sec_context:major_status:00000001:gss_state:0
req_flags=00000002:ret_flags=00000000
gss_init_sec_context exiting: major_status=1
gss_release_buffer entering
gss_release_buffer exiting: major_status=0
************AND THIS IS WHERE IT HANGS*********************
What does this mean ??
Thank you
-Neha
There are two calls to init_sec_context here and both generated an
output token. This means the client has almost completed the SSL
handshake (just *one* more token to pass in). It's unclear from this
trace whether the client is blocked writing the 2nd GSSAPI token or
block reading the reply to it. The original environment variable
setting I mentioned (GLOBUS_GSI_GSS_ASSIST_DEBUG_LEVEL) should let
you know which is occurring.
Joe
