dark

該視頻由███VPN贊助

Total
0
Shares
0
0
0



我試圖寫一個更誠實的VPN廣告。贊助商對此不滿意。 •在██████.com/ honest免費獲得██天的███VPN。

我引用的ASA裁決：https://www.asa.org.uk/rulings/tefincom-sa-a19-547668.html

我在https://tomscott.com
在Twitter上的https://twitter.com/tomscott
在Facebook上https://facebook.com/tomscott
在Instagram上為tomscottgo。

46 comments

  1. I'd like to thank all the team at ██████ VPN for ████████████. (The opening speech isn't about a real person, by the way; it was just the worst possible segue I could think of.)

  8. I now know that at least somebody apart from me knows that the VPN company, if they want/need to, can store your activity (the websites you're going to).

  24. Tom, I used to watch you all the time, but forgot to hit that subscribe button. Due to a medical condition that developed as a result of septic shock, I could not even remember your name. I have a foreign friend (who will likely see my face and know who I am 🙂 ) that brought you up a couple times and finally I remembered and subscribed. Anyways, all this is a bit off-topic, but I bring it up as an excuse for what I am about to say: THANK YOU for standing up to sketchy advertisers. The number of VPN providers throwing money around at YouTubers and other content providers has been driving me absolutely nuts because of exactly the reasons you mentioned. Sorry this comment is a bit late, but it is for reasons mentioned earlier. Honestly I've unsubscribed from any youtube channel that has an in video ad-roll for a VPN provider again if they make such audacious claims. I've watched a few that have even used Net Neutrality as a reason to use them, and this infuriates me further.

  29. VPN =
    Very unrealistic tool to use as a main
    Protection from the internet that isn't
    Needed since everything is almost secure
    Or VUTTUAAMPFTITINSEIAS for short

    Right?..

  34. 2:28 truth to be told, it could be avoided by using multiple VPN services. That way, the vpn that gets the traffic does not inherently knows who the client is, while the one that sends it to the client have no idea what is the Metadata of the content it is delivering. Almost like a degraded form of tor, really. Only that you are connected to actual dns server. Also, you can't really change the nodes, and the client has an encrypted connection to each and every one of the nodes. Maybe it actually isn't that similar to tor, after all

  35. 2:15 where I you, I would not use anything "military grade". Military grade usually means "an absolute nut level of password scaling used together with software & hardware from 10 years, in case you are somewhat lucky". Military things work because of the iron discipline of the people managing and using them, as well as the almost inherent ability to quickly cut of infected parts of the network and routine checks. They do not work because they are robust nor advanced.

  37. Do you want to use your personal laptop on your work WiFi during your lunch break but are paranoid about your work logging your metadata?

  38. As an IT guy with casual interest in cyber security these ads always bothered me, thank you for the informative video!

    However I have one point… I've seen multiple times that banks (especially national ones) tend to upgrade their security very slowly… They are probably more afraid of getting complaints from not-tech-savvy customers who still use IE6 about "why this doesn't work anymore? I'm losing $$$ by not being able to do X and Y…!". For this reason, I would still advise people who want to handle bank accounts with a lot of money from public wifi to use VPN. Or you know… just wait until you get home.

  43. An FYI for new-ish web service developers: Even though as shown in this video the URI (after the authority, and including the query string), is encrypted in SSL connections, it's still necessary to pay attention to what gets placed there. In IIS, for example, (assuming logging is enabled at all) the full URI is logged in plain text on the server. If you've implemented a web service that takes credit card numbers, for example, and it expects these numbers to be specified within a query string parameter, if that server is compromised, all of those numbers would be present in its logs. This isn't inherently obvious and it seems that it really shouldn't work this way, but that's my point: we don't know what we don't know. Independent security audits during the design phase and again for the ready-to-release code are highly advisable.

Comments are closed.