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.exp_myproxy_protocol.encoding_of_binary_data at Sun, 06 Nov 2022 09:03:04 GMT SourceForge : Post

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin
Project: Editor     Discussion > EXP:MyProxy Protocol > Encoding of binary data > List of Posts
Forum Topic - Encoding of binary data: (2 Items)
View:  as 
 
 
Encoding of binary data
The document needs to be more clear on how to encode binary data in sections 4 and 5. For starters, there is an error in
 stating (on multiple places) that "certificates are encoded using the X.509 ASN.1 format". ASN.1 is a language that 
describes a data structure. It can in turn be serialized in a number of ways, DER encoding is the most common.

In section 4, is the "byte encoding the number of certificates to be sent" in ASCII or binary? This further implies an 
upper limit of a certificate chain length to either 9 or 255. Either way, this limitation is not documented.

Section 4 again: "The server will then send a standard RESPONSE message, and both client and server will close the 
connection." Does this mean that the proxy certificate is sent BEFORE the response message?
Re: Encoding of binary data
Thanks for the comments.  I\'ve corrected the document to specify DER encoding for certificates and unsigned binary 
encoding of the number of certificates to be sent.

In response to the last comment: yes, the proxy certificate is sent before the final response message.

 
 


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.exp_myproxy_protocol.encoding_of_binary_data at Sun, 06 Nov 2022 09:03:04 GMT