This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/discussion/do/listPosts/projects.ggf-editor/discussion.info_gsi_message_spec.review at Thu, 03 Nov 2022 23:19:47 GMT SourceForge : Post

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin
Project: Editor     Discussion > INFO:GSI Message Spec > review > List of Posts
Forum Topic - review: (1 Item)
View:  as 
 
 
review
I strongly support publication of this document.  To my knowledge,
there is no existing GSI message specification that would allow an
interoperable implementation of GSSAPI authentication for GridFTP as
described in GFD.20.  Since GridFTP servers commonly require GSSAPI
authentication via GSI, this meets an important need.  Also, this
document specifies the protocol binding for the GSS-API Extensions
documented in GFD.24, required for developing interoperable
implementations of that document.

Section 4.1 should include:
  The client must send an SSL 3.0 client hello message and must not
  send an SSL 2.0 client hello message (see RFC 2246 Section E).

In Section 6, the [GSS-Ext] reference should be to GFD.24, and the
MyProxy reference should be to GFD.54.  Also, some reference should be
provided to GFD.20.

There are some typos:
  "(SSLv3)," -> "(SSLv3);"
  "per-web" -> "pre-web"
  "Section 0" -> "Section 2"
  "standard an EEC certificate" -> "a standard EEC certificate"
  "Certificate cert chain" -> "Certificate chain"
  "is undefined" -> "is undefined."
  "has been critically reviewed" -> "has not been critically reviewed"

 
 


The Open Grid Forum Contact Webmaster | Report a problem | GridForge Help
This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/discussion/do/listPosts/projects.ggf-editor/discussion.info_gsi_message_spec.review at Thu, 03 Nov 2022 23:19:48 GMT