Deploying to gh-pages from @ e330abf 🚀

feed.xml

@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en"><generator uri="https://jekyllrb.com/" version="4.3.3">Jekyll</generator><link href="https://1jungu.github.io/feed.xml" rel="self" type="application/atom+xml"/><link href="https://1jungu.github.io/" rel="alternate" type="text/html" hreflang="en"/><updated>2024-08-30T13:37:41+00:00</updated><id>https://1jungu.github.io/feed.xml</id><title type="html">Jun Gu’s homepage</title><subtitle>A simple, whitespace theme for academics. Based on [*folio](https://github.com/bogoli/-folio) design. </subtitle><entry><title type="html">How to use sshfs to mount remote file systems on Windows</title><link href="https://1jungu.github.io/blog/2024/How-to-use-sshfs/" rel="alternate" type="text/html" title="How to use sshfs to mount remote file systems on Windows"/><published>2024-02-15T00:00:00+00:00</published><updated>2024-02-15T00:00:00+00:00</updated><id>https://1jungu.github.io/blog/2024/How-to-use-sshfs</id><content type="html" xml:base="https://1jungu.github.io/blog/2024/How-to-use-sshfs/"><![CDATA[<h2 id="1-mount-remote-file-system-to-windows-system">1 Mount remote file system to Windows system</h2> <p>Test</p> <h3 id="11-install-necessary-software">1.1 Install necessary software</h3> <p><a href="https://winfsp.dev/rel/">WinFsp</a></p> <p>It requires <a href="https://github.com/winfsp/sshfs-win">winfsp/sshfs-win: SSHFS For Windows</a> installed. There are two kinds of installer (x86 vs x64) to choose.</p> <blockquote> <p>“x86” and “x64” are terms describing different families of computer architecture. <strong>x86</strong>: This term originally refers to a series of Intel microprocessors starting with the 8086 and including the 80186, 80286, 80386, and 80486. The term “x86” is used because the names of several of Intel’s processors ended in “86”. It has since come to refer more generally to any <strong>32-bit</strong> processor using a similar instruction set. An x86 (32-bit) processor can directly access up to 4 gigabytes of memory. <strong>x64</strong>: This term refers to a 64-bit extension of the x86 architecture. The extension was originally developed by <strong>AMD</strong> and named “x86-64”, but it is also known as “x64” in Windows environments. This <strong>64-bit</strong> architecture removes the 4-gigabyte memory limit of x86 and can theoretically address up to 18.4 million terabytes of memory. In addition, x64 architectures typically process data in larger chunks (64 bits at a time), which can lead to better performance for certain kinds of tasks.</p> </blockquote> <p>It’s worth noting that most most modern desktop and laptop processors are based on the x64 architecture and can run both x86 (32-bit) and x64 (64-bit) software. Currently, <code class="language-plaintext highlighter-rouge">x64</code> is your best your choice and should be checked in your system info.</p> <h3 id="12-install-gui-software">1.2 Install GUI software</h3> <p>If you want to use <a href="https://github.com/evsar3/sshfs-win-manager">GUI software</a>, <a href="https://winfsp.dev/rel/">WinFsp</a> is <strong>NOT</strong> necessary to install on your system, but also requires <strong>SSHFS</strong> installed.</p> <p>Be sure check sshfs binary path in setting UI</p> <p><img src="/assets/img/sshfs_exe.png#pic_center" alt="sshfs_exe.png"/></p> <p>Detailed guide could be seen <a href="https://blog.xieqiaokang.com/posts/505416489.html">here</a></p> <h3 id="13-limitations">1.3 Limitations</h3> <ol> <li>Don’t support keyboard-interactive authentication<sup id="fnref:1" role="doc-noteref"><a href="#fn:1" class="footnote" rel="footnote">1</a></sup> such as google authenticator<sup id="fnref:2" role="doc-noteref"><a href="#fn:2" class="footnote" rel="footnote">2</a></sup></li> <li>Using pubkey authentication is a trade-off solution but could threaten the security.</li> <li>Some remote machine could forbid pubkey login in <code class="language-plaintext highlighter-rouge">sshd_config</code> <code class="language-plaintext highlighter-rouge">PubkeyAuthentication no</code></li> </ol> <h2 id="2-solutions-using-wsl2">2 Solutions using WSL2</h2> <p>If you use ubuntu distribution in WSL2, follow this steps</p> <div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code>1. <span class="nb">sudo </span>apt-get <span class="nb">install </span>sshfs
+<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en"><generator uri="https://jekyllrb.com/" version="4.3.3">Jekyll</generator><link href="https://1jungu.github.io/feed.xml" rel="self" type="application/atom+xml"/><link href="https://1jungu.github.io/" rel="alternate" type="text/html" hreflang="en"/><updated>2024-08-30T13:54:10+00:00</updated><id>https://1jungu.github.io/feed.xml</id><title type="html">Jun Gu’s homepage</title><subtitle>A simple, whitespace theme for academics. Based on [*folio](https://github.com/bogoli/-folio) design. </subtitle><entry><title type="html">How to use sshfs to mount remote file systems on Windows</title><link href="https://1jungu.github.io/blog/2024/How-to-use-sshfs/" rel="alternate" type="text/html" title="How to use sshfs to mount remote file systems on Windows"/><published>2024-02-15T00:00:00+00:00</published><updated>2024-02-15T00:00:00+00:00</updated><id>https://1jungu.github.io/blog/2024/How-to-use-sshfs</id><content type="html" xml:base="https://1jungu.github.io/blog/2024/How-to-use-sshfs/"><![CDATA[<h2 id="1-mount-remote-file-system-to-windows-system">1 Mount remote file system to Windows system</h2> <p>Test</p> <h3 id="11-install-necessary-software">1.1 Install necessary software</h3> <p><a href="https://winfsp.dev/rel/">WinFsp</a></p> <p>It requires <a href="https://github.com/winfsp/sshfs-win">winfsp/sshfs-win: SSHFS For Windows</a> installed. There are two kinds of installer (x86 vs x64) to choose.</p> <blockquote> <p>“x86” and “x64” are terms describing different families of computer architecture. <strong>x86</strong>: This term originally refers to a series of Intel microprocessors starting with the 8086 and including the 80186, 80286, 80386, and 80486. The term “x86” is used because the names of several of Intel’s processors ended in “86”. It has since come to refer more generally to any <strong>32-bit</strong> processor using a similar instruction set. An x86 (32-bit) processor can directly access up to 4 gigabytes of memory. <strong>x64</strong>: This term refers to a 64-bit extension of the x86 architecture. The extension was originally developed by <strong>AMD</strong> and named “x86-64”, but it is also known as “x64” in Windows environments. This <strong>64-bit</strong> architecture removes the 4-gigabyte memory limit of x86 and can theoretically address up to 18.4 million terabytes of memory. In addition, x64 architectures typically process data in larger chunks (64 bits at a time), which can lead to better performance for certain kinds of tasks.</p> </blockquote> <p>It’s worth noting that most most modern desktop and laptop processors are based on the x64 architecture and can run both x86 (32-bit) and x64 (64-bit) software. Currently, <code class="language-plaintext highlighter-rouge">x64</code> is your best your choice and should be checked in your system info.</p> <h3 id="12-install-gui-software">1.2 Install GUI software</h3> <p>If you want to use <a href="https://github.com/evsar3/sshfs-win-manager">GUI software</a>, <a href="https://winfsp.dev/rel/">WinFsp</a> is <strong>NOT</strong> necessary to install on your system, but also requires <strong>SSHFS</strong> installed.</p> <p>Be sure check sshfs binary path in setting UI</p> <p><img src="/assets/img/sshfs_exe.png#pic_center" alt="sshfs_exe.png"/></p> <p>Detailed guide could be seen <a href="https://blog.xieqiaokang.com/posts/505416489.html">here</a></p> <h3 id="13-limitations">1.3 Limitations</h3> <ol> <li>Don’t support keyboard-interactive authentication<sup id="fnref:1" role="doc-noteref"><a href="#fn:1" class="footnote" rel="footnote">1</a></sup> such as google authenticator<sup id="fnref:2" role="doc-noteref"><a href="#fn:2" class="footnote" rel="footnote">2</a></sup></li> <li>Using pubkey authentication is a trade-off solution but could threaten the security.</li> <li>Some remote machine could forbid pubkey login in <code class="language-plaintext highlighter-rouge">sshd_config</code> <code class="language-plaintext highlighter-rouge">PubkeyAuthentication no</code></li> </ol> <h2 id="2-solutions-using-wsl2">2 Solutions using WSL2</h2> <p>If you use ubuntu distribution in WSL2, follow this steps</p> <div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code>1. <span class="nb">sudo </span>apt-get <span class="nb">install </span>sshfs
 2. <span class="nb">mkdir</span> <span class="nt">-p</span> mountpoint 
 3. <span class="nb">sudo </span>sshfs <span class="nt">-o</span> allow_other user@host:/path /mountpoint <span class="nt">-p</span> port <span class="c">#port is your ssh port</span>
 4. <span class="c">#you can view remote file systems in ubuntu and Windows Explorer</span>