Package com.pnfsoftware.jeb.core
package com.pnfsoftware.jeb.core
The core package and sub-packages define classes and interfaces to interact with and
develop JEB back-end plugins.
Back-end plugins come in multiple varieties, including:
- Engines plugins: those plugins are loaded by the engine and can run any code.
- Unit plugins (also referred to as parsers): those plugins are used to parse input data and provide results to front-ends. They are primarily used to extend JEB functionality as they allow third-party addition of disassemblers, decompilers, reformatters, deobfuscators, parsers, or binary data transformers of any sort to the JEB base package.
- Decompiler plugins: IR and AST optimizers for
gendec
anddexdec
- See Also:
-
ClassDescriptionSkeleton implementation for
engines plugins
.Skeleton implementation of JEB plugins.Basic implementation for a named artifact that takes a flexibleIInput
object.Manager for Core assets.Bookmark manager used by JEB projects.Definition of a bookmark.Boolean option description used by property definition managers.Floating controller information.Public options forICoreContext
.These objects represent classnames of plugins that are currently being developed.Editable plugins information offer setters to mutate some plugin-info properties such as the name or description.Utility routines forJEB Engines context
.Utility class to handle (parse and get, build and save) some JEB back-end properties.Base interface for artifacts.A core context.A dynamic target plugin is a special type of plugin that takes one or more units as input and provide augmentation for those units.A context for JEB engines.Interface for standard JEB engines plugin.Definition of some input bytes seen by the Core context.A "runtime" artifact, that connects a project, an artifact, and root units.Simple definition for a type-less option, containing a name and a description.Base interface for JEB back-end plugins.IPluginFileEntry<T extends IPlugin>Plugin entry managed by a plugin manager.Plugin information object.JEB plugin manager for external plugins running alongside the JEB back-end components.A runtime project represents a loaded instance of a JEB project.Extended, typed option containing type of definition in addition toIOptionDefinition
.Types of typed options.A unit contribution plugin.An interface implemented by all types that produceunits
.A filter for units, used byRuntimeProjectUtil
utility methods.This decorator interface is used to let users know that arbitrary data objects may be attached to the object.Information about a JEB client (aka, a JEB front-end).JEB constants.Service class used to create or retrieve a reference to the JEB core context.List option description used by property definition managers.An implementation for an option description.Performance counters, reserved for internal debug use.Standard implementation of a plugin information object.A collection of utility methods to navigate and act on JEB projects.Metadata information for a JEB script (type, description, version, etc.).Parser and generator ofScriptMetadata
objects.Standard implementation of the user-data support decorator interface.Version number object.