Release 0.4.2#2
Merged
Merged
Conversation
The permission check already rejects a group- or other-accessible identity. This adds the file-type half: the load target must resolve to a regular file, not a directory, device, fifo, or socket. Symlinks are followed rather than rejected, so a Kubernetes Secret volume (which mounts each file as a symlink) still works; the resolved target's type and mode are enforced, and a dangling symlink fails closed. Covered by a unit test. Co-authored-by: AI <noreply+norm@overpay.com>
The getrawtransaction, sendrawtransaction, and transparent address-index paths built their connection and transport errors directly, bypassing the generic error funnel, so the zebra host, port, and cookie-file path leaked to the RPC client. Route those sites through a helper that logs the full detail server-side and returns a fixed generic message; disconnect logging still records the reason. Covered by an offline actor test. Co-authored-by: AI <noreply+norm@overpay.com>
Transitive dependency via rayon. A new advisory (an invalid pointer dereference in the fmt::Pointer impl for Atomic and Shared) fails the advisories gate on the current lockfile; zecd has no first-party use of the affected impl. Lockfile-only patch bump from 0.9.18 to 0.9.20. Co-authored-by: AI <noreply+norm@overpay.com>
The four-rung privacy ladder dropped its top rung in the transparent-recipient pre-check, so build_payment rejected a bare transparent recipient under AllowFullyTransparent with a -8 error, the exact send that policy exists to permit. AllowFullyTransparent is strictly more permissive than AllowRevealedRecipients, so it must permit any transparent recipient the latter does. Guarded by a unit test asserting the full four-rung ladder. Co-authored-by: AI <noreply+norm@overpay.com>
emersonian
force-pushed
the
feature/v0.4.2
branch
from
July 7, 2026 15:47
fb4b780 to
5ad4b36
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixed
z_sendmanywithprivacyPolicy=AllowFullyTransparentno longer rejects a bare transparent recipient; the top privacy rung had been dropped, so the send was wrongly refused as needingAllowRevealedRecipients.Security
getrawtransaction,sendrawtransaction, and the transparent address-index lookups no longer leak the upstream zebra host, port, or cookie-file path to the RPC client; the detail is logged server-side and a generic message is returned.crossbeam-epochto 0.9.20 for RUSTSEC-2026-0204.