<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Linux Server on Naman&#39;s blog</title>
    <link>https://blog.cyberloki.dev/tags/linux-server/</link>
    <description>Recent content in Linux Server on Naman&#39;s blog</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 05 May 2024 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.cyberloki.dev/tags/linux-server/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to manage a server on a network you don&#39;t control?</title>
      <link>https://blog.cyberloki.dev/posts/server-on-campus-wifi/</link>
      <pubDate>Sun, 05 May 2024 00:00:00 +0000</pubDate>
      <guid>https://blog.cyberloki.dev/posts/server-on-campus-wifi/</guid>
      <description>Preface Link to heading Most students in colleges probably don&amp;rsquo;t have their own server hardware using the campus WiFi. There are several issues with this configuration:&#xA;You don&amp;rsquo;t control the network, so your server can go offline in case of a planned/unplanned outage All your traffic is probably recorded You&amp;rsquo;re probably MITMed if they&amp;rsquo;re using an SSL Proxy You don&amp;rsquo;t know if your server will get the same IP address as the last time or not You probably have some sort of webpage based login preventing automatic WiFi connection You&amp;rsquo;re a normal person who does not own a server in the first place(lol) You&amp;rsquo;ll probably not want to use such a network for anything other than Spotify and some gaming.</description>
    </item>
  </channel>
</rss>
