Skip to content

Ghidra is a software reverse engineering (SRE) framework

Merge remote-tracking branch 'origin/GP-6829_ghidra1_TrustStores'

ghidra1dd3679488ddd
diff --cc Ghidra/Configurations/Public_Release/src/global/docs/WhatsNew.md
index 051f9972e3,6734410c3a..062b5f9b61
--- a/Ghidra/Configurations/Public_Release/src/global/docs/WhatsNew.md
+++ b/Ghidra/Configurations/Public_Release/src/global/docs/WhatsNew.md
@@@ -68,86 -73,68 +73,76 @@@ older client version of Ghidra should a
## Security Related Fixes
- ### RMI Serialization Filter Improvements
- RMI Serialization filters for the Ghidra Server have been tightened and similar filters have been
- added to Ghidra client applications which may communicate with a Ghidra Server. Please report
- any unexpected *InvalidClassException* errors, which may occur, to the Ghidra team. If this does occur,
- please check your Ghidra Server or application log files for entries which indicate any filter
- rejections and the name of the offending class.
-
- ### Ghidra Server - PKI Authentication Vulnerability
- For those Ghidra Server deployments which utilize PKI Authentication mode (-a2), a logic bug
- within the authentication callback to the server could allow an attacker to authenticate as a
- different user without having access to their private key. Prior to completing the forged
- authentication callback, the attacker would still need to successfully complete a fully authenticated
- TLS connection with the Ghidra Server based on the installed Certificate Authorities (CAs).
-
- ## Bitfields
- The Decompiler now recovers and displays the names of **bitfield** components in structured
- data-types, when analyzing code that manipulates them.
-
- Low-level details of how code isolates an individual bitfield are simplified away in Decompiler
- output. Instead, the bitfield is displayed as a single logical value, by name, using standard field
- access notation. Both expressions that *read from* or *write to* a bitfield can be recovered.
-
- Many optimized expressions that read, write, or compare multiple bitfields at once can also be
- broken out so that the individual bitfields are visible.
-
- ## Objective-C
- The old Objective-C analyzers:
- * Objective-C 2 Class
- * Objective-C 2 Decompiler Message
- * Objective-C Message (Prototype)
-
- have been been reworked and replaced with versions that are more compatible with modern
- Objective-C binaries:
- * Objective-C Type Metadata Analyzer
- * Objective-C Message Analyzer
-
- Where possible, calls to `_objc_msgSend()` and its variations (including `_objc_msgSend$` stubs)
- have been overridden to reference the actual target method (if discoverable), which results in a
- much more user-friendly decompilation.
-
- Additionally, a variety of AARCH64 call-fixups have been implemented which further clean up
- decompilation, hiding much of the noise that things like Automatic Reference Counting (ARC) can
- generate.
-
- ## Debuginfod
- We've added support for downloading DWARF debug files from HTTP[s] debuginfod servers, as well as
- searching the user's `$HOME/.cache/debuginfod_client` directory. You can configure these options in
- the Code Browser tool's **Edit | DWARF External Debug Config** menu.
-
- ## Microsoft Demangler
- We've added **Output Options** to the Microsoft Demangler to control the demangled output
- presentation, changing it from the standard form.
-
- One option controls the inclusion of user-defined-type tags (e.g., "struct") when the type is used
- as a function or template argument. When the tags are not applied, it can reduce the bifurcation
- of symbols within namespaces where some namespaces have the tags and others do not. This can happen
- when non-mangled symbols do not include the tag and demangled symbols do.
-
- Another option controls whether the standard **\`anonymous namespace'** is presented in a
- **_anon_ABCD01234** form using its encoded anonymous namespace number. When the new form is used,
- it can reduce the commingling of symbols from two distinct anonymous namespaces into one generic
- **\`anonymous namespace'**. Note, however, that non-mangled symbols with the generic
- **\`anonymous namespace'** (or one of its variants) can still be found in a program, coming from
- other sources, such as PDB. There is currently no simple way to try to match these with the new
- encoded form; thus, using the encoded form can also create bifurcation in the namespace.
-
- ## Processors
- Added the Hexagon Processor module. The instruction syntax is modified from the Hexagon manual to better
- fit Ghidra's mnemonic and operand Listing API. This processor also introduces the first use of Ghidra's
- Sleigh **crossbuild** feature which is used for weaving pcode for parallel processor architectures such
- as the Hexagon.
-
- There have been a significant number of missing/extension instructions added to the ARM, AARCH64,
- and X86 processors. Additionally since 12.0 there a myriad of processor specification bugs have been fixed.
-
- ## Jython Extension
- Jython support is now delivered as a Ghidra Extension, which means an extra step is required to
- install it. If you require Jython, simply go to `File -> Install Extensions` in the Ghidra
- Front End GUI and check "Jython". Restart Ghidra and Jython support will be enabled.
+ ### TLS/SSL Client/Server Changes
+
+ Ghidra Server and BSim PostgreSQL Server deployments now highly encourage the use of a CA-signed
+ server certificate. In addition, Ghidra clients will now enforce server-authentication
+ for all SSL/TLS connections. This was previously not the case with earlier versions of Ghidra.
+ This server-authentication also applies to accessing servers accessed via the loopback/localhost
+ interface, although the property `ghidra.disable.loopback.server.authentication` can be set `true` in
+ `support/launch.properties` file to disable such local server authentication for testing.
+
+ A suitable keystore must be obtained from a CA signing-authority or a self-signed certificate file may
+ be generated but is not preferred. If needed, the new `server/certTool` command provided with Ghidra
+ may be used to assist with the keystore request and generation.
+
+ Each client must ensure that trusted certificates are added to an appropriate trust store.
+ Ghidra clients now support the use of OS managed certificate trust stores as well as default trust stores
+ supplied with the Java installation. For Windows and macOS, the system provided `User Certificate
+ Manager` may be launched from the Ghidra projct window (Edit -> Manage Certificates...). For Unix/Linux
+ the property `ghidra.unix.default.cacerts` may be optionally specified in `support/launch.properties` to
+ identify a directory path where unencrypted PEM or DER trusted certificate files may be added. In the case of a
+ server which uses a self-signed certificate, that certificate would need to be added by each client as a trusted
+ certificate. Otherwise, all the CA certificates in the server's CA-chain should be added if not already
+ present.
+
+ #### Ghidra Server
+
+ If the `server/server.conf` file does not specify a `ghidra.keystore` the server will continue to auto-generate
+ a temporary self-signed server certificate. However, when this occurs the server will now only listen
+ for loopback connections on the localhost interface. If remote connections are required, a proper
+ keystore must be specified. If local access only is acceptable, a Ghidra client may set the
+ `ghidra.disable.loopback.server.authentication=true` property in the `support/launch.properties` file with caution.
+ Otherwise, a keystore must be generated.
+
+ See `server/svrREADME.md or server/svrREADME.html for more details.
+
+ #### BSim PostgreSQL Server
+
+ A BSim PostgreSQL data directory that was configured with a previous version of Ghidra will
+ not have any new constraints other than client connections now performing server
+ authentication. If using a self-signed certificate it will need to be added to client
+ trust stores or a properly signed server certificate/keystore obtained.
+
+ New BSim PostgreSQL deployments should specify a server keystore when initialized. If a keystore
+ is not specified, the server will use an auto-generated self-signed certificate which will need to
+ be added to client trust stores. When either a keystore is not specified, or the `trust` authentication
+ mode is used (`--auth=trust`), the server will be configured to listen to loopback connections on the
+ localhost interface only.
+
+ See Ghidra GUI Help Content related to BSim Database Configuration and `bsim_ctl` for more details.
+
+ ## BSim PostgreSQL Deployment and Control (bsim_ctl)
+
+ Extensive changes have been made to the BSim PostgreSQL control script. New `bsim_ctl` commands
+ have been added for initializing and reconfiguring a server deployment (`init`, `configure`). Once
+ a deployment is configured, the following commands are used to manage its state: `start`, `stop`, and
+ `restart`. In addition, the ability to install as a Linux Service has been added using the commands
+ `install-service` and `uninstall-service`. A new command `listusers` has also been added to aid with
+ user management.
+
+ When initializing or configuring a PostgreSQL server, `password` authentication mode is now the default
+ if the `--auth` option is not specified. This differs from previous releases which defaulted to `trust`
+ authentication. In general, use of `trust` authentication should be avoided.
+
++
++
++
++... To Be Continued ...
++
++
++
+
## Additional Bug Fixes and Enhancements
Numerous other new features, improvements, and bug fixes are fully listed in the
[Change History](ChangeHistory.md) file.