<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>Comments on: Your computer can leak data in many ways</title>
	<atom:link href="http://www.epanorama.net/blog/2020/05/06/your-computer-can-leak-data-in-many-ways/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.epanorama.net/blog/2020/05/06/your-computer-can-leak-data-in-many-ways/</link>
	<description>All about electronics and circuit design</description>
	<lastBuildDate>Fri, 10 Apr 2026 21:14:09 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.9.14</generator>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2020/05/06/your-computer-can-leak-data-in-many-ways/comment-page-1/#comment-1692867</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Fri, 25 Sep 2020 15:41:51 +0000</pubDate>
		<guid isPermaLink="false">https://www.epanorama.net/blog/?p=186122#comment-1692867</guid>
		<description><![CDATA[https://www.facebook.com/groups/2600net/permalink/2840397389516701/

WebRTC signaling using sound. Works with all devices that have microphone + speakers. Runs in the browser.
Nearby devices negotiate the WebRTC connection by exchanging the necessary Session Description Protocol (SDP) data via a sequence of audio tones. Upon successful negotiation, a local WebRTC connection is established between the browsers allowing data to be exchanged.
The WebRTC technology allows two browsers running on different devices to connect with each other and exchange data. There is no need to install plugins or download applications. To initiate the connection, the peers exchange contact information (ip address, network ports, session id, etc.). This process is called &quot;signaling&quot;. The WebRTC specification does not define any standard for signaling - the contact exchange can be achieved by any protocol or technology.
In this project the signaling is performed via sound. The signaling sequence looks like this:
Peer A broadcasts an offer for a WebRTC connection by encoding the session data into audio tones
Nearby peer(s) capture the sound emitted by peer A and decode the WebRTC session data
Peer B, who wants to establish connection with peer A, responds with an audio answer. The answer has peer B&#039;s contact information encoded in it. Additionally, peer B starts trying to connect to peer A
Peer A receives the answer from peer B, decodes the transmitted contact data and allows peer B to connect
Connection is established
Try it yourself: ggerganov.github.io/wave-share
https://github.com/ggerganov/wave-share]]></description>
		<content:encoded><![CDATA[<p><a href="https://www.facebook.com/groups/2600net/permalink/2840397389516701/" rel="nofollow">https://www.facebook.com/groups/2600net/permalink/2840397389516701/</a></p>
<p>WebRTC signaling using sound. Works with all devices that have microphone + speakers. Runs in the browser.<br />
Nearby devices negotiate the WebRTC connection by exchanging the necessary Session Description Protocol (SDP) data via a sequence of audio tones. Upon successful negotiation, a local WebRTC connection is established between the browsers allowing data to be exchanged.<br />
The WebRTC technology allows two browsers running on different devices to connect with each other and exchange data. There is no need to install plugins or download applications. To initiate the connection, the peers exchange contact information (ip address, network ports, session id, etc.). This process is called &#8220;signaling&#8221;. The WebRTC specification does not define any standard for signaling &#8211; the contact exchange can be achieved by any protocol or technology.<br />
In this project the signaling is performed via sound. The signaling sequence looks like this:<br />
Peer A broadcasts an offer for a WebRTC connection by encoding the session data into audio tones<br />
Nearby peer(s) capture the sound emitted by peer A and decode the WebRTC session data<br />
Peer B, who wants to establish connection with peer A, responds with an audio answer. The answer has peer B&#8217;s contact information encoded in it. Additionally, peer B starts trying to connect to peer A<br />
Peer A receives the answer from peer B, decodes the transmitted contact data and allows peer B to connect<br />
Connection is established<br />
Try it yourself: ggerganov.github.io/wave-share<br />
<a href="https://github.com/ggerganov/wave-share" rel="nofollow">https://github.com/ggerganov/wave-share</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2020/05/06/your-computer-can-leak-data-in-many-ways/comment-page-1/#comment-1680013</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Sat, 23 May 2020 11:18:43 +0000</pubDate>
		<guid isPermaLink="false">https://www.epanorama.net/blog/?p=186122#comment-1680013</guid>
		<description><![CDATA[Simple chat program using near ultrasonic frequencies. Works without Wifi or Bluetooth and won&#039;t show up in a pcap.
https://github.com/Katee/quietnet]]></description>
		<content:encoded><![CDATA[<p>Simple chat program using near ultrasonic frequencies. Works without Wifi or Bluetooth and won&#8217;t show up in a pcap.<br />
<a href="https://github.com/Katee/quietnet" rel="nofollow">https://github.com/Katee/quietnet</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2020/05/06/your-computer-can-leak-data-in-many-ways/comment-page-1/#comment-1679896</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Fri, 22 May 2020 19:48:36 +0000</pubDate>
		<guid isPermaLink="false">https://www.epanorama.net/blog/?p=186122#comment-1679896</guid>
		<description><![CDATA[OK, so you&#039;ve air-gapped that PC. Cut the speakers. Covered the LEDs. Disconnected the monitor. Now, about the data-leaking power supply unit...
I have no mouth, and I must scream
https://www.theregister.co.uk/2020/05/04/power_supply_attack/]]></description>
		<content:encoded><![CDATA[<p>OK, so you&#8217;ve air-gapped that PC. Cut the speakers. Covered the LEDs. Disconnected the monitor. Now, about the data-leaking power supply unit&#8230;<br />
I have no mouth, and I must scream<br />
<a href="https://www.theregister.co.uk/2020/05/04/power_supply_attack/" rel="nofollow">https://www.theregister.co.uk/2020/05/04/power_supply_attack/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2020/05/06/your-computer-can-leak-data-in-many-ways/comment-page-1/#comment-1679890</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Fri, 22 May 2020 19:30:45 +0000</pubDate>
		<guid isPermaLink="false">https://www.epanorama.net/blog/?p=186122#comment-1679890</guid>
		<description><![CDATA[https://www.tomshardware.com/news/cyberattack-steals-pc-data-through-its-power-supply]]></description>
		<content:encoded><![CDATA[<p><a href="https://www.tomshardware.com/news/cyberattack-steals-pc-data-through-its-power-supply" rel="nofollow">https://www.tomshardware.com/news/cyberattack-steals-pc-data-through-its-power-supply</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2020/05/06/your-computer-can-leak-data-in-many-ways/comment-page-1/#comment-1678358</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Wed, 06 May 2020 21:48:44 +0000</pubDate>
		<guid isPermaLink="false">https://www.epanorama.net/blog/?p=186122#comment-1678358</guid>
		<description><![CDATA[https://en.wikipedia.org/wiki/Van_Eck_phreaking]]></description>
		<content:encoded><![CDATA[<p><a href="https://en.wikipedia.org/wiki/Van_Eck_phreaking" rel="nofollow">https://en.wikipedia.org/wiki/Van_Eck_phreaking</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
