| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
svn path=/trunk/; revision=37731
|
|
|
|
|
|
| |
directly.
svn path=/trunk/; revision=37420
|
|
|
|
| |
svn path=/trunk/; revision=36443
|
|
|
|
|
|
|
|
|
| |
- Fix dissection of extensions in INAP it should now be possible to add
an "OID dissector" for extensions.
Should fix BUG
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5799
svn path=/trunk/; revision=36435
|
|
|
|
| |
svn path=/trunk/; revision=36365
|
|
|
|
|
|
| |
http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=36079
svn path=/trunk/; revision=36085
|
|
|
|
| |
svn path=/trunk/; revision=36049
|
|
|
|
|
|
| |
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5637
svn path=/trunk/; revision=35843
|
|
|
|
| |
svn path=/trunk/; revision=35757
|
|
|
|
|
|
|
|
|
| |
ensure the
return string is NULL terminated.
Make the change also in the .cnf file
svn path=/trunk/; revision=35551
|
|
|
|
| |
svn path=/trunk/; revision=35501
|
|
|
|
|
|
| |
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5573
svn path=/trunk/; revision=35498
|
|
|
|
| |
svn path=/trunk/; revision=35387
|
|
|
|
|
|
|
|
|
|
|
| |
keys to have _uint in their names, to match the routines that handle
dissector tables with string keys. (Using _port can confuse people into
thinking they're intended solely for use with TCP/UDP/etc. ports when,
in fact, they work better for things such as Ethernet types, where the
binding of particular values to particular protocols are a lot
stronger.)
svn path=/trunk/; revision=35224
|
|
|
|
| |
svn path=/trunk/; revision=35126
|
|
|
|
| |
svn path=/trunk/; revision=34814
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5076
Use:
/*
* Dissect Multiple Choice Message
* This function is used to decode a message, when several encoding may be used.
* For exemple, in the last MAP version, the Cancel Location is defined like this:
* CancelLocationArg ::= [3] IMPLICIT SEQUENCE
* But in the previous MAP version, it was a CHOICE between a SEQUENCE and an IMSI
* As ASN1 encoders (or software) still uses the old encoding, this function allows
* the decoding of both versions.
* Moreover, some optimizations (or bad practice ?) in ASN1 encoder, removes the
* SEQUENCE tag, when only one parameter is present in the SEQUENCE.
* This explain why the function expects 3 parameters:
* - a [3] SEQUENCE corresponding the recent ASN1 MAP encoding
* - a SEQUENCE for old style
* - and a single parameter, for old version or optimizations
*
* The analyze of the first ASN1 tag, indicate what kind of decoding should be used,
* if the decoding function is provided (so not a NULL function)
*/
svn path=/trunk/; revision=34001
|
|
|
|
| |
svn path=/trunk/; revision=32509
|
|
|
|
| |
svn path=/trunk/; revision=32405
|
|
|
|
|
|
| |
RANAP and friends want the MNC encoded in big endian form.
svn path=/trunk/; revision=32257
|
|
|
|
| |
svn path=/trunk/; revision=31961
|
|
|
|
|
|
| |
wrong decoding IMSI with GSM MAP protocol
svn path=/trunk/; revision=31764
|
|
|
|
| |
svn path=/trunk/; revision=31546
|
|
|
|
| |
svn path=/trunk/; revision=31413
|
|
|
|
| |
svn path=/trunk/; revision=31404
|
|
|
|
|
|
|
| |
returns an ep_allocated string (and whose name reflects that what you
get out is UTF-8, not just ASCII).
svn path=/trunk/; revision=31376
|
|
|
|
| |
svn path=/trunk/; revision=31102
|
|
|
|
| |
svn path=/trunk/; revision=30516
|
|
svn path=/trunk/; revision=30470
|