<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Privacy on Skycoin Blog</title><link>https://blog.theskywirenetwork.net/tags/privacy/</link><description>Recent content in Privacy on Skycoin Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 09 Feb 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.theskywirenetwork.net/tags/privacy/index.xml" rel="self" type="application/rss+xml"/><item><title>DmsgWeb: Anonymous Websites Over DMSG</title><link>https://blog.theskywirenetwork.net/posts/dmsgweb-anonymous-port-forwarding/</link><pubDate>Fri, 09 Feb 2024 00:00:00 +0000</pubDate><guid>https://blog.theskywirenetwork.net/posts/dmsgweb-anonymous-port-forwarding/</guid><description>&lt;h3 id="dmsgweb--anonymous-port-forwarding-over-dmsg"&gt;DmsgWeb — Anonymous Port Forwarding Over DMSG&lt;/h3&gt;
&lt;p&gt;Skywire v1.3.17 introduces &lt;strong&gt;DmsgWeb&lt;/strong&gt;, a new utility for hosting and accessing websites over the DMSG overlay network. DmsgWeb provides a resolving SOCKS5 proxy — similar to and inspired by I2P — that lets a web browser access sites hosted entirely within the DMSG network.&lt;/p&gt;
&lt;h3 id="how-it-works"&gt;How It Works&lt;/h3&gt;
&lt;p&gt;DmsgWeb operates in two modes:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Client&lt;/strong&gt; (&lt;code&gt;skywire dmsg web&lt;/code&gt;) — Runs a local SOCKS5 proxy that resolves &lt;code&gt;.dmsg&lt;/code&gt; domains to DMSG public keys and routes traffic over the encrypted DMSG overlay. Configure your browser to use the proxy, and DMSG-hosted sites become accessible just like any other website. Non-DMSG traffic can optionally be routed through a Skywire SOCKS5 proxy for additional privacy.&lt;/p&gt;</description></item><item><title>Question Regarding Latency and Privacy of the Meshnet</title><link>https://blog.theskywirenetwork.net/posts/question-regarding-latency-and-privacy-of-the-meshnet/</link><pubDate>Fri, 18 Aug 2017 00:00:00 +0000</pubDate><guid>https://blog.theskywirenetwork.net/posts/question-regarding-latency-and-privacy-of-the-meshnet/</guid><description>&lt;p&gt;&lt;em&gt;This post refers to Skywire earlier on in its formation, before it was named Skywire. Adapted from a bitcointalk post dated August 09, 2014.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Quote from: &lt;strong&gt;CraigM&lt;/strong&gt; on August 09, 2014, 07:20:24 AM&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;The meshnet is intended to be a nice privacy tool with benefits comparable to tor, but lower latency correct?&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;The meshnet is intended to allow funding nodes via micropayments in skycoin to cover bandwidth costs correct? Doesn&amp;rsquo;t this leave force all node operators to record detailed and published logs (on their personal block chains) describing all the transactions which inherently correspond to everyone who send data through their node? This seems like it would allow any third party to do traffic correlation attacks much like the ones on tor, except you don&amp;rsquo;t need access to the connections. Even if they don&amp;rsquo;t end up being publicly inspectable, logging everything seems like it might have some real issues (it can be requested by law enforcement, and takes up a lot of space)&lt;/p&gt;</description></item></channel></rss>