Thank you for the precious star rating. I am rooting for you, woojja, as you silently push forward toward completing the course.

It was interesting to listen to. However, I'm a bit worried because I've heard that if you open up a network by running a server at home, hackers somehow find out instantly and swarm in like a pack of dogs, leaving everything in ruins. It makes me wonder if it's really okay to open it up like this. Also, would the setup be very difficult on a MAC? Please cover the settings for Mac as well. It would be even better if you could do it on YouTube... I really enjoyed the great lecture. ^______________^

Hello woojja, thank you so much for enjoying the lectures. As you mentioned, your point that running a server at home and manually opening network ports can be a security risk is a very accurate and reasonable concern. Based on your inquiry, it seems you are curious about the cases for Lecture 6 and Lecture 2, so I will explain each. **Lecture 6. Remote Tunnels Method (Very Safe)** This method is like "not leaving the door of your house open, but rather you going out first through a trusted passage." - **No Inbound Port Opening:** You do not need to touch router settings (port forwarding) to allow external access. Since your PC initiates a secure connection request to Microsoft's servers first, even if a hacker finds your IP, the "door" to enter is closed. - **Strong Authentication:** The tunnel is only activated when you log in with your own GitHub/Microsoft account. Third parties without account permissions are fundamentally blocked from access. - **End-to-End Encryption:** All data is encrypted during transmission, making interception nearly impossible. (*) Security becomes perfect if you set up 'Two-Factor Authentication (OTP)' for the GitHub or Microsoft account you use to log in to the VS Code Remote Tunnels feature. **Lecture 2. code-server Method (Security Configuration Required)** The code-server method has a completely different security mechanism than the Remote Tunnels (MS relay method) explained above. Since code-server runs a web server directly on your server (or home PC) and allows external access, there is a real possibility of becoming a 'target for hackers' as you worried. However, you can operate it safely enough if you have the following 'shields': - **Basic Authentication:** Ensure that code-server can only be accessed through a strong password. - **Communication Encryption (HTTPS):** By converting data into code for transmission, no one can see the content even if it is intercepted in the middle. - **Utilizing Cloudflare Tunnel:** If you are uneasy about direct port forwarding, I recommend this tool. It hides the server's actual address and ensures access only through Cloudflare's security network. (You can use it by purchasing and connecting a cheap domain from Cloudflare, allowing secure access without opening ports.) I recommend checking the details of Cloudflare Tunnel via the internet or AI. **In summary:** - The **Lecture 6 method** is much safer than opening a typical server because it uses a 'secret passage' provided by a trusted security company like Microsoft. - For the **Lecture 2 method**, you can build a professional-level secure development environment if you add additional security measures such as HTTPS and Cloudflare Tunnel. Regarding your question about settings on Mac, I unfortunately produce my lectures primarily for Windows and Linux environments, so please understand that there are limitations in providing answers based on direct testing with Mac equipment (I don't have a Mac ^^;). However, VS Code is designed to provide almost the same user experience regardless of the operating system. In particular, the installation process for Remote Tunnels or code-server covered today works with almost the same commands in the Mac terminal. I hope this provides a sufficient answer, and please feel free to leave a question whenever you have more!

This content makes me smile and warms my heart. Thank you so much for the detailed response. Have a happy day~ ^________^