<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How to build a VPN from scratch in four easy steps without spending one penny in ISC2 Security Congress</title>
    <link>https://community.isc2.org/t5/ISC2-Security-Congress/How-to-build-a-VPN-from-scratch-in-four-easy-steps-without/m-p/34933#M340</link>
    <description>&lt;P&gt;Well... yeah. The solution I documented is supposed to be for the single purpose of connecting remote workers to work. It's split-tunnel anyway, so **by design** it does nothing to protect against the other attack scenarios you mentioned. But even if it weren't split-tunnel, everything coming from that VPN would be from the same IP Address anyway, and so it would be a lousy solution for evading hostile governments. But it was never meant for that - it's only meant to connect remote workers to work.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The attack scenarios you brought up are real and they need a solution - but there are lots of VPN services designed to help solve them, and people have been connecting to them for years.&lt;BR /&gt;&lt;BR /&gt;But - as I think this through - one huge weakness with VPNs in general is, as you pointed out - hostile ISPs can record traffic and analyze it later, and it's easy to spot VPN traffic. But now with COVID-19, if organizations everywhere adopt VPN technology, and now it's easy with my documentation, hostile ISPs can no longer make assumptions about VPN traffic. And so, maybe my documentation has some indirect benefit with the hostile government problem. But I don't think I'll pitch it that way.&lt;/P&gt;</description>
    <pubDate>Sun, 19 Apr 2020 13:28:27 GMT</pubDate>
    <dc:creator>gregscott</dc:creator>
    <dc:date>2020-04-19T13:28:27Z</dc:date>
    <item>
      <title>How to build a VPN from scratch in four easy steps without spending one penny</title>
      <link>https://community.isc2.org/t5/ISC2-Security-Congress/How-to-build-a-VPN-from-scratch-in-four-easy-steps-without/m-p/34929#M338</link>
      <description>&lt;P&gt;In the wake of the COVID-19 crisis and everyone setting up emergency work-from-home infrastructures, here is a detailed cookbook for setting up a VPN from scratch without spending any money. It even has video demos. Enjoy.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://www.dgregscott.com/how-to-build-a-vpn-in-four-easy-steps-without-spending-one-penny/" target="_blank"&gt;https://www.dgregscott.com/how-to-build-a-vpn-in-four-easy-steps-without-spending-one-penny/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- Greg Scott&lt;/P&gt;</description>
      <pubDate>Mon, 09 Oct 2023 09:30:04 GMT</pubDate>
      <guid>https://community.isc2.org/t5/ISC2-Security-Congress/How-to-build-a-VPN-from-scratch-in-four-easy-steps-without/m-p/34929#M338</guid>
      <dc:creator>gregscott</dc:creator>
      <dc:date>2023-10-09T09:30:04Z</dc:date>
    </item>
    <item>
      <title>Re: How to build a VPN from scratch in four easy steps without spending one penny</title>
      <link>https://community.isc2.org/t5/ISC2-Security-Congress/How-to-build-a-VPN-from-scratch-in-four-easy-steps-without/m-p/34931#M339</link>
      <description>&lt;P&gt;The problem is that if you have a single purpose for a VPN, such as connecting to you work, that's great! The real problem is that if you are using a VPN to protect your privacy and defend again possible hacks it becomes a really problem! Far too may silly companies base their security on IP address, so when I have my VPN turned on I either get extra checks or I am not allowed to connect at all. While I do understand the thought that bad actors might be hiding behind these VPNs it completely ignores the more progressive user who simply does not want his ISP recording and selling his traffic. So for those who work in companies who block based on IP, please rethink this Policy!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;John-&lt;/P&gt;</description>
      <pubDate>Sun, 19 Apr 2020 03:48:24 GMT</pubDate>
      <guid>https://community.isc2.org/t5/ISC2-Security-Congress/How-to-build-a-VPN-from-scratch-in-four-easy-steps-without/m-p/34931#M339</guid>
      <dc:creator>JKWiniger</dc:creator>
      <dc:date>2020-04-19T03:48:24Z</dc:date>
    </item>
    <item>
      <title>Re: How to build a VPN from scratch in four easy steps without spending one penny</title>
      <link>https://community.isc2.org/t5/ISC2-Security-Congress/How-to-build-a-VPN-from-scratch-in-four-easy-steps-without/m-p/34933#M340</link>
      <description>&lt;P&gt;Well... yeah. The solution I documented is supposed to be for the single purpose of connecting remote workers to work. It's split-tunnel anyway, so **by design** it does nothing to protect against the other attack scenarios you mentioned. But even if it weren't split-tunnel, everything coming from that VPN would be from the same IP Address anyway, and so it would be a lousy solution for evading hostile governments. But it was never meant for that - it's only meant to connect remote workers to work.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The attack scenarios you brought up are real and they need a solution - but there are lots of VPN services designed to help solve them, and people have been connecting to them for years.&lt;BR /&gt;&lt;BR /&gt;But - as I think this through - one huge weakness with VPNs in general is, as you pointed out - hostile ISPs can record traffic and analyze it later, and it's easy to spot VPN traffic. But now with COVID-19, if organizations everywhere adopt VPN technology, and now it's easy with my documentation, hostile ISPs can no longer make assumptions about VPN traffic. And so, maybe my documentation has some indirect benefit with the hostile government problem. But I don't think I'll pitch it that way.&lt;/P&gt;</description>
      <pubDate>Sun, 19 Apr 2020 13:28:27 GMT</pubDate>
      <guid>https://community.isc2.org/t5/ISC2-Security-Congress/How-to-build-a-VPN-from-scratch-in-four-easy-steps-without/m-p/34933#M340</guid>
      <dc:creator>gregscott</dc:creator>
      <dc:date>2020-04-19T13:28:27Z</dc:date>
    </item>
  </channel>
</rss>

