diff options
| author | Anders Broman <anders.broman@ericsson.com> | 2005-12-16 06:47:22 +0000 |
|---|---|---|
| committer | Anders Broman <anders.broman@ericsson.com> | 2005-12-16 06:47:22 +0000 |
| commit | 483ec5bd0548f9720551737670c163fba32c3a8e (patch) | |
| tree | 9bcacac0d821309d6bc8e8d748dddb8791e40eb4 /asn1/dop/dop.asn | |
| parent | 163252a41c8f6ce7b233de6db317422647757d04 (diff) | |
| download | wireshark-483ec5bd0548f9720551737670c163fba32c3a8e.tar.gz | |
From Graeme Lunt:
* DOP - This has now been successfully tested and so is now enabled by default and workaround code removed.
Also now uses the correct EXPORTs from the other modules/dissectors.
* X509SAT - Most of the selected attributes are now supported in addition to the DirectoryString syntax attributes. This includes restoring the correct DirectoryString syntax and also providing the basic syntaxes (e.g. OBJECT IDENTIFIER, PrintableString). The latter requires a sed line in the Makefile which I assume should be OK? Not all the SAT can be defined in x509sat - so some have been included in x509if and x509af - though x509sat.cnf contains the master list and references the other dissectors where appropriate.
(I still prefer a syntax registration approach but I don't think that is going to be agreed in the short term.)
* X509IF - a mechanism to register some formating, based upon the hf_index, that is used in the cnf file.
* A couple of fixes identified by Stig.
svn path=/trunk/; revision=16814
Diffstat (limited to 'asn1/dop/dop.asn')
| -rw-r--r-- | asn1/dop/dop.asn | 8 |
1 files changed, 0 insertions, 8 deletions
diff --git a/asn1/dop/dop.asn b/asn1/dop/dop.asn index cea41dc89e..f7ddeb0180 100644 --- a/asn1/dop/dop.asn +++ b/asn1/dop/dop.asn @@ -278,8 +278,6 @@ dSAOperationalBindingManagementUnbind OPERATION ::= directoryUnbind EstablishOperationalBindingArgumentData ::= -- OPTIONALLY-PROTECTED-SEQ -- {-- SEQUENCE {bindingType [0] --OPERATIONAL-BINDING.&id({OpBindingSet}) -- OBJECT IDENTIFIER, --- The following line, whilst wrong, helps with Thales DOP dissection --- bindingID [1] IMPLICIT OperationalBindingID OPTIONAL, bindingID [1] OperationalBindingID OPTIONAL, accessPoint [2] AccessPoint, -- symmetric, Role A initiates, or Role B initiates @@ -329,8 +327,6 @@ Time ::= CHOICE {utcTime UTCTime, EstablishOperationalBindingResult ::= -- OPTIONALLY-PROTECTED-SEQ -- {-- SEQUENCE {bindingType [0] --OPERATIONAL-BINDING.&id({OpBindingSet}) -- OBJECT IDENTIFIER, --- The following line, whilst wrong, helps with Thales DOP dissection --- bindingID [1] IMPLICIT OperationalBindingID OPTIONAL, bindingID [1] OperationalBindingID OPTIONAL, accessPoint [2] AccessPoint, -- symmetric, Role A replies , or Role B replies @@ -361,8 +357,6 @@ EstablishOperationalBindingResult ::= ModifyOperationalBindingArgumentData ::= -- OPTIONALLY-PROTECTED-SEQ -- {--SEQUENCE {bindingType [0] --OPERATIONAL-BINDING.&id({OpBindingSet})-- OBJECT IDENTIFIER, --- The following line, whilst wrong, helps with Thales DOP dissection --- bindingID [1] IMPLICIT OperationalBindingID, bindingID [1] OperationalBindingID, accessPoint [2] AccessPoint OPTIONAL, -- symmetric, Role A initiates, or Role B initiates @@ -429,8 +423,6 @@ ModifyOperationalBindingResultData ::= SEQUENCE { TerminateOperationalBindingArgumentData ::= -- OPTIONALLY-PROTECTED-SEQ -- {-- SEQUENCE {bindingType [0] --OPERATIONAL-BINDING.&id({OpBindingSet})-- OBJECT IDENTIFIER, --- The following line, whilst wrong, helps with Thales DOP dissection --- bindingID [1] IMPLICIT OperationalBindingID, bindingID [1] OperationalBindingID, -- symmetric, Role A initiates, or Role B initiates initiator |