Blog

MIB Smithy 4.3 and MIB Smithy SDK 4.2 Released

MIB Smithy version 4.3 and MIB Smithy SDK version 4.2 are now available for download.

This release of MIB Smithy incorporates enhancements from the MIB Smithy SDK 4.1 and 4.2 releases and the MIB Views 1.6 release to add AES encryption support to SNMPv3 and several other usability enhancements to the SNMP tools built in to the MIB editor such as masking of agent passwords and improved handling of enumerated values for display. In addition, window size and position are saved and restored between sessions and behavior on multiple display setups is improved (similar changes will be made to MIB Views in a coming release).

In addition to these changes from MIB Smithy SDK 4.1 and MIB Views 1.6, the following changes are in this release:

346: Add tdom to build and distribution

The tDOM package for Tcl is now built in to MIB Smithy for XML and XSL processing. Professional Edition users can begin taking advantage of it immediately; additional XML features are in the works for both Professional and Standard.

359: Save/restore window geometry across sessions

MIB Smithy now saves and restores its window location and size between launches, rather than always opening to a fixed size/location relative to the screen size.

2710: wrong # args error importing mosy files

A “wrong # args” error could occur when importing mosy .defs files to reconstruct MIB module specifications from when reconstructing table definitions.

2459: Default window size on Windows with multiple displays

The default window size for MIB Smithy, when no previous session size is available, is no longer based relative to the desktop size. Previously this would make the window span multiple displays (particularly ridiculous on a triple display setup).

2714: [smilib format] using both OID and Syntax

You can now specify both an OID and syntax with the value given to the [smilib format] command, rather than having to choose one or the other. This way you can specify all three values from a received varbind and get the specific formatting (e.g. via DISPLAY-HINT) if the OID is known, or default formatting for the ASN.1 data type (e.g. hex for OCTET STRING) if it is unknown, with one command.