I knew that asn2wrs generated these but I thought the oids were
created from within (I even spent some time trying to figure out where
they came from)
L
On 8/27/07, Kukosa, Tomas <tomas.kukosa@xxxxxxxxxxx> wrote:
> > - There are others that attempt to be registered with "funky" oid
> > strings "dop.agreement.2.5.19.1" or "x411.extension-attribute.27"
> > which are not resolvable (I tried to fix these but they come from deep
> > into asn2wrs and I could not figure out how to get it fixed).
>
> Hi,
>
> it comes from
> --- asn1\dop\dop.cnf ---
> #.REGISTER
> ...
> HierarchicalAgreement B "dop.agreement.2.5.19.2"
> "hierarchical-agreement"
> ...
>
> it generates
> --- packet-dop.c ---
> register_ber_oid_dissector("dop.agreement.2.5.19.2",
> dissect_HierarchicalAgreement_PDU, proto_dop, "hierarchical-agreement");
>
>
> if you change it in .cnf file then it will be changed in packet-dop.c
>
> Regards,
> Tomas
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev@xxxxxxxxxxxxx
> http://www.wireshark.org/mailman/listinfo/wireshark-dev
>
--
This information is top security. When you have read it, destroy yourself.
-- Marshall McLuhan