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.24 by root, Sat Apr 20 14:59:26 2019 UTC vs.
Revision 1.38 by root, Sun Apr 21 00:39:26 2019 UTC

8 8
9 my $ber = ber_decode $buf, $Convert::BER::XS::SNMP_PROFILE 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 12 # The above results in a data structure consisting of
13 # (class, tag, # constructed, data) 13 # (class, tag, flags, data)
14 # tuples. Below is such a message, SNMPv1 trap 14 # tuples. Below is such a message, SNMPv1 trap
15 # with a Cisco mac change notification. 15 # with a Cisco mac change notification.
16 # Did you know that Cisco is in the news almost 16 # Did you know that Cisco is in the news almost
17 # every week because of some backdoor password 17 # every week because of some backdoor password
18 # or other extremely stupid security bug? 18 # or other extremely stupid security bug?
19 19
20 [ ASN_UNIVERSAL, ASN_SEQUENCE, 1, 20 [ ASN_UNIVERSAL, ASN_SEQUENCE, 1,
21 [ 21 [
22 [ ASN_UNIVERSAL, ASN_INTEGER32, 0, 0 ], # snmp version 1 22 [ ASN_UNIVERSAL, ASN_INTEGER, 0, 0 ], # snmp version 1
23 [ ASN_UNIVERSAL, 4, 0, "public" ], # community 23 [ ASN_UNIVERSAL, 4, 0, "public" ], # community
24 [ ASN_CONTEXT, 4, 1, # CHOICE, constructed - trap PDU 24 [ ASN_CONTEXT, 4, 1, # CHOICE, constructed - trap PDU
25 [ 25 [
26 [ 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
27 [ ASN_APPLICATION, SNMP_IPADDRESS, 0, "10.0.0.1" ], # SNMP IpAddress 27 [ ASN_APPLICATION, SNMP_IPADDRESS, 0, "10.0.0.1" ], # SNMP IpAddress
28 [ ASN_UNIVERSAL, ASN_INTEGER32, 0, 6 ], # generic trap 28 [ ASN_UNIVERSAL, ASN_INTEGER, 0, 6 ], # generic trap
29 [ ASN_UNIVERSAL, ASN_INTEGER32, 0, 1 ], # specific trap 29 [ ASN_UNIVERSAL, ASN_INTEGER, 0, 1 ], # specific trap
30 [ ASN_APPLICATION, SNMP_TIMETICKS, 0, 1817903850 ], # SNMP TimeTicks 30 [ ASN_APPLICATION, SNMP_TIMETICKS, 0, 1817903850 ], # SNMP TimeTicks
31 [ ASN_UNIVERSAL, ASN_SEQUENCE, 1, # the varbindlist 31 [ ASN_UNIVERSAL, ASN_SEQUENCE, 1, # the varbindlist
32 [ 32 [
33 [ ASN_UNIVERSAL, ASN_SEQUENCE, 1, # a single varbind, "key value" pair 33 [ ASN_UNIVERSAL, ASN_SEQUENCE, 1, # a single varbind, "key value" pair
34 [ 34 [
36 [ ASN_UNIVERSAL, ASN_OCTET_STRING, 0, "...data..." # the value 36 [ ASN_UNIVERSAL, ASN_OCTET_STRING, 0, "...data..." # the value
37 ] 37 ]
38 ] 38 ]
39 ], 39 ],
40 ... 40 ...
41 # let's dump it, for debugging
42
43 ber_dump $ber, $Convert::BER::XS::SNMP_PROFILE;
41 44
42 # let's decode it a bit with some helper functions 45 # let's decode it a bit with some helper functions
43 46
44 my $msg = ber_is_seq $ber 47 my $msg = ber_is_seq $ber
45 or die "SNMP message does not start with a sequence"; 48 or die "SNMP message does not start with a sequence";
46 49
47 ber_is $msg->[0], ASN_UNIVERSAL, ASN_INTEGER32, 0 50 ber_is $msg->[0], ASN_UNIVERSAL, ASN_INTEGER, 0
48 or die "SNMP message does not start with snmp version\n"; 51 or die "SNMP message does not start with snmp version\n";
49 52
50 # message is SNMP v1 or v2c? 53 # message is SNMP v1 or v2c?
51 if ($msg->[0][BER_DATA] == 0 || $msg->[0][BER_DATA] == 1) { 54 if ($msg->[0][BER_DATA] == 0 || $msg->[0][BER_DATA] == 1) {
52 55
55 my $trap = $msg->[2][BER_DATA]; 58 my $trap = $msg->[2][BER_DATA];
56 59
57 # check whether trap is a cisco mac notification mac changed message 60 # check whether trap is a cisco mac notification mac changed message
58 if ( 61 if (
59 (ber_is_oid $trap->[0], "1.3.6.1.4.1.9.9.215.2") # cmnInterfaceObjects 62 (ber_is_oid $trap->[0], "1.3.6.1.4.1.9.9.215.2") # cmnInterfaceObjects
60 and (ber_is_i32 $trap->[2], 6) 63 and (ber_is_int $trap->[2], 6)
61 and (ber_is_i32 $trap->[3], 1) # mac changed msg 64 and (ber_is_int $trap->[3], 1) # mac changed msg
62 ) { 65 ) {
63 ... and so on 66 ... and so on
64 67
65 # finally, let's encode it again and hope it results in the same bit pattern 68 # finally, let's encode it again and hope it results in the same bit pattern
66 69
100 103
101=item C<:const_index> 104=item C<:const_index>
102 105
103The BER tuple array index constants: 106The BER tuple array index constants:
104 107
105 BER_CLASS BER_TAG BER_CONSTRUCTED BER_DATA 108 BER_CLASS BER_TAG BER_FLAGS BER_DATA
106 109
107=item C<:const_asn> 110=item C<:const_asn>
108 111
109ASN class values (these are C<0>, C<1>, C<2> and C<3>, respectively - 112ASN 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 113exactly thw two topmost bits from the identifier octet shifted 6 bits to
113 ASN_UNIVERSAL ASN_APPLICATION ASN_CONTEXT ASN_PRIVATE 116 ASN_UNIVERSAL ASN_APPLICATION ASN_CONTEXT ASN_PRIVATE
114 117
115ASN tag values (some of which are aliases, such as C<ASN_OID>). Their 118ASN 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. 119numerical value corresponds exactly to the numbers used in BER/X.690.
117 120
118 ASN_BOOLEAN ASN_INTEGER32 ASN_BIT_STRING ASN_OCTET_STRING ASN_NULL ASN_OBJECT_IDENTIFIER 121 ASN_BOOLEAN ASN_INTEGER ASN_BIT_STRING ASN_OCTET_STRING ASN_NULL ASN_OID
119 ASN_OBJECT_DESCRIPTOR ASN_OID ASN_EXTERNAL ASN_REAL ASN_SEQUENCE ASN_ENUMERATED 122 ASN_OBJECT_IDENTIFIER ASN_OBJECT_DESCRIPTOR ASN_EXTERNAL ASN_REAL ASN_SEQUENCE ASN_ENUMERATED
120 ASN_EMBEDDED_PDV ASN_UTF8_STRING ASN_RELATIVE_OID ASN_SET ASN_NUMERIC_STRING 123 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 124 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 125 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 126 ASN_ISO646_STRING ASN_GENERAL_STRING ASN_UNIVERSAL_STRING ASN_CHARACTER_STRING ASN_BMP_STRING
124 127
134 137
135Constants only relevant to SNMP. These are the tag values used by SNMP in 138Constants 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 139the C<ASN_APPLICATION> namespace and have the exact numerical value as in
137BER/RFC 2578. 140BER/RFC 2578.
138 141
139 SNMP_IPADDRESS SNMP_COUNTER32 SNMP_UNSIGNED32 SNMP_TIMETICKS SNMP_OPAQUE SNMP_COUNTER64 142 SNMP_IPADDRESS SNMP_COUNTER32 SNMP_UNSIGNED32 SNMP_GAUGE32
143 SNMP_TIMETICKS SNMP_OPAQUE SNMP_COUNTER64
140 144
141=item C<:decode> 145=item C<:decode>
142 146
143C<ber_decode> and the match helper functions: 147C<ber_decode> and the match helper functions:
144 148
149 ber_decode ber-decode_prefix
145 ber_decode ber_is ber_is_seq ber_is_i32 ber_is_oid 150 ber_is ber_is_seq ber_is_int ber_is_oid
151 ber_dump
146 152
147=item C<:encode> 153=item C<:encode>
148 154
149C<ber_encode> and the construction helper functions: 155C<ber_encode> and the construction helper functions:
150 156
151 ber_encode ber_i32 157 ber_encode
158 ber_int
152 159
153=back 160=back
154 161
155=head2 ASN.1/BER/DER/... BASICS 162=head2 ASN.1/BER/DER/... BASICS
156 163
157ASN.1 is a strange language that can be used to describe protocols and 164ASN.1 is a strange language that can be used to describe protocols and
158data structures. It supports various mappings to JSON, XML, but most 165data structures. It supports various mappings to JSON, XML, but most
159importantly, to a various binary encodings such as BER, that is the topic 166importantly, to a various binary encodings such as BER, that is the topic
160of this module, and is used in SNMP or LDAP for example. 167of this module, and is used in SNMP, LDAP or X.509 for example.
161 168
162While ASN.1 defines a schema that is useful to interpret encoded data, 169While ASN.1 defines a schema that is useful to interpret encoded data,
163the BER encoding is actually somewhat self-describing: you might not know 170the BER encoding is actually somewhat self-describing: you might not know
164whether something is a string or a number or a sequence or something else, 171whether something is a string or a number or a sequence or something else,
165but you can nevertheless decode the overall structure, even if you end up 172but you can nevertheless decode the overall structure, even if you end up
167 174
168This works because BER values are tagged with a type and a namespace, 175This works because BER values are tagged with a type and a namespace,
169and also have a flag that says whether a value consists of subvalues (is 176and also have a flag that says whether a value consists of subvalues (is
170"constructed") or not (is "primitive"). 177"constructed") or not (is "primitive").
171 178
172Tags are simple integers, and ASN.1 defines a somewhat weird assortment of 179Tags are simple integers, and ASN.1 defines a somewhat weird assortment
173those - for example, you have 32 bit signed integers and 16(!) different 180of those - for example, you have one integers and 16(!) different
174string types, but there is no Unsigned32 type for example. Different 181string types, but there is no Unsigned32 type for example. Different
175applications work around this in different ways, for example, SNMP defines 182applications work around this in different ways, for example, SNMP defines
176application-specific Gauge32, Counter32 and Unsigned32, which are mapped 183application-specific Gauge32, Counter32 and Unsigned32, which are mapped
177to two different tags: you can distinguish between Counter32 and the 184to two different tags: you can distinguish between Counter32 and the
178others, but not between Gause32 and Unsigned32, without the ASN.1 schema. 185others, but not between Gause32 and Unsigned32, without the ASN.1 schema.
182=head2 DECODED BER REPRESENTATION 189=head2 DECODED BER REPRESENTATION
183 190
184This module represents every BER value as a 4-element tuple (actually an 191This module represents every BER value as a 4-element tuple (actually an
185array-reference): 192array-reference):
186 193
187 [CLASS, TAG, CONSTRUCTED, DATA] 194 [CLASS, TAG, FLAGS, DATA]
188 195
189For example: 196For example:
190 197
191 [ASN_UNIVERSAL, ASN_INTEGER32, 0, 177] # the integer 177 198 [ASN_UNIVERSAL, ASN_INTEGER, 0, 177] # the integer 177
192 [ASN_UNIVERSAL, ASN_OCTET_STRING, 0, "john"] # the string "john" 199 [ASN_UNIVERSAL, ASN_OCTET_STRING, 0, "john"] # the string "john"
193 [ASN_UNIVERSAL, ASN_OID, 0, "1.3.6.133"] # some OID 200 [ASN_UNIVERSAL, ASN_OID, 0, "1.3.6.133"] # some OID
194 [ASN_UNIVERSAL, ASN_SEQUENCE, 1, [ [ASN_UNIVERSAL... # a sequence 201 [ASN_UNIVERSAL, ASN_SEQUENCE, 1, [ [ASN_UNIVERSAL... # a sequence
195 202
196To avoid non-descriptive hardcoded array index numbers, this module 203To avoid non-descriptive hardcoded array index numbers, this module
197defines symbolic constants to access these members: C<BER_CLASS>, 204defines symbolic constants to access these members: C<BER_CLASS>,
198C<BER_TAG>, C<BER_CONSTRUCTED> and C<BER_DATA>. 205C<BER_TAG>, C<BER_FLAGS> and C<BER_DATA>.
199 206
200Also, the first three members are integers with a little caveat: for 207Also, the first three members are integers with a little caveat: for
201performance reasons, these are readonly and shared, so you must not modify 208performance reasons, these are readonly and shared, so you must not modify
202them (increment, assign to them etc.) in any way. You may modify the 209them (increment, assign to them etc.) in any way. You may modify the
203I<DATA> member, and you may re-assign the array itself, e.g.: 210I<DATA> member, and you may re-assign the array itself, e.g.:
204 211
205 $ber = ber_decode $binbuf; 212 $ber = ber_decode $binbuf;
206 213
207 # the following is NOT legal: 214 # the following is NOT legal:
208 $ber->[BER_CLASS] = ASN_PRIVATE; # ERROR, CLASS/TAG/CONSTRUCTED are READ ONLY(!) 215 $ber->[BER_CLASS] = ASN_PRIVATE; # ERROR, CLASS/TAG/FLAGS are READ ONLY(!)
209 216
210 # but all of the following are fine: 217 # but all of the following are fine:
211 $ber->[BER_DATA] = "string"; 218 $ber->[BER_DATA] = "string";
212 $ber->[BER_DATA] = [ASN_UNIVERSAL, ASN_INTEGER32, 0, 123]; 219 $ber->[BER_DATA] = [ASN_UNIVERSAL, ASN_INTEGER, 0, 123];
213 @$ber = (ASN_APPLICATION, SNMP_TIMETICKS, 0, 1000); 220 @$ber = (ASN_APPLICATION, SNMP_TIMETICKS, 0, 1000);
214 221
215I<CLASS> is something like a namespace for I<TAG>s - there is the 222I<CLASS> is something like a namespace for I<TAG>s - there is the
216C<ASN_UNIVERSAL> namespace which defines tags common to all ASN.1 223C<ASN_UNIVERSAL> namespace which defines tags common to all ASN.1
217implementations, the C<ASN_APPLICATION> namespace which defines tags for 224implementations, the C<ASN_APPLICATION> namespace which defines tags for
223(partial) interpretation of the data value. For example, SNMP defines 230(partial) interpretation of the data value. For example, SNMP defines
224extra tags in the C<ASN_APPLICATION> namespace, and to take full advantage 231extra tags in the C<ASN_APPLICATION> namespace, and to take full advantage
225of these, you need to tell this module how to handle those via profiles. 232of these, you need to tell this module how to handle those via profiles.
226 233
227The most common tags in the C<ASN_UNIVERSAL> namespace are 234The most common tags in the C<ASN_UNIVERSAL> namespace are
228C<ASN_INTEGER32>, C<ASN_BIT_STRING>, C<ASN_NULL>, C<ASN_OCTET_STRING>, 235C<ASN_INTEGER>, C<ASN_BIT_STRING>, C<ASN_NULL>, C<ASN_OCTET_STRING>,
229C<ASN_OBJECT_IDENTIFIER>, C<ASN_SEQUENCE>, C<ASN_SET> and 236C<ASN_OBJECT_IDENTIFIER>, C<ASN_SEQUENCE>, C<ASN_SET> and
230C<ASN_IA5_STRING>. 237C<ASN_IA5_STRING>.
231 238
232The most common tags in SNMP's C<ASN_APPLICATION> namespace are 239The most common tags in SNMP's C<ASN_APPLICATION> namespace are
233C<SNMP_COUNTER32>, C<SNMP_UNSIGNED32>, C<SNMP_TIMETICKS> and 240C<SNMP_COUNTER32>, C<SNMP_UNSIGNED32>, C<SNMP_TIMETICKS> and
234C<SNMP_COUNTER64>. 241C<SNMP_COUNTER64>.
235 242
236The I<CONSTRUCTED> flag is really just a boolean - if it is false, 243The I<FLAGS> value is really just a boolean at this time (but might
237the value is "primitive" and contains no subvalues, kind of like a 244get extended) - if it is C<0>, the value is "primitive" and contains
238non-reference perl scalar. If it is true, then the value is "constructed" 245no subvalues, kind of like a non-reference perl scalar. If it is C<1>,
239which just means it contains a list of subvalues which this module will 246then the value is "constructed" which just means it contains a list of
240en-/decode as BER tuples themselves. 247subvalues which this module will en-/decode as BER tuples themselves.
241 248
242The I<DATA> value is either a reference to an array of further tuples (if 249The I<DATA> value is either a reference to an array of further tuples
243the value is I<CONSTRUCTED>), some decoded representation of the value, 250(if the value is I<FLAGS>), some decoded representation of the value, if
244if this module knows how to decode it (e.g. for the integer types above) 251this module knows how to decode it (e.g. for the integer types above) or
245or a binary string with the raw octets if this module doesn't know how to 252a binary string with the raw octets if this module doesn't know how to
246interpret the namespace/tag. 253interpret the namespace/tag.
247 254
248Thus, you can always decode a BER data structure and at worst you get a 255Thus, you can always decode a BER data structure and at worst you get a
249string in place of some nice decoded value. 256string in place of some nice decoded value.
250 257
252 259
253=head2 DECODING AND ENCODING 260=head2 DECODING AND ENCODING
254 261
255=over 262=over
256 263
257=item $tuple = ber_decoded $bindata[, $profile] 264=item $tuple = ber_decode $bindata[, $profile]
258 265
259Decodes binary BER data in C<$bindata> and returns the resulting BER 266Decodes binary BER data in C<$bindata> and returns the resulting BER
260tuple. Croaks on any decoding error, so the returned C<$tuple> is always 267tuple. Croaks on any decoding error, so the returned C<$tuple> is always
261valid. 268valid.
262 269
266 273
267In addition to rolling your own, this module provides a 274In addition to rolling your own, this module provides a
268C<$Convert::BER::XS::SNMP_PROFILE> that knows about the additional SNMP 275C<$Convert::BER::XS::SNMP_PROFILE> that knows about the additional SNMP
269types. 276types.
270 277
278Example: decode a BER blob using the default profile - SNMP values will be
279decided as raw strings.
280
281 $tuple = ber_decode $data;
282
283Example: as above, but use the provided SNMP profile.
284
285 $tuple = ber_encode $data, $Convert::BER::XS::SNMP_PROFILE;
286
287=item ($tuple, $bytes) = ber_decode_prefix $bindata[, $profile]
288
289Works like C<ber_decode>, except it doesn't croak when there is data after
290the BER data, but instead returns the decoded value and the number of
291bytes it decoded.
292
293This is useful when you have BER data at the start of a buffer and other
294data after, and you need to find the length.
295
296Also, since BER is self-delimited, this can be used to decode multiple BER
297values joined together.
298
271=item $bindata = ber_encode $tuple[, $profile] 299=item $bindata = ber_encode $tuple[, $profile]
272 300
273Encodes the BER tuple into a BER/DER data structure. AS with 301Encodes the BER tuple into a BER/DER data structure. AS with
274Cyber_decode>, an optional profile can be given. 302Cyber_decode>, an optional profile can be given.
303
304The encoded data should be both BER and DER ("shortest form") compliant
305unless the input says otherwise (e.g. it uses constructed strings).
275 306
276=back 307=back
277 308
278=head2 HELPER FUNCTIONS 309=head2 HELPER FUNCTIONS
279 310
291a ease-of-use exception, they usually also accept C<undef> instead of a 322a ease-of-use exception, they usually also accept C<undef> instead of a
292tuple reference, in which case they silently fail to match. 323tuple reference, in which case they silently fail to match.
293 324
294=over 325=over
295 326
296=item $bool = ber_is $tuple, $class, $tag, $constructed, $data 327=item $bool = ber_is $tuple, $class, $tag, $flags, $data
297 328
298This takes a BER C<$tuple> and matches its elements against the provided 329This takes a BER C<$tuple> and matches its elements against the provided
299values, all of which are optional - values that are either missing or 330values, all of which are optional - values that are either missing or
300C<undef> will be ignored, the others will be matched exactly (e.g. as if 331C<undef> will be ignored, the others will be matched exactly (e.g. as if
301you used C<==> or C<eq> (for C<$data>)). 332you used C<==> or C<eq> (for C<$data>)).
306 orf die "tuple is not an ASN SEQUENCE"; 337 orf die "tuple is not an ASN SEQUENCE";
307 338
308 ber_is $tuple, ASN_UNIVERSAL, ASN_NULL 339 ber_is $tuple, ASN_UNIVERSAL, ASN_NULL
309 or die "tuple is not an ASN NULL value"; 340 or die "tuple is not an ASN NULL value";
310 341
311 ber_is $tuple, ASN_UNIVERSAL, ASN_INTEGER32, 0, 50 342 ber_is $tuple, ASN_UNIVERSAL, ASN_INTEGER, 0, 50
312 or die "BER integer must be 50"; 343 or die "BER integer must be 50";
313 344
314=item $seq = ber_is_seq $tuple 345=item $seq = ber_is_seq $tuple
315 346
316Returns the sequence members (the array of subvalues) if the C<$tuple> is 347Returns the sequence members (the array of subvalues) if the C<$tuple> is
323 my $snmp = ber_is_seq $ber 354 my $snmp = ber_is_seq $ber
324 or die "SNMP packet invalid: does not start with SEQUENCE"; 355 or die "SNMP packet invalid: does not start with SEQUENCE";
325 356
326 # now we know $snmp is a sequence, so decode the SNMP version 357 # now we know $snmp is a sequence, so decode the SNMP version
327 358
328 my $version = ber_is_i32 $snmp->[0] 359 my $version = ber_is_int $snmp->[0]
329 or die "SNMP packet invalid: does not start with version number"; 360 or die "SNMP packet invalid: does not start with version number";
330 361
331=item $bool = ber_is_i32 $tuple, $i32 362=item $bool = ber_is_int $tuple, $int
332 363
333Returns a true value if the C<$tuple> represents an ASN INTEGER32 with 364Returns a true value if the C<$tuple> represents an ASN INTEGER with
334the value C<$i32>. 365the value C<$int>.
335 366
336=item $i32 = ber_is_i32 $tuple 367=item $int = ber_is_int $tuple
337 368
338Returns true (and extracts the integer value) if the C<$tuple> is an ASN 369Returns true (and extracts the integer value) if the C<$tuple> is an
339INTEGER32. For C<0>, this function returns a special value that is 0 but 370C<ASN_INTEGER>. For C<0>, this function returns a special value that is 0
340true. 371but true.
341 372
342=item $bool = ber_is_oid $tuple, $oid_string 373=item $bool = ber_is_oid $tuple, $oid_string
343 374
344Returns true if the C<$tuple> represents an ASN_OBJECT_IDENTIFIER 375Returns true if the C<$tuple> represents an ASN_OBJECT_IDENTIFIER
345that exactly matches C<$oid_string>. Example: 376that exactly matches C<$oid_string>. Example:
356 387
357=head3 CONSTRUCTION HELPERS 388=head3 CONSTRUCTION HELPERS
358 389
359=over 390=over
360 391
361=item $tuple = ber_i32 $value 392=item $tuple = ber_int $value
362 393
363Constructs a new C<ASN_INTEGER32> tuple. 394Constructs a new C<ASN_INTEGER> tuple.
364 395
365=back 396=back
366 397
367=head2 RELATIONSHIP TO L<Convert::BER> and L<Convert::ASN1> 398=head2 RELATIONSHIP TO L<Convert::BER> and L<Convert::ASN1>
368 399
381use Exporter qw(import); 412use Exporter qw(import);
382 413
383our $VERSION; 414our $VERSION;
384 415
385BEGIN { 416BEGIN {
386 $VERSION = 0.8; 417 $VERSION = '1.0';
387 XSLoader::load __PACKAGE__, $VERSION; 418 XSLoader::load __PACKAGE__, $VERSION;
388} 419}
389 420
390our %EXPORT_TAGS = ( 421our %EXPORT_TAGS = (
391 const_index => [qw( 422 const_index => [qw(
392 BER_CLASS BER_TAG BER_CONSTRUCTED BER_DATA 423 BER_CLASS BER_TAG BER_FLAGS BER_DATA
393 )], 424 )],
425 const_asn_class => [qw(
426 ASN_UNIVERSAL ASN_APPLICATION ASN_CONTEXT ASN_PRIVATE
427 )],
394 const_asn => [qw( 428 const_asn_tag => [qw(
395 ASN_BOOLEAN ASN_INTEGER32 ASN_BIT_STRING ASN_OCTET_STRING ASN_NULL ASN_OBJECT_IDENTIFIER 429 ASN_BOOLEAN ASN_INTEGER ASN_BIT_STRING ASN_OCTET_STRING ASN_NULL ASN_OID ASN_OBJECT_IDENTIFIER
396 ASN_OBJECT_DESCRIPTOR ASN_OID ASN_EXTERNAL ASN_REAL ASN_SEQUENCE ASN_ENUMERATED 430 ASN_OBJECT_DESCRIPTOR ASN_EXTERNAL ASN_REAL ASN_SEQUENCE ASN_ENUMERATED
397 ASN_EMBEDDED_PDV ASN_UTF8_STRING ASN_RELATIVE_OID ASN_SET ASN_NUMERIC_STRING 431 ASN_EMBEDDED_PDV ASN_UTF8_STRING ASN_RELATIVE_OID ASN_SET ASN_NUMERIC_STRING
398 ASN_PRINTABLE_STRING ASN_TELETEX_STRING ASN_T61_STRING ASN_VIDEOTEX_STRING ASN_IA5_STRING 432 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 433 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 434 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 )], 435 )],
404 const_ber_type => [qw( 436 const_ber_type => [qw(
405 BER_TYPE_BYTES BER_TYPE_UTF8 BER_TYPE_UCS2 BER_TYPE_UCS4 BER_TYPE_INT 437 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 438 BER_TYPE_OID BER_TYPE_RELOID BER_TYPE_NULL BER_TYPE_BOOL BER_TYPE_REAL
407 BER_TYPE_IPADDRESS BER_TYPE_CROAK 439 BER_TYPE_IPADDRESS BER_TYPE_CROAK
408 )], 440 )],
409 const_snmp => [qw( 441 const_snmp => [qw(
410 SNMP_IPADDRESS SNMP_COUNTER32 SNMP_UNSIGNED32 SNMP_TIMETICKS SNMP_OPAQUE SNMP_COUNTER64 442 SNMP_IPADDRESS SNMP_COUNTER32 SNMP_GAUGE32 SNMP_UNSIGNED32
443 SNMP_TIMETICKS SNMP_OPAQUE SNMP_COUNTER64
411 )], 444 )],
412 decode => [qw( 445 decode => [qw(
413 ber_decode 446 ber_decode ber_decode_prefix
414 ber_is ber_is_seq ber_is_i32 ber_is_oid 447 ber_is ber_is_seq ber_is_int ber_is_oid
448 ber_dump
415 )], 449 )],
416 encode => [qw( 450 encode => [qw(
417 ber_encode 451 ber_encode
418 ber_i32 452 ber_int
419 )], 453 )],
420); 454);
421 455
422our @EXPORT_OK = map @$_, values %EXPORT_TAGS; 456our @EXPORT_OK = map @$_, values %EXPORT_TAGS;
423 457
424$EXPORT_TAGS{all} = \@EXPORT_OK; 458$EXPORT_TAGS{all} = \@EXPORT_OK;
459$EXPORT_TAGS{const_asn} = [map @{ $EXPORT_TAGS{$_} }, qw(const_asn_class const_asn_tag)];
425$EXPORT_TAGS{const} = [map @{ $EXPORT_TAGS{$_} }, qw(const_index const_asn)]; 460$EXPORT_TAGS{const} = [map @{ $EXPORT_TAGS{$_} }, qw(const_index const_asn)];
426use Data::Dump; ddx \%EXPORT_TAGS; 461
462our $DEFAULT_PROFILE = new Convert::BER::XS::Profile;
463
464$DEFAULT_PROFILE->_set_default;
465
466# additional SNMP application types
467our $SNMP_PROFILE = new Convert::BER::XS::Profile;
468
469$SNMP_PROFILE->set (ASN_APPLICATION, SNMP_IPADDRESS , BER_TYPE_IPADDRESS);
470$SNMP_PROFILE->set (ASN_APPLICATION, SNMP_COUNTER32 , BER_TYPE_INT);
471$SNMP_PROFILE->set (ASN_APPLICATION, SNMP_UNSIGNED32, BER_TYPE_INT);
472$SNMP_PROFILE->set (ASN_APPLICATION, SNMP_TIMETICKS , BER_TYPE_INT);
473$SNMP_PROFILE->set (ASN_APPLICATION, SNMP_OPAQUE , BER_TYPE_IPADDRESS);
474
475=head2 DEBUGGING
476
477To aid debugging, you cna call the C<ber_dump> function to print a "nice"
478representation to STDOUT.
479
480=over
481
482=item ber_dump $tuple[, $profile[, $prefix]]
483
484In addition to specifying the BER C<$tuple> to dump, youc an also specify
485a C<$profile> and a C<$prefix> string that is printed in front of each line.
486
487If C<$profile> is C<$Convert::BER::XS::SNMP_PROFILE>, then C<ber_dump>
488will try to improve its output for SNMP data.
489
490The output usually contains three columns, the "human readable" tag, the
491BER type used to decode it, and the data value.
492
493This function is somewhat slow and uses a number of heuristics and tricks,
494so it really is only suitable for debug prints.
495
496Example output:
497
498 SEQUENCE
499 | OCTET_STRING bytes 800063784300454045045400000001
500 | OCTET_STRING bytes
501 | CONTEXT (7) bytes CONSTRUCTED
502 | | INTEGER int 1058588941
503 | | INTEGER int 0
504 | | INTEGER int 0
505 | | SEQUENCE
506 | | | SEQUENCE
507 | | | | OID oid 1.3.6.1.2.1.1.3.0
508 | | | | TIMETICKS int 638085796
509
510=cut
511
512# reverse enum, very slow and ugly hack
513sub _re {
514 my ($export_tag, $value) = @_;
515
516 for my $symbol (@{ $EXPORT_TAGS{$export_tag} }) {
517 $value == eval $symbol
518 and return $symbol;
519 }
520
521 "($value)"
522}
523
524$SNMP_PROFILE->set (ASN_APPLICATION, SNMP_COUNTER64 , BER_TYPE_INT);
525
526sub _ber_dump {
527 my ($ber, $profile, $indent) = @_;
528
529 if (my $seq = ber_is_seq $ber) {
530 printf "%sSEQUENCE\n", $indent;
531 &_ber_dump ($_, $profile, "$indent| ")
532 for @$seq;
533 } else {
534 my $asn = $ber->[BER_CLASS] == ASN_UNIVERSAL;
535
536 my $class = _re const_asn_class => $ber->[BER_CLASS];
537 my $tag = $asn ? _re const_asn_tag => $ber->[BER_TAG] : $ber->[BER_TAG];
538 my $type = _re const_ber_type => $profile->get ($ber->[BER_CLASS], $ber->[BER_TAG]);
539 my $data = $ber->[BER_DATA];
540
541 if ($profile == $SNMP_PROFILE and $ber->[BER_CLASS] == ASN_APPLICATION) {
542 $tag = _re const_snmp => $ber->[BER_TAG];
543 } elsif (!$asn) {
544 $tag = "$class ($tag)";
545 }
546
547 $class =~ s/^ASN_//;
548 $tag =~ s/^(ASN_|SNMP_)//;
549 $type =~ s/^BER_TYPE_//;
550
551 if ($ber->[BER_FLAGS]) {
552 printf "$indent%-16.16s %-6.6s CONSTRUCTED\n", $tag, lc $type;
553 &_ber_dump ($_, $profile, "$indent| ")
554 for @$data;
555 } else {
556 if ($data =~ y/\x20-\x7e//c > 10 or $data =~ /\x00./s) {
557 # assume binary
558 $data = unpack "H*", $data;
559 substr $data, 40, 1e9, "..." if 40 < length $data;
560 } else {
561 $data =~ s/[^\x20-\x7e]/./g;
562 $data = "\"$data\"" if $type =~ /string/i;
563 substr $data, 40, 1e9, "..." if 40 < length $data;
564 }
565
566 printf "$indent%-16.16s %-6.6s %s\n", $tag, lc $type, $data;
567 }
568 }
569}
570
571sub ber_dump($;$$) {
572 _ber_dump $_[0], $_[1] || $DEFAULT_PROFILE, $_[2];
573}
427 574
428=head1 PROFILES 575=head1 PROFILES
429 576
430While any BER data can be correctly encoded and decoded out of the box, it 577While 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" 578can be inconvenient to have to manually decode some values into a "better"
571C<BER_TYPE_BYTES>. When you don't want that but instead prefer a hard 718C<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. 719error for some types, then C<BER_TYPE_CROAK> is for you.
573 720
574=back 721=back
575 722
576=cut 723=head2 Example Profile
577 724
578our $DEFAULT_PROFILE = new Convert::BER::XS::Profile; 725The following creates a profile suitable for SNMP - it's exactly identical
726to the C<$Convert::BER::XS::SNMP_PROFILE> profile.
727
579our $SNMP_PROFILE = new Convert::BER::XS::Profile; 728 our $SNMP_PROFILE = new Convert::BER::XS::Profile;
580 729
581# additional SNMP application types
582$SNMP_PROFILE->set (ASN_APPLICATION, SNMP_IPADDRESS , BER_TYPE_IPADDRESS); 730 $SNMP_PROFILE->set (ASN_APPLICATION, SNMP_IPADDRESS , BER_TYPE_IPADDRESS);
583$SNMP_PROFILE->set (ASN_APPLICATION, SNMP_COUNTER32 , BER_TYPE_INT); 731 $SNMP_PROFILE->set (ASN_APPLICATION, SNMP_COUNTER32 , BER_TYPE_INT);
584$SNMP_PROFILE->set (ASN_APPLICATION, SNMP_UNSIGNED32, BER_TYPE_INT); 732 $SNMP_PROFILE->set (ASN_APPLICATION, SNMP_UNSIGNED32, BER_TYPE_INT);
585$SNMP_PROFILE->set (ASN_APPLICATION, SNMP_TIMETICKS , BER_TYPE_INT); 733 $SNMP_PROFILE->set (ASN_APPLICATION, SNMP_TIMETICKS , BER_TYPE_INT);
586$SNMP_PROFILE->set (ASN_APPLICATION, SNMP_OPAQUE , BER_TYPE_IPADDRESS); 734 $SNMP_PROFILE->set (ASN_APPLICATION, SNMP_OPAQUE , BER_TYPE_IPADDRESS);
587$SNMP_PROFILE->set (ASN_APPLICATION, SNMP_COUNTER64 , BER_TYPE_INT); 735 $SNMP_PROFILE->set (ASN_APPLICATION, SNMP_COUNTER64 , BER_TYPE_INT);
588
589$DEFAULT_PROFILE->_set_default;
590
5911;
592 736
593=head2 LIMITATIONS/NOTES 737=head2 LIMITATIONS/NOTES
594 738
595This module can only en-/decode 64 bit signed and unsigned integers, and 739This module can only en-/decode 64 bit signed and unsigned integers, and
596only when your perl supports those. 740only when your perl supports those.
597 741
598This module does not generally care about ranges, i.e. it will happily 742This 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 743de-/encode 64 bit integers into an C<ASN_INTEGER> value, or a negative
600number into an C<SNMP_COUNTER64>. 744number into an C<SNMP_COUNTER64>.
601 745
602OBJECT IDENTIFIEERs cannot have unlimited length, although the limit is 746OBJECT 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 747much larger than e.g. the one imposed by SNMP or other protocols,a nd is
604about 4kB. 748about 4kB.
605 749
750Indefinite length encoding is not supported.
751
752Constructed strings are decoded just fine, but there should be a way to
753join them for convenience.
754
606REAL values are not supported and will currently croak. 755REAL values are not supported and will currently croak.
756
757The encoder and decoder tend to accept more formats than should be
758strictly supported.
607 759
608This module has undergone little to no testing so far. 760This module has undergone little to no testing so far.
609 761
610=head2 ITHREADS SUPPORT 762=head2 ITHREADS SUPPORT
611 763
617 Marc Lehmann <schmorp@schmorp.de> 769 Marc Lehmann <schmorp@schmorp.de>
618 http://software.schmorp.de/pkg/Convert-BER-XS 770 http://software.schmorp.de/pkg/Convert-BER-XS
619 771
620=cut 772=cut
621 773
7741;
775

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines