This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/go/projects.ggf-editor/discussion.rec_secure_communication_profile.topc4183 at Sun, 06 Nov 2022 09:02:56 GMT SourceForge : Post

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin
Project: Editor     Discussion > REC:Secure Communication Profile 1.0 > Hostname verification > List of Posts
Forum Topic - Hostname verification: (2 Items)
View:  as 
 
 
Hostname verification
The document contains a number of references to using server certificates for "hostname verification". I think that this
 is restrictive as the certificate authenticates the server and not just the name of the remote host that gives access 
to the server. I think that these statements could be rephrased to recognise the possibility that the server's address 
may be dynamic.

RFC 2818 allows for this possibility i.e. "If the client has external information as to the expected identity of the 
server, the hostname check MAY be omitted. (For instance, a  client may be connecting to a machine whose address and 
hostname are dynamic but the client knows the certificate that the server will present.)"
Re: Hostname verification
Resolved: updated with additional descriptive text and termed this process "token verification"

 
 


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/go/projects.ggf-editor/discussion.rec_secure_communication_profile.topc4183 at Sun, 06 Nov 2022 09:02:56 GMT