I just looked at the acse asn1 definition
and apart from a few constructs such as
[0] ABSTRACT-SYNTAX.&Type
and
[3] IMPLICIT SEQUENCE {other-mechanism-name
MECHANISM-NAME.&id({ObjectSet}),
other-mechanism-value
MECHANISM-NAME.&Type
({ObjectSet}{@.other-mechanism-name})}
(which would have to be handimplemented inside the template)
The ASN2ETH compiler should be able to generate code for the entire
protocol quite easily and with very little effort.
If you are game, I can create a dissector for the full protocol using
the ASN2ETH compiler (and handimplement the two constructs above in
the template).
Would you then be willing to test it and port over the remaining logic
which the compiler doesnt handle yet?
(I think it would be even easier to maintain than the current one
since for example there would now be a generic infrastructure to
handle calling a subdissector based on OID
(register_ber_oid_dissector() )
On Mon, 13 Sep 2004 08:19:28 +0000, Sid Sid <ysidelnikov@xxxxxxxxxxx> wrote:
> >From: Herbert Falk <herb@xxxxxxxxxxxx>
> >IEC 61850 is specifying the use of X,509 certificates for Application Level
> >Authentication within ACSE. I have extended packet-acse.c to decode this
> >and the ACSE Authentication values as specified by ACSE and the ACSE
> >Mechanism Name.
> I guess it's the best way - to extend but not to rewrite.
> >In doing so, I found that packet-acse.c and packet-pres.c make limited use
> >of ASN1.c. Thus they are vulnerable and will break if indefinite length
> >encodings are encountered.
> Strong assertion.
> Do you really have example of capture file which breaks acse/pres
> dissectors?
> If yes do you mind to send me such file(s) ?
> I guess all what we need is to path acse/pres dissectors if need be using
> such capture file.
> I already have MMS capture file you've sent me couple of months ago - seems
> ok with acse/pres dissectors.
> Thank you.
>
> _________________________________________________________________
> MSN 8 with e-mail virus protection service: 2 months FREE*
> http://join.msn.com/?page=features/virus
>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
>
