A desktop SNMP browser, MIB editor and alert router.

A MIB that will not load tells you why

The underlying library answers “Could not load module at X” for a missing file, a PDF, a syntax error on line 412 and an unsatisfiable IMPORTS alike. SnmpLens recovers the real message and reports a stage — read, content, parse, imports, build, semantic — with the position, an excerpt with a caret, and the modules that could not be satisfied along with the symbols each was needed for.

It recognises the files people download by mistake: an HTML error page, a PDF, a zip, a UTF-16 file. All four otherwise arrive as the same sentence.

Credentials are not kept beside the data

Community strings and v3 passphrases are sealed with a key held by the operating system — DPAPI on Windows, the Keychain on macOS, a 0600 file on Linux — and never written next to the database. The settings screen names the backend actually in use rather than saying “encrypted”, because those three protect against different things.

Sealing that fails never falls back to writing plaintext, and never overwrites good ciphertext with a half-sealed object.

Updates are signed, not just downloaded

Every release ships a SHA-256 manifest and an Ed25519 signature over it. The application verifies the signature against a key compiled into the binary, then checks the asset against the now-authenticated manifest — the same model a Linux package repository uses. A build whose signature is missing refuses the update rather than applying it.

An alert that fails leaves a record

Deliveries are queued in a durable outbox and retried with backoff. Whether a failure is retried is decided by the protocol reply code — 4xx transient and 5xx permanent for SMTP, per RFC 5321 — never by searching the text a receiver wrote. A delivery finally given up on is kept and listed, because it is the only record that a notification never arrived.