Light

Episode #1015 Quiz

Spatial-Domain Wireless Jamming
Date: 2025-03-04 | Length: 2.5 hrs | Episode page at twit.tv

About this episode

Episode 1015 explores spatial-domain wireless jamming using Reconfigurable Intelligent Surfaces (RIS), a passive tech that digitally controls radio wave reflections to selectively disrupt targeted WiFi devices without affecting neighbors even millimeters away. This physical-layer jamming bypasses protocol-level defenses, highlighting a novel attack vector with undetectable, low-power focused interference and potential countermeasures.

Your name and email are stored only in your browser local storage for convenience. They are not retained server-side.

NameEmail

Question 1: According to the Security Now! episode, why did Mozilla remove the explicit promise in Firefox's privacy policy stating that it would never sell user data?

Question 1

According to the Security Now! episode, why did Mozilla remove the explicit promise in Firefox's privacy policy stating that it would never sell user data?

Because user backlash over selling data forced Mozilla to explicitly confirm they buy data but do not sell it. Because Firefox is transitioning to a fully paid subscription model removing the need for privacy promises. Because Firefox planned to begin selling detailed user data to advertisers to increase revenue. Because some legal jurisdictions define 'sale of data' so broadly that the promise became legally inaccurate and required clarification.

Question 2: In the aftermath of the $1.5 billion Ethereum heist involving Bybit, what was identified as the primary security failure?

Question 2

In the aftermath of the $1.5 billion Ethereum heist involving Bybit, what was identified as the primary security failure?

Ethereum blockchain vulnerabilities were exploited to directly rewrite transaction history and withdraw funds. Bybit's own network was directly hacked by North Korean attackers exploiting a vulnerability in their servers. A supplier service called Safe{Wallet} was hacked, allowing malicious code that targeted Bybit's multi-signature smart contracts. Bybit employees used weak credentials that were compromised, leading to unauthorized fund transfers.

Question 3: What key difference differentiates Firefox's approach to Manifest V3 from Google's Chrome, according to the episode?

Question 3

What key difference differentiates Firefox's approach to Manifest V3 from Google's Chrome, according to the episode?

Firefox replaced blockingWebRequest with declarativeNetRequest, limiting extension capabilities similar to Chrome. Firefox removed support for uBlock Origin entirely due to security concerns with Manifest V2. Firefox has dropped Manifest V2 entirely and only supports V3, unlike Chrome which supports both V2 and V3. Firefox supports both Manifest V2 and V3, allowing uBlock Origin to continue functioning fully, whereas Chrome has fully phased out Manifest V2.

Question 4: According to the episode, which of the following describes how Reconfigurable Intelligent Surfaces (RIS) enable targeted spatial-domain wireless jamming?

Question 4

According to the episode, which of the following describes how Reconfigurable Intelligent Surfaces (RIS) enable targeted spatial-domain wireless jamming?

RIS encrypt wireless signals at the protocol layer to prevent unauthorized devices from decoding transmissions. RIS actively transmit high-power jamming signals focused narrowly to disrupt a single device's communication only. RIS use reactive jamming by decoding packets in real-time and interfering with specific transmissions selectively. RIS passively reflect existing ambient radio signals with digitally controlled phase shifts to selectively jam targeted devices without affecting nearby ones.

Question 5: Which of the following statements about memory-safe programming languages was emphasized in the episode's discussion referencing the ACM's call for standardization?

Question 5

Which of the following statements about memory-safe programming languages was emphasized in the episode's discussion referencing the ACM's call for standardization?

Memory-safe languages prevent many security vulnerabilities by automatically managing access to memory, reducing issues like buffer overflows and use-after-free errors. C and C++ are considered memory-safe languages because they provide direct hardware access and fine control over memory usage. Memory-safe languages are slower and less stable than C and C++, which is why adoption has been limited despite security benefits. Memory safety primarily affects graphical user interfaces and has little impact on core system stability or security.

Cancel

My Data//Security & Privacy//Clear Local Data

© 2026 Ken ArmstrongSecurity Now™ is a trademark of TWiT LLC. All trademarks and copyrights of the Security Now podcast are respected and reserved to their respective holders.
This is a hobby project made with love and admiration for what Steve Gibson and Leo Laporte have built over 20 years.