ASN.1 Editor v24.8.28

What's new

• Introduced a re-designed new tree node creation dialog which allows to specify type tag using different approaches:
  
• added support for RELATIVE_OID type editor

Other quality improvements and bug fixes

• includes ASN.1 binary parser bugs fixed in parser library.
• replaced individual ASN type icons with single sprite sheet by @Crypt32 in #37
• Added CA/Browser forum OIDs by @Crypt32 in #43
• Fixed TextViewer INTEGER and BIT_STRING rendering bugs by @Crypt32 in #44
• implemented #45 by @Crypt32 in #46
• Re-design new node creation dialog by @Crypt32 in #50
• Added editor support for RELATIVE_OID by @Crypt32 in #52

Full Changelog: v23.12.17...v24.8.28

ASN.1 Editor v23.12.17

This release implements the long-requested feature to view some implicit context-specific types as text rather than in hex. This is extremely useful when viewing/editing Subject Alternative Names (SAN) extension, where all alternative name types use CHOICE and ASN.1 Editor showed them as hex dump. Now, I'm trying to figure out if context-specific type consist of ASCII printable characters and if they do, convert them to text.

• SAN extension presentation before:
  
• After:
  

And you can view/edit these types in text mode:

---

In addition, Node Content Editor UI is updated. Text radio button is enabled only when node supports content editing in text mode:

In this case, node content contains non-printable characters, thus Text radio is disabled.

ASN.1 Editor v23.11.24

What's new?

This release adds OID lookup table editor:

In this dialog, you can search, edit and delete OID mappings.

OID lookup editor is accessible from both, main toolbar:

Or from OID node's context menu in ASN tree view:

Or from Edit menu. When you use context or Edit menu item, selected OID is automatically placed into editor form. All you need is to provide friendly name and hit Enter to save. All custom OID mappings are saved in current user's roaming AppData folder and have precedence over built-in OID mappings.

You can edit existing mappings. To edit existing item, you need to delete it first. Press Del button (or context menu on selected OID entry), it will be removed from the list and existing values will be copied directly to form. Provide new friendly name and hit Enter to save it in user dictionary.

Bug fixes

• Application crashes when trying to view license information

ASN.1 Editor v23.10.24

.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:

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:

• 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:

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:

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

• Ref lib update by @Crypt32 in #25
• Ref lib update by @Crypt32 in #26
• Advanced bin2 string by @Crypt32 in #27
• downgraded from .NET 4.8 to .NET 4.7.2 for better compatibility by @Crypt32 in #28
• Tabbed documents by @Crypt32 in #29
• implemented #12 by @Crypt32 in #30

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

ASN.1 Editor v23.10.20

What's Changed

• Update OID.txt by @PorucikPihrt in #3
• Show English friendly names for OIDs by @RufusJWB in #7
• Added OID: commonPKI certHash by @matheller in #23
• Fix of parent window detection in Debug build by @denchukanov in #21
• Asn1 editor v next by @Crypt32 in #24

New Contributors

• @PorucikPihrt made their first contribution in #3
• @RufusJWB made their first contribution in #7
• @matheller made their first contribution in #23
• @denchukanov made their first contribution in #21
• @Crypt32 made their first contribution in #24

Full Changelog: https://github.com/PKISolutions/Asn1Editor.WPF/commits/v23.10.20