From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] About to have fiber internet and need VPN info
Date: Sun, 07 Aug 2022 20:30:43 +0100 [thread overview]
Message-ID: <3154390.AJdgDx1Vlc@lenovo.localdomain> (raw)
In-Reply-To: <CAGfcS_kK=iuM37O4sqTfmNjHx4JViJ_LtcjYY6U57ziECKdt4A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3448 bytes --]
On Sunday, 7 August 2022 19:27:42 BST Rich Freeman wrote:
> On Sun, Aug 7, 2022 at 11:36 AM Michael <confabulate@kintzios.com> wrote:
> > The best a well configured VPN tunnel can offer is a secure connection
> > between client and VPN server, which is handy if you are out and about
> > using untrusted and insecure WiFi hotspots.
> >
> > The only other reason for using a VPN service is to present a different
> > geolocation for the purpose of overcoming country-specific website
> > restrictions.
>
> I think ONLY is a bit strong here. A VPN effectively makes it
> impossible for your ISP to know who you're talking to, and it obscures
> your IP from hosts you are connecting to.
Yes, fair point. I was thinking why would you go to such an effort just to
obscure your comms from your ISP. I'm not saying there aren't use cases
supporting this endeavor. I was thinking more about political activists
operating under oppressive regimes where state-level surveillance would be the
threat model. In this case I would think state actors wouldn't rely on ISPs
alone to share such information, although ISP's data would be tapped into for
good measure.
> Sure, there are ways to defeat this, but most of them are only
> applicable for state-level actors, and the methods available to
> ordinary companies can only identify at best a unique browser profile,
> which only lets them correlate traffic with those they share info with
> to the degree that you use a single browser profile across those
> platforms. For non-web traffic there are generally fewer attacks
> available. Many of the attacks that are often cited like DNS-based
> attacks are not that difficult to prevent (eg by ensuring your DNS
> traffic goes out over the VPN).
Yes, careful VPN implementations would guard against DNS leaks and the like.
> If there are sites you browse using a different browser profile
> (ideally on a VM/etc), and you never use that browser profile for
> ecommerce or activity associated with your normal social media
> accounts, then it is unlikely that those sites will actually be able
> to identify you.
>
> Really the biggest pain with the VPNs is the number of websites that
> actively try to block connections from them or flood you with
> CAPTCHAs. Many more mainstream social media sites/etc also
> effectively require association with a mobile phone number, or trigger
> this behavior if they don't like your IP address. Obviously VPNs can
> be abused to attack hosts or evade bans and generally cause trouble,
> which is a frustration for those who simply don't want companies to
> know who you are.
>
> Bottom line is that just because the NSA can track your connections
> doesn't mean that every random webserver on the planet can do so. The
> few government agencies that are likely to be that well-connected are
> also very interested in keeping the extent of their capabilities
> hidden from each other, and so when they intercept your data they're
> going to guard it even more carefully than you would.
I would sincerely hope so. Can't vouch their contractors and subcontractors
would do the same in all cases though.
> A solution doesn't need to be able to defeat the NSA to be useful.
ACK. It boils down to use cases and requirements. I suppose people who seek
to avoid state surveillance would probably use multilayered encryption and
steganography, or better stay off the Internet all together? ;-)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-08-07 19:30 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 10:57 [gentoo-user] About to have fiber internet and need VPN info Dale
2022-07-16 11:23 ` Federico J. Denkena
2022-07-18 9:23 ` Adam Carter
2022-07-16 13:21 ` Peter Humphrey
2022-07-16 16:41 ` Dale
2022-07-18 9:34 ` Adam Carter
2022-08-05 23:09 ` thelma
2022-07-16 17:00 ` Mark Knecht
2022-07-16 17:17 ` Dale
2022-07-16 17:44 ` Mark Knecht
2022-07-16 17:53 ` Michael
2022-08-04 22:32 ` Dale
2022-08-04 22:46 ` Michael
2022-08-05 20:45 ` Dale
2022-08-05 22:39 ` Michael
2022-08-06 6:07 ` Dale
2022-08-06 8:32 ` Michael
2022-08-06 10:59 ` Dale
2022-08-06 11:08 ` Dale
2022-08-06 12:41 ` Peter Humphrey
2022-08-06 12:42 ` Michael
2022-08-07 6:06 ` William Kenworthy
2022-08-07 15:36 ` Michael
2022-08-07 18:27 ` Rich Freeman
2022-08-07 19:30 ` Michael [this message]
2022-08-08 16:34 ` Laurence Perkins
2022-08-08 23:04 ` Peter Humphrey
2022-08-08 23:35 ` Neil Bothwick
2022-08-09 8:50 ` Michael
2022-08-09 16:21 ` Laurence Perkins
2022-08-05 14:53 ` Laurence Perkins
2022-08-05 23:05 ` Wol
2022-08-05 23:36 ` Peter Humphrey
2022-08-08 16:25 ` Laurence Perkins
2022-08-08 23:07 ` Peter Humphrey
2022-08-08 23:33 ` Neil Bothwick
2022-08-09 16:06 ` Laurence Perkins
2022-08-09 18:20 ` Peter Humphrey
2022-08-08 16:19 ` Laurence Perkins
2022-08-06 11:38 ` Rich Freeman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3154390.AJdgDx1Vlc@lenovo.localdomain \
--to=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox