ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/Convert-BER-XS/XS.pm
(Generate patch)

Comparing Convert-BER-XS/XS.pm (file contents):
Revision 1.11 by root, Fri Apr 19 20:44:34 2019 UTC vs.
Revision 1.24 by root, Sat Apr 20 14:59:26 2019 UTC

4 4
5=head1 SYNOPSIS 5=head1 SYNOPSIS
6 6
7 use Convert::BER::XS ':all'; 7 use Convert::BER::XS ':all';
8 8
9 my $ber = ber_decode $buf 9 my $ber = ber_decode $buf, $Convert::BER::XS::SNMP_PROFILE
10 or die "unable to decode SNMP message"; 10 or die "unable to decode SNMP message";
11 11
12 # The above results in a data structure consisting of (class, tag, 12 # The above results in a data structure consisting of
13 # (class, tag, # constructed, data)
13 # constructed, data) tuples. Below is such a message, SNMPv1 trap 14 # tuples. Below is such a message, SNMPv1 trap
14 # with a Cisco mac change notification. 15 # with a Cisco mac change notification.
15 # Did you know that Cisco is in the news almost every week because 16 # Did you know that Cisco is in the news almost
17 # every week because of some backdoor password
16 # of some backdoor password or other extremely stupid security bug? 18 # or other extremely stupid security bug?
17 19
18 [ ASN_UNIVERSAL, ASN_SEQUENCE, 1, 20 [ ASN_UNIVERSAL, ASN_SEQUENCE, 1,
19 [ 21 [
20 [ ASN_UNIVERSAL, ASN_INTEGER32, 0, 0 ], # snmp version 1 22 [ ASN_UNIVERSAL, ASN_INTEGER32, 0, 0 ], # snmp version 1
21 [ ASN_UNIVERSAL, 4, 0, "public" ], # community 23 [ ASN_UNIVERSAL, 4, 0, "public" ], # community
22 [ ASN_CONTEXT, 4, 1, # CHOICE, constructed - trap PDU 24 [ ASN_CONTEXT, 4, 1, # CHOICE, constructed - trap PDU
23 [ 25 [
24 [ ASN_UNIVERSAL, ASN_OBJECT_IDENTIFIER, 0, "1.3.6.1.4.1.9.9.215.2" ], # enterprise oid 26 [ ASN_UNIVERSAL, ASN_OBJECT_IDENTIFIER, 0, "1.3.6.1.4.1.9.9.215.2" ], # enterprise oid
25 [ ASN_APPLICATION, 0, 0, "\x0a\x00\x00\x01" ], # SNMP IpAddress, 10.0.0.1 27 [ ASN_APPLICATION, SNMP_IPADDRESS, 0, "10.0.0.1" ], # SNMP IpAddress
26 [ ASN_UNIVERSAL, ASN_INTEGER32, 0, 6 ], # generic trap 28 [ ASN_UNIVERSAL, ASN_INTEGER32, 0, 6 ], # generic trap
27 [ ASN_UNIVERSAL, ASN_INTEGER32, 0, 1 ], # specific trap 29 [ ASN_UNIVERSAL, ASN_INTEGER32, 0, 1 ], # specific trap
28 [ ASN_APPLICATION, ASN_TIMETICKS, 0, 1817903850 ], # SNMP TimeTicks 30 [ ASN_APPLICATION, SNMP_TIMETICKS, 0, 1817903850 ], # SNMP TimeTicks
29 [ ASN_UNIVERSAL, ASN_SEQUENCE, 1, # the varbindlist 31 [ ASN_UNIVERSAL, ASN_SEQUENCE, 1, # the varbindlist
30 [ 32 [
31 [ ASN_UNIVERSAL, ASN_SEQUENCE, 1, # a single varbind, "key value" pair 33 [ ASN_UNIVERSAL, ASN_SEQUENCE, 1, # a single varbind, "key value" pair
32 [ 34 [
33 [ ASN_UNIVERSAL, ASN_OBJECT_IDENTIFIER, 0, "1.3.6.1.4.1.9.9.215.1.1.8.1.2.1" ], 35 [ ASN_UNIVERSAL, ASN_OBJECT_IDENTIFIER, 0, "1.3.6.1.4.1.9.9.215.1.1.8.1.2.1" ],
60 ) { 62 ) {
61 ... and so on 63 ... and so on
62 64
63 # finally, let's encode it again and hope it results in the same bit pattern 65 # finally, let's encode it again and hope it results in the same bit pattern
64 66
65 my $buf = ber_encode $ber; 67 my $buf = ber_encode $ber, $Convert::BER::XS::SNMP_PROFILE;
66 68
67=head1 DESCRIPTION 69=head1 DESCRIPTION
68 70
69WARNING: Before release 1.0, the API is not considered stable in any way. 71WARNING: Before release 1.0, the API is not considered stable in any way.
70 72
71This module implements a I<very> low level BER/DER en-/decoder. 73This module implements a I<very> low level BER/DER en-/decoder.
72 74
73If is tuned for low memory and high speed, while still maintaining some 75It is tuned for low memory and high speed, while still maintaining some
74level of user-friendlyness. 76level of user-friendlyness.
75 77
76Currently, not much is documented, as this is an initial release to 78=head2 EXPORT TAGS AND CONSTANTS
77reserve CPAN namespace, stay tuned for a few days. 79
80By default this module doesn't export any symbols, but if you don't want
81to break your keyboard, editor or eyesight with extremely long names, I
82recommend importing the C<:all> tag. Still, you can selectively import
83things.
84
85=over
86
87=item C<:all>
88
89All of the below. Really. Recommended for at least first steps, or if you
90don't care about a few kilobytes of wasted memory (and namespace).
91
92=item C<:const>
93
94All of the strictly ASN.1-related constants defined by this module, the
95same as C<:const_asn :const_index>. Notably, this does not contain
96C<:const_ber_type> and C<:const_snmp>.
97
98A good set to get everything you need to decode and match BER data would be
99C<:decode :const>.
100
101=item C<:const_index>
102
103The BER tuple array index constants:
104
105 BER_CLASS BER_TAG BER_CONSTRUCTED BER_DATA
106
107=item C<:const_asn>
108
109ASN class values (these are C<0>, C<1>, C<2> and C<3>, respectively -
110exactly thw two topmost bits from the identifier octet shifted 6 bits to
111the right):
112
113 ASN_UNIVERSAL ASN_APPLICATION ASN_CONTEXT ASN_PRIVATE
114
115ASN tag values (some of which are aliases, such as C<ASN_OID>). Their
116numerical value corresponds exactly to the numbers used in BER/X.690.
117
118 ASN_BOOLEAN ASN_INTEGER32 ASN_BIT_STRING ASN_OCTET_STRING ASN_NULL ASN_OBJECT_IDENTIFIER
119 ASN_OBJECT_DESCRIPTOR ASN_OID ASN_EXTERNAL ASN_REAL ASN_SEQUENCE ASN_ENUMERATED
120 ASN_EMBEDDED_PDV ASN_UTF8_STRING ASN_RELATIVE_OID ASN_SET ASN_NUMERIC_STRING
121 ASN_PRINTABLE_STRING ASN_TELETEX_STRING ASN_T61_STRING ASN_VIDEOTEX_STRING ASN_IA5_STRING
122 ASN_ASCII_STRING ASN_UTC_TIME ASN_GENERALIZED_TIME ASN_GRAPHIC_STRING ASN_VISIBLE_STRING
123 ASN_ISO646_STRING ASN_GENERAL_STRING ASN_UNIVERSAL_STRING ASN_CHARACTER_STRING ASN_BMP_STRING
124
125=item C<:const_ber_type>
126
127The BER type constants, explained in the PROFILES section.
128
129 BER_TYPE_BYTES BER_TYPE_UTF8 BER_TYPE_UCS2 BER_TYPE_UCS4 BER_TYPE_INT
130 BER_TYPE_OID BER_TYPE_RELOID BER_TYPE_NULL BER_TYPE_BOOL BER_TYPE_REAL
131 BER_TYPE_IPADDRESS BER_TYPE_CROAK
132
133=item C<:const_snmp>
134
135Constants only relevant to SNMP. These are the tag values used by SNMP in
136the C<ASN_APPLICATION> namespace and have the exact numerical value as in
137BER/RFC 2578.
138
139 SNMP_IPADDRESS SNMP_COUNTER32 SNMP_UNSIGNED32 SNMP_TIMETICKS SNMP_OPAQUE SNMP_COUNTER64
140
141=item C<:decode>
142
143C<ber_decode> and the match helper functions:
144
145 ber_decode ber_is ber_is_seq ber_is_i32 ber_is_oid
146
147=item C<:encode>
148
149C<ber_encode> and the construction helper functions:
150
151 ber_encode ber_i32
152
153=back
78 154
79=head2 ASN.1/BER/DER/... BASICS 155=head2 ASN.1/BER/DER/... BASICS
80 156
81ASN.1 is a strange language that can be sed to describe protocols and 157ASN.1 is a strange language that can be used to describe protocols and
82data structures. It supports various mappings to JSON, XML, but most 158data structures. It supports various mappings to JSON, XML, but most
83importantly, to a various binary encodings such as BER, that is the topic 159importantly, to a various binary encodings such as BER, that is the topic
84of this module, and is used in SNMP or LDAP for example. 160of this module, and is used in SNMP or LDAP for example.
85 161
86While ASN.1 defines a schema that is useful to interpret encoded data, 162While ASN.1 defines a schema that is useful to interpret encoded data,
87the BER encoding is actually somehat self-describing: you might not know 163the BER encoding is actually somewhat self-describing: you might not know
88whether something is a string or a number or a sequence or something else, 164whether something is a string or a number or a sequence or something else,
89but you can nevertheless decode the overall structure, even if you end up 165but you can nevertheless decode the overall structure, even if you end up
90with just a binary blob for the actual value. 166with just a binary blob for the actual value.
91 167
92This works because BER values are tagged with a type and a namespace, 168This works because BER values are tagged with a type and a namespace,
93and also have a flag that says whther a value consists of subvalues (is 169and also have a flag that says whether a value consists of subvalues (is
94"constructed") or not (is "primitive"). 170"constructed") or not (is "primitive").
95 171
96Tags are simple integers, and ASN.1 defines a somewhat weird assortment of 172Tags are simple integers, and ASN.1 defines a somewhat weird assortment of
97those - for example, you have 32 bit signed integers and 16(!) different 173those - for example, you have 32 bit signed integers and 16(!) different
98string types, but there is no unsigned32 type for example. Different 174string types, but there is no Unsigned32 type for example. Different
99applications work around this in different ways, for example, SNMP defines 175applications work around this in different ways, for example, SNMP defines
100application-specific Gauge32, Counter32 and Unsigned32, which are mapped 176application-specific Gauge32, Counter32 and Unsigned32, which are mapped
101to two different tags: you can distinguish between Counter32 and the 177to two different tags: you can distinguish between Counter32 and the
102others, but not between Gause32 and Unsigned32, without the ASN.1 schema. 178others, but not between Gause32 and Unsigned32, without the ASN.1 schema.
103 179
107 183
108This module represents every BER value as a 4-element tuple (actually an 184This module represents every BER value as a 4-element tuple (actually an
109array-reference): 185array-reference):
110 186
111 [CLASS, TAG, CONSTRUCTED, DATA] 187 [CLASS, TAG, CONSTRUCTED, DATA]
188
189For example:
190
191 [ASN_UNIVERSAL, ASN_INTEGER32, 0, 177] # the integer 177
192 [ASN_UNIVERSAL, ASN_OCTET_STRING, 0, "john"] # the string "john"
193 [ASN_UNIVERSAL, ASN_OID, 0, "1.3.6.133"] # some OID
194 [ASN_UNIVERSAL, ASN_SEQUENCE, 1, [ [ASN_UNIVERSAL... # a sequence
112 195
113To avoid non-descriptive hardcoded array index numbers, this module 196To avoid non-descriptive hardcoded array index numbers, this module
114defines symbolic constants to access these members: C<BER_CLASS>, 197defines symbolic constants to access these members: C<BER_CLASS>,
115C<BER_TAG>, C<BER_CONSTRUCTED> and C<BER_DATA>. 198C<BER_TAG>, C<BER_CONSTRUCTED> and C<BER_DATA>.
116 199
135specific applications (for example, the SNMP C<Unsigned32> type is in this 218specific applications (for example, the SNMP C<Unsigned32> type is in this
136namespace), a special-purpose context namespace (C<ASN_CONTEXT>, used e.g. 219namespace), a special-purpose context namespace (C<ASN_CONTEXT>, used e.g.
137for C<CHOICE>) and a private namespace (C<ASN_PRIVATE>). 220for C<CHOICE>) and a private namespace (C<ASN_PRIVATE>).
138 221
139The meaning of the I<TAG> depends on the namespace, and defines a 222The meaning of the I<TAG> depends on the namespace, and defines a
140(partial) interpretation of the data value. For example, right now, SNMP 223(partial) interpretation of the data value. For example, SNMP defines
141application namespace knowledge ix hardcoded into this module, so it 224extra tags in the C<ASN_APPLICATION> namespace, and to take full advantage
142knows that SNMP C<Unsigned32> values need to be decoded into actual perl 225of these, you need to tell this module how to handle those via profiles.
143integers.
144 226
145The most common tags in the C<ASN_UNIVERSAL> namespace are 227The most common tags in the C<ASN_UNIVERSAL> namespace are
146C<ASN_INTEGER32>, C<ASN_BIT_STRING>, C<ASN_NULL>, C<ASN_OCTET_STRING>, 228C<ASN_INTEGER32>, C<ASN_BIT_STRING>, C<ASN_NULL>, C<ASN_OCTET_STRING>,
147C<ASN_OBJECT_IDENTIFIER>, C<ASN_SEQUENCE>, C<ASN_SET> and 229C<ASN_OBJECT_IDENTIFIER>, C<ASN_SEQUENCE>, C<ASN_SET> and
148C<ASN_IA5_STRING>. 230C<ASN_IA5_STRING>.
149 231
150The most common tags in SNMP's C<ASN_APPLICATION> namespace 232The most common tags in SNMP's C<ASN_APPLICATION> namespace are
151are C<SNMP_IPADDRESS>, C<SNMP_COUNTER32>, C<SNMP_UNSIGNED32>, 233C<SNMP_COUNTER32>, C<SNMP_UNSIGNED32>, C<SNMP_TIMETICKS> and
152C<SNMP_TIMETICKS>, C<SNMP_OPAQUE> and C<SNMP_COUNTER64>. 234C<SNMP_COUNTER64>.
153 235
154The I<CONSTRUCTED> flag is really just a boolean - if it is false, the 236The I<CONSTRUCTED> flag is really just a boolean - if it is false,
155the value is "primitive" and contains no subvalues, kind of like a 237the value is "primitive" and contains no subvalues, kind of like a
156non-reference perl scalar. IF it is true, then the value is "constructed" 238non-reference perl scalar. If it is true, then the value is "constructed"
157which just means it contains a list of subvalues which this module will 239which just means it contains a list of subvalues which this module will
158en-/decode as BER tuples themselves. 240en-/decode as BER tuples themselves.
159 241
160The I<DATA> value is either a reference to an array of further tuples (if 242The I<DATA> value is either a reference to an array of further tuples (if
161the value is I<CONSTRUCTED>), some decoded representation of the value, 243the value is I<CONSTRUCTED>), some decoded representation of the value,
170 252
171=head2 DECODING AND ENCODING 253=head2 DECODING AND ENCODING
172 254
173=over 255=over
174 256
175=item $tuple = ber_decoded $bindata 257=item $tuple = ber_decoded $bindata[, $profile]
176 258
177Decodes binary BER data in C<$bindata> and returns the resulting BER 259Decodes binary BER data in C<$bindata> and returns the resulting BER
178tuple. Croaks on any decoding error, so the returned C<$tuple> is always 260tuple. Croaks on any decoding error, so the returned C<$tuple> is always
179valid. 261valid.
180 262
263How tags are interpreted is defined by the second argument, which must
264be a C<Convert::BER::XS::Profile> object. If it is missing, the default
265profile will be used (C<$Convert::BER::XS::DEFAULT_PROFILE>).
266
267In addition to rolling your own, this module provides a
268C<$Convert::BER::XS::SNMP_PROFILE> that knows about the additional SNMP
269types.
270
181=item $bindata = ber_encode $tuple 271=item $bindata = ber_encode $tuple[, $profile]
182 272
183Encodes the BER tuple into a BER/DER data structure. 273Encodes the BER tuple into a BER/DER data structure. AS with
274Cyber_decode>, an optional profile can be given.
184 275
185=back 276=back
186 277
187=head2 HELPER FUNCTIONS 278=head2 HELPER FUNCTIONS
188 279
189Working with a 4-tuple for every value can be annoying. Or, rather, I<is> 280Working with a 4-tuple for every value can be annoying. Or, rather, I<is>
190annoying. To reduce this a bit, this module defines a number of helper 281annoying. To reduce this a bit, this module defines a number of helper
191functions, both to match BER tuples and to conmstruct BER tuples: 282functions, both to match BER tuples and to construct BER tuples:
192 283
193=head3 MATCH HELPERS 284=head3 MATCH HELPERS
194 285
195Thse functions accept a BER tuple as first argument and either paertially 286These functions accept a BER tuple as first argument and either partially
196or fully match it. They often come in two forms, one which exactly matches 287or fully match it. They often come in two forms, one which exactly matches
197a value, and one which only matches the type and returns the value. 288a value, and one which only matches the type and returns the value.
198 289
199They do check whether valid tuples are passed in and croak otherwise. As 290They do check whether valid tuples are passed in and croak otherwise. As
200a ease-of-use exception, they usually also accept C<undef> instead of a 291a ease-of-use exception, they usually also accept C<undef> instead of a
201tuple reference. in which case they silently fail to match. 292tuple reference, in which case they silently fail to match.
202 293
203=over 294=over
204 295
205=item $bool = ber_is $tuple, $class, $tag, $constructed, $data 296=item $bool = ber_is $tuple, $class, $tag, $constructed, $data
206 297
207This takes a BER C<$tuple> and matches its elements agains the privded 298This takes a BER C<$tuple> and matches its elements against the provided
208values, all of which are optional - values that are either missing or 299values, all of which are optional - values that are either missing or
209C<undef> will be ignored, the others will be matched exactly (e.g. as if 300C<undef> will be ignored, the others will be matched exactly (e.g. as if
210you used C<==> or C<eq> (for C<$data>)). 301you used C<==> or C<eq> (for C<$data>)).
211 302
212Some examples: 303Some examples:
249true. 340true.
250 341
251=item $bool = ber_is_oid $tuple, $oid_string 342=item $bool = ber_is_oid $tuple, $oid_string
252 343
253Returns true if the C<$tuple> represents an ASN_OBJECT_IDENTIFIER 344Returns true if the C<$tuple> represents an ASN_OBJECT_IDENTIFIER
254that exactly matches C$oid_string>. Exmaple: 345that exactly matches C<$oid_string>. Example:
255 346
256 ber_is_oid $tuple, "1.3.6.1.4" 347 ber_is_oid $tuple, "1.3.6.1.4"
257 or die "oid must be 1.3.6.1.4"; 348 or die "oid must be 1.3.6.1.4";
258 349
259=item $oid = ber_is_oid $tuple 350=item $oid = ber_is_oid $tuple
287use common::sense; 378use common::sense;
288 379
289use XSLoader (); 380use XSLoader ();
290use Exporter qw(import); 381use Exporter qw(import);
291 382
292our $VERSION = 0.2; 383our $VERSION;
293 384
385BEGIN {
386 $VERSION = 0.8;
294XSLoader::load __PACKAGE__, $VERSION; 387 XSLoader::load __PACKAGE__, $VERSION;
388}
295 389
296our %EXPORT_TAGS = ( 390our %EXPORT_TAGS = (
297 const => [qw( 391 const_index => [qw(
298 BER_CLASS BER_TAG BER_CONSTRUCTED BER_DATA 392 BER_CLASS BER_TAG BER_CONSTRUCTED BER_DATA
299 393 )],
394 const_asn => [qw(
300 ASN_BOOLEAN ASN_INTEGER32 ASN_BIT_STRING ASN_OCTET_STRING ASN_NULL ASN_OBJECT_IDENTIFIER ASN_TAG_BER ASN_TAG_MASK 395 ASN_BOOLEAN ASN_INTEGER32 ASN_BIT_STRING ASN_OCTET_STRING ASN_NULL ASN_OBJECT_IDENTIFIER
301 ASN_CONSTRUCTED ASN_UNIVERSAL ASN_APPLICATION ASN_CONTEXT ASN_PRIVATE ASN_CLASS_MASK ASN_CLASS_SHIFT 396 ASN_OBJECT_DESCRIPTOR ASN_OID ASN_EXTERNAL ASN_REAL ASN_SEQUENCE ASN_ENUMERATED
302 ASN_SEQUENCE 397 ASN_EMBEDDED_PDV ASN_UTF8_STRING ASN_RELATIVE_OID ASN_SET ASN_NUMERIC_STRING
303 398 ASN_PRINTABLE_STRING ASN_TELETEX_STRING ASN_T61_STRING ASN_VIDEOTEX_STRING ASN_IA5_STRING
399 ASN_ASCII_STRING ASN_UTC_TIME ASN_GENERALIZED_TIME ASN_GRAPHIC_STRING ASN_VISIBLE_STRING
400 ASN_ISO646_STRING ASN_GENERAL_STRING ASN_UNIVERSAL_STRING ASN_CHARACTER_STRING ASN_BMP_STRING
401
402 ASN_UNIVERSAL ASN_APPLICATION ASN_CONTEXT ASN_PRIVATE
403 )],
404 const_ber_type => [qw(
405 BER_TYPE_BYTES BER_TYPE_UTF8 BER_TYPE_UCS2 BER_TYPE_UCS4 BER_TYPE_INT
406 BER_TYPE_OID BER_TYPE_RELOID BER_TYPE_NULL BER_TYPE_BOOL BER_TYPE_REAL
407 BER_TYPE_IPADDRESS BER_TYPE_CROAK
408 )],
409 const_snmp => [qw(
304 SNMP_IPADDRESS SNMP_COUNTER32 SNMP_UNSIGNED32 SNMP_TIMETICKS SNMP_OPAQUE SNMP_COUNTER64 410 SNMP_IPADDRESS SNMP_COUNTER32 SNMP_UNSIGNED32 SNMP_TIMETICKS SNMP_OPAQUE SNMP_COUNTER64
305 )], 411 )],
306 encode => [qw( 412 decode => [qw(
307 ber_decode 413 ber_decode
308 ber_is ber_is_seq ber_is_i32 ber_is_oid 414 ber_is ber_is_seq ber_is_i32 ber_is_oid
309 )], 415 )],
310 decode => [qw( 416 encode => [qw(
311 ber_encode 417 ber_encode
418 ber_i32
312 )], 419 )],
313); 420);
314 421
315our @EXPORT_OK = map @$_, values %EXPORT_TAGS; 422our @EXPORT_OK = map @$_, values %EXPORT_TAGS;
316 423
317$EXPORT_TAGS{all} = \@EXPORT_OK; 424$EXPORT_TAGS{all} = \@EXPORT_OK;
425$EXPORT_TAGS{const} = [map @{ $EXPORT_TAGS{$_} }, qw(const_index const_asn)];
426use Data::Dump; ddx \%EXPORT_TAGS;
427
428=head1 PROFILES
429
430While any BER data can be correctly encoded and decoded out of the box, it
431can be inconvenient to have to manually decode some values into a "better"
432format: for instance, SNMP TimeTicks values are decoded into the raw octet
433strings of their BER representation, which is quite hard to decode. With
434profiles, you can change which class/tag combinations map to which decoder
435function inside C<ber_decode> (and of course also which encoder functions
436are used in C<ber_encode>).
437
438This works by mapping specific class/tag combinations to an internal "ber
439type".
440
441The default profile supports the standard ASN.1 types, but no
442application-specific ones. This means that class/tag combinations not in
443the base set of ASN.1 are decoded into their raw octet strings.
444
445C<Convert::BER::XS> defines two profile variables you can use out of the box:
446
447=over
448
449=item C<$Convert::BER::XS::DEFAULT_PROFILE>
450
451This is the default profile, i.e. the profile that is used when no
452profile is specified for de-/encoding.
453
454You can modify it, but remember that this modifies the defaults for all
455callers that rely on the default profile.
456
457=item C<$Convert::BER::XS::SNMP_PROFILE>
458
459A profile with mappings for SNMP-specific application tags added. This is
460useful when de-/encoding SNMP data.
461
462Example:
463
464 $ber = ber_decode $data, $Convert::BER::XS::SNMP_PROFILE;
465
466=back
467
468=head2 The Convert::BER::XS::Profile class
469
470=over
471
472=item $profile = new Convert::BER::XS::Profile
473
474Create a new profile. The profile will be identical to the default
475profile.
476
477=item $profile->set ($class, $tag, $type)
478
479Sets the mapping for the given C<$class>/C<$tag> combination to C<$type>,
480which must be one of the C<BER_TYPE_*> constants.
481
482Note that currently, the mapping is stored in a flat array, so large
483values of C<$tag> will consume large amounts of memory.
484
485Example:
486
487 $profile = new Convert::BER::XS::Profile;
488 $profile->set (ASN_APPLICATION, SNMP_COUNTER32, BER_TYPE_INT);
489 $ber = ber_decode $data, $profile;
490
491=item $type = $profile->get ($class, $tag)
492
493Returns the BER type mapped to the given C<$class>/C<$tag> combination.
494
495=back
496
497=head2 BER TYPES
498
499This lists the predefined BER types - you can map any C<CLASS>/C<TAG>
500combination to any C<BER_TYPE_*>.
501
502=over
503
504=item C<BER_TYPE_BYTES>
505
506The raw octets of the value. This is the default type for unknown tags and
507de-/encodes the value as if it were an octet string, i.e. by copying the
508raw bytes.
509
510=item C<BER_TYPE_UTF8>
511
512Like C<BER_TYPE_BYTES>, but decodes the value as if it were a UTF-8 string
513(without validation!) and encodes a perl unicode string into a UTF-8 BER
514string.
515
516=item C<BER_TYPE_UCS2>
517
518Similar to C<BER_TYPE_UTF8>, but treats the BER value as UCS-2 encoded
519string.
520
521=item C<BER_TYPE_UCS4>
522
523Similar to C<BER_TYPE_UTF8>, but treats the BER value as UCS-4 encoded
524string.
525
526=item C<BER_TYPE_INT>
527
528Encodes and decodes a BER integer value to a perl integer scalar. This
529should correctly handle 64 bit signed and unsigned values.
530
531=item C<BER_TYPE_OID>
532
533Encodes and decodes an OBJECT IDENTIFIER into dotted form without leading
534dot, e.g. C<1.3.6.1.213>.
535
536=item C<BER_TYPE_RELOID>
537
538Same as C<BER_TYPE_OID> but uses relative object identifier
539encoding: ASN.1 has this hack of encoding the first two OID components
540into a single integer in a weird attempt to save an insignificant amount
541of space in an otherwise wasteful encoding, and relative OIDs are
542basically OIDs without this hack. The practical difference is that the
543second component of an OID can only have the values 1..40, while relative
544OIDs do not have this restriction.
545
546=item C<BER_TYPE_NULL>
547
548Decodes an C<ASN_NULL> value into C<undef>, and always encodes a
549C<ASN_NULL> type, regardless of the perl value.
550
551=item C<BER_TYPE_BOOL>
552
553Decodes an C<ASN_BOOLEAN> value into C<0> or C<1>, and encodes a perl
554boolean value into an C<ASN_BOOLEAN>.
555
556=item C<BER_TYPE_REAL>
557
558Decodes/encodes a BER real value. NOT IMPLEMENTED.
559
560=item C<BER_TYPE_IPADDRESS>
561
562Decodes/encodes a four byte string into an IPv4 dotted-quad address string
563in Perl. Given the obsolete nature of this type, this is a low-effort
564implementation that simply uses C<sprintf> and C<sscanf>-style conversion,
565so it won't handle all string forms supported by C<inet_aton> for example.
566
567=item C<BER_TYPE_CROAK>
568
569Always croaks when encountered during encoding or decoding - the
570default behaviour when encountering an unknown type is to treat it as
571C<BER_TYPE_BYTES>. When you don't want that but instead prefer a hard
572error for some types, then C<BER_TYPE_CROAK> is for you.
573
574=back
575
576=cut
577
578our $DEFAULT_PROFILE = new Convert::BER::XS::Profile;
579our $SNMP_PROFILE = new Convert::BER::XS::Profile;
580
581# additional SNMP application types
582$SNMP_PROFILE->set (ASN_APPLICATION, SNMP_IPADDRESS , BER_TYPE_IPADDRESS);
583$SNMP_PROFILE->set (ASN_APPLICATION, SNMP_COUNTER32 , BER_TYPE_INT);
584$SNMP_PROFILE->set (ASN_APPLICATION, SNMP_UNSIGNED32, BER_TYPE_INT);
585$SNMP_PROFILE->set (ASN_APPLICATION, SNMP_TIMETICKS , BER_TYPE_INT);
586$SNMP_PROFILE->set (ASN_APPLICATION, SNMP_OPAQUE , BER_TYPE_IPADDRESS);
587$SNMP_PROFILE->set (ASN_APPLICATION, SNMP_COUNTER64 , BER_TYPE_INT);
588
589$DEFAULT_PROFILE->_set_default;
318 590
3191; 5911;
320 592
321=head2 BUGS / SHORTCOMINGs 593=head2 LIMITATIONS/NOTES
322 594
323This module does have a number of SNMPisms hardcoded, such as the SNMP 595This module can only en-/decode 64 bit signed and unsigned integers, and
324tags for Unsigned32 and so on. More configurability is needed, and, if 596only when your perl supports those.
325ever implemented, will come in a form similar to how L<JSON::XS> and 597
326L<CBOR::XS> respresent things, namely with an object-oriented interface. 598This module does not generally care about ranges, i.e. it will happily
599de-/encode 64 bit integers into an C<ASN_INTEGER32> value, or a negative
600number into an C<SNMP_COUNTER64>.
601
602OBJECT IDENTIFIEERs cannot have unlimited length, although the limit is
603much larger than e.g. the one imposed by SNMP or other protocols,a nd is
604about 4kB.
605
606REAL values are not supported and will currently croak.
607
608This module has undergone little to no testing so far.
609
610=head2 ITHREADS SUPPORT
611
612This module is unlikely to work when the (officially discouraged) ithreads
613are in use.
327 614
328=head1 AUTHOR 615=head1 AUTHOR
329 616
330 Marc Lehmann <schmorp@schmorp.de> 617 Marc Lehmann <schmorp@schmorp.de>
331 http://software.schmorp.de/pkg/Convert-BER-XS 618 http://software.schmorp.de/pkg/Convert-BER-XS

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines