CommitWatch RSS
AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 15 Bitcoin

build: move default FRESH_CLONE location from /tmp to /var/tmp

ELcd25fe4a View source ↗
Public commit record

What the developer wrote

Authored by SomberNight

85/100 · Strong
build: move default FRESH_CLONE location from /tmp to /var/tmp

Apparently many distros these days mount /tmp as RAM-disk.
Even debian (starting with 13) does this now.
The Android build needs to store dozens of gigs, so RAM is often not sufficiently large.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit simply changes the default temporary directory used during Electrum's build process from /tmp to /var/tmp. The reason is practical: many Linux distributions now put /tmp in memory (RAM disk), and the Android build needs to store tens of gigabytes, which can exceed available RAM. This is a build reliability change, not a security fix.

Recommended action

No security action needed. Treat as a routine build/maintenance improvement.

Security signals we found

No strong security signals were identified.

Risk score

Why this scored 15/100

Our methodology →
Potential impact 0/30
Exploitability 0/25
Stealth signal 0/15
Affected reach 0/15
Confidence 10/10
Evidence quality 5/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.

More from Electrum

Related watches

Low 42 AI analysisMessage 73 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

Merge pull request #10830 from accumulator/qml_trustedcoin_wallet_scope

This change fixes a programming mistake in Electrum's mobile/QML user interface where the trustedcoin two-factor authentication (2FA) plugin stored wallet, transaction, and callback information as shared class-level data instead of per-use…

Class-level mutable state for security-critical objects (wallet, transaction, success/failure callbacks) replaced with per-request closurePotential cross-request state collision in 2FA OTP signing flowRemoval of plugin-global self.wallet/self.tx/self.on_success/self.on_failure
a357e86fby ghost43+29−293 files
No security note in commit
Open full analysis →Source commit ↗
Low 49 AI analysisMessage 73 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

Merge pull request #10853 from f321x/swapserver_negative_nonce

This patch fixes a small bug in how Electrum checks proof-of-work (PoW) nonces from Nostr swap server announcements. Previously, a missing or negative nonce was treated as having zero PoW, which is correct for missing nonces but the code a…

Input validation gap: negative PoW nonce acceptedPotential DoS/crash due to unexpected negative value in cryptographic hash pathValidation moved into exception-handled parsing block
0d6df530by ghost43+2−22 files
No security note in commit
Open full analysis →Source commit ↗
Low 37 AI analysisMessage 60 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

swaps: handle negative PoW nonce gracefully

This commit fixes a small bug in Electrum's submarine swap feature. When a swap server advertises itself using a Nostr event, the client checks a 'proof-of-work nonce' to verify the server did enough computational work. Before the patch, a…

Input validation hardening for externally supplied PoW nonceNegative integer nonce could bypass or distort proof-of-work scoringNostr swap announcement parsing is an untrusted input surface
290c0a48by f321x+2−22 files
No security note in commit
Open full analysis →Source commit ↗