Skip to content

ASN.1 Editor v23.10.24
Compare
Choose a tag to compare
@Crypt32 Crypt32 released this 24 Oct 16:39
· 37 commits to master since this release
v23.10.24
4f568b8

.NET Framework requirements

ASN.1 Editor is now compiled under .NET Framework 4.7.2 (previously, it was .NET 4.5 and previous release was mistakenly compiled under .NET 4.8).

Tabbed Documents

This release adds tabbed document support. Now, you can view and edit multiple ASN.1-encoded files in single window:
image
Now, New command creates a new tab instead of resetting entire window.
Tabbed documents support common shortcuts:

  • Create new tab: Ctrl+N or Ctrl+T (either will work)
  • Close active tab: Ctrl+F4
  • Save all tabs: Ctrl+Shift+S
  • Switch to next tab: Ctrl+Tab

There are three navigation buttons on a left side of tab strip: image

  • Left and right scroll bar buttons to scroll the tab strip (if all tabs overflow the visible area)
  • Menu button to see all tabs and easily switch between them. Current active tab is highlighted with checkmark and bold font.

Note: there is a known issue that scrollbar isn't scrolling to a new selected tab if it is outside of the visible area. I'm working on it and hope to fix this issue.

Tab headers have its own context menu:
image

Nodes can be copied and pasted across different tabs. That is, you can copy ASN node in one document and paste in another. Node copy/paste functionality doesn't work across different instances of the editor.

Enhanced binary-to-string converter

With latest update of my ASN.1 Parser, ASN.1 Editor received additional cryptography-related PEM headers out of the box. As the result, radiobutton stack on a right side is deprecated and replaced with a dropdown list on a toolbar:
image

OID lookup

By default, ASN.1 Editor ships an OID.txt file with a list of OID <-> Friendly Name mappings that are used to resolve non-standard object identifiers. This list is fixed and replaced with every application update. Now, you can have custom lookup file in your user profile at the following location:

%AppData%\Sysadmins LV\Asn1Editor\OID.txt

The logic is as follows:

  1. Load OID map from OID.txt file stored along with the application
  2. Try to lookup an OID.txt file under current user's profile (see above) and append mappings in runtime database.
  3. User-defined mappings will overwrite all existing mappings (in case of duplicate OID definitions)

As a reminder: OID lookup database is used only when object identifier is not registered on your machine.

What's Changed

Full Changelog: v23.10.20...v23.10.24

Contributors

Crypt32
Assets 3
Loading