RE: [taste-users] asn1scc/tinyAsn1 and X.509

[ Thread Index | Date Index | More Archives ]

Hi Adrian,

Unfortunately, the ASN.1 compiler does not support the X.681 spec (Information Class Objects). 

So, regarding your final question, I am afraid that our ASN.1 compiler cannot compile the X.509 standards without major enhancements.

Kind regards,
George Mamais

Dr.-Ing. George Mamais
Semantix Information Technologies
email: gmamais@xxxxxxxxxxx
web  :
phone: (+30)2106412065
fax  : (+30)2106412068
addr.: K Tsaldari 62, 11476, Athens, GREECE

-----Original Message-----
From: Adrian-Ken Rueegsegger [mailto:ken@xxxxxxxxxxx] 
Sent: Thursday, September 27, 2012 5:53 PM
To: Maxime Perrotin
Cc: taste-users@xxxxxxxxxxxxxxxxxxx; George Mamais
Subject: Re: [taste-users] asn1scc/tinyAsn1 and X.509

Hi again,

On 09/27/2012 04:03 PM, Maxime Perrotin wrote:
> Sure, here it is:
> We will release the source code (and documentation) a bit later on, 
> when it is finalized.

That's great, thanks.

> In the meantime please feel free to ask if you need help to set it up 
> and use it. And if you have comments or suggestions, don't hesitate.

The official ITU-T X.509 ASN.1 specification found at [1] (under "Formal
description(s)") does not use the problematic construct (ANY DEFINED BY). The compilation still fails with the following error:

$ mono asn1.exe -Ada AuthenticationFramework.asn File AuthenticationFramework.asn, line 52:24 no viable alternative at character '&'

It seems that the TYPE-IDENTIFIER information object class (specified in X.681, [2]) is not supported by asn1scc.

Is there a way to work around this issue or do you think compiling the
X.509 specs requires enhancements to the asn1scc tool?

Thanks again for you help.

Best regards,

[1] -
[2] -

Mail converted by MHonArc 2.6.19+