>>>>> "DS" == Dirk Süsserott <[EMAIL PROTECTED]> writes:
DS> The question is: Does this also apply to the type ASN_OPAQUE, i.e. can I DS> safely interchange the types ASN_OCTET_STR and ASN_OPAQUE? DS> Do they have the very same behaviour regarding memory handling and DS> differ only in the type? That would be great for my purpose. Generally, you should never use OPAQUEs. If you have an application specific binary blob of data, you should put it in an OCTET STRING. An OPAQUE is a special type that was actually deprecated in SMIv2, so it's not even supposed to be used. The goal of it was to allow for extensibility but the SMI authors dropped it from suggested usage in second version of the language. OPAQUEs must also be a double wrapped BER sequence. IE, normally an octet string when encoded looks like 0x04 LEN .. .. ..; An opaque, on the other hand, needs to enclose another BER wrapped type internally. Thus, the first byte encoded in the value beyond the length field MUST be another BER type code, followed by a length. -- Wes Hardaker Sparta, Inc. ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
