The web site itself will also be moving to a new server soon, once we’ve got email services integrated with our LDAP server (another of many upgrades to our internal systems I hope to write about in the articles section soon). Then we can retire the old server hardware that’s been in operation since 2001 when our flagship product, MIB Smithy, was just a spark of an idea.

I’m totally amped to get the last of this migration done. For one thing, I’ve been feeling a bit down on myself for getting behind on product development and neglecting to get the articles section rolling (too many commitments over the last year or two), and it will free up time to get back into it. But mainly I’m amped because of all the potential for reducing drag.

Internally, I’m looking forward a ton of automation, ability to handle and delegate to more staff, room for expansion, speed and capabilities that moving all our x86 platforms to high-end hardware running VMware Server will provide.

Externally, you can soon expect IPv6 and 64-bit platform support for our products and speeding our release cycle back up. We’re bringing the popular FogBugz bug/support tracker online with the last bit of web/email server migration, and I hope to have it integrated directly into our products soon thereafter. Since we’ve outgrown our current bug/feature tracking systems, and email inquiries aren’t currently handled directly through a tracker, this should be a big improvement in our planning, scheduling, and handling of such inquiries.

Overall I’m excited because all of these changes, while they’ve been time consuming and occasionally frustrating, represent a whole new chapter for Muonics: one that will feel to me much less like a startup and much more like a well-oiled machine.

• The right-click popup menu in the Project Tree will no longer show for Type/Value Assignment virtual folders as it was actually showing the menu for the module. Consequently, selecting “Remove” would remove the module, rather than all Type/Value Assignments as one might expect.
• A “record search string is ambiguous” error would occur when sorting OIDs for generating some output formats if the name assigned to one of those OIDs was also used in another module.
• An “invalid command name” error could occur when trying to show the calendar popup for REVISION and LAST-UPDATED timestamps due to a trace not being removed after the popup is hidden.
• Removed conversion of spaces to HTML entities in help file:// URLs under Windows to prevent errors launching help when MSIE 7 is the default browser.

Once again I would like to apologize for the inconvenienced caused by the downtime.

Michael Kirkham, President & CEO

After reviewing security logs and comparing file systems and source code to known backups as part of our security audit, we are relieved to report that we have not found any evidence that any systems or customer information were successfully compromised during the period that firewall rules were partially disabled and some internet-facing systems were under attack. Additionally it appears that at least some of what was reported as an attack was the work of worms targeting Windows vulnerabilities, which we do not use for our servers–traffic we do not normally see due to firewalls and other protections.

The main avenue for attack that we were most concerned with was certain systems that were being brought up to migrate services to that might not have been fully patched or locked down yet while they were in transition. Though it doesn’t appear there’s been any compromise, as an added precaution, we will still be reinstalling these systems and services, so you may expect some brief periods of down time over the weekend (much of this we’re doing anyway, to sync up deployed software versions with versions being installed on the new systems to ease transition). We’re also revoking all authentication and encryption keys and have requested a new SSL certificate, and will take additional steps to improve our auditing procedures and response time.

Once we have finished upgrading critical server software and have received the new SSL certificate, we will bring the shopping system back online. You will not be able to log into your Muonics web site account until this time.

Please accept our apology for any inconvenience or worry caused by our previous notice and the downtime involved. Though it appears to have been a false alarm, one can never be too cautious about these things.

Should you have any lingering concerns, we will be more than happy to reimburse anyone who has placed orders with us online, at any time in the past, for up to 12 months of credit activity monitoring from your choice of provider. You can contact me directly by phone or email any time between now and March 31, 2008 to arrange.

Thank you for your patience.

Michael Kirkham, President & CEO

(more…)

• nmtrapd under Linux could max out CPU usage due to Linux-specific handling of select() timeouts.
• Newlines and carriage returns in OCTET STRING values were forcing conversion to hex (such as in varbind values in responses) as if they were non-printable characters.
• A crash could occur if the environment variable for pointing to the license key file were mistakenly set to a directory instead.

• A “wrong # args” error could occur when previewing a single OBJECT-TYPE in SMI format (the error did not occur when previewing the whole module).

Changes affecting both MIB Smithy and MIB Smithy SDK:

• The “piberrors” type in the XML-SMI Schema document was not correct and did not match the implementation and has been corrected.
• Newlines and carriage returns in OCTET STRING values were forcing conversion to hex (such as in varbind values in responses) as if they were on-printable characters.
• A crash could occur if the environment variable for pointing to the license key file were mistakenly set to a directory instead.

Also, when such failure occurred due to the duplicate definition, double-clicking on the error in the compiler log should have opened the text file editor for manual correction, but instead caused an “invalid workspace type” error.

Both of these issues have been corrected in the 4.0.6 release.

While I expect all posts will be categorized under either “News” or “Articles” (with additional categories as appropriate), you’ll notice that the categories listed for posts now have feed icons next to them, which you can use to subscribe to more specific categories. The “News+Articles” feed is still the feed for the full blog.

If you’re already subscribed to a feed, you may wish to resubscribe as paths have been changed (e.g. the “News” feed is now “/blog/category/news/feed/” instead of “/news_feed.php”). Redirects are in place so your subscription should continue to operate as before even if you don’t, but resubscribing will reduce the number of requests your client needs to send.

My apologies if this causes any trouble. The dust is still settling a bit on the new systems.