Podchaser Logo
Home
The Mind Tech Podcast: Episode 25 - Shit Kat

The Mind Tech Podcast: Episode 25 - Shit Kat

Released Thursday, 12th September 2013
Good episode? Give it some love!
The Mind Tech Podcast: Episode 25 - Shit Kat

The Mind Tech Podcast: Episode 25 - Shit Kat

The Mind Tech Podcast: Episode 25 - Shit Kat

The Mind Tech Podcast: Episode 25 - Shit Kat

Thursday, 12th September 2013
Good episode? Give it some love!
Rate Episode

Shit Kat

Hosted by Gareth Davies and Joe Ressington

The Mind Tech Podcast is your weekly dose of tech, privacy, security and conspiracy.

Each week we'll talk about the very latest tech news and the continued threats to internet freedom.

Joe's Nexus 7 Home Screen

Pogoplug

Mind Tech News:

New Apple Stuff

Android KitKat

Some reasons why Google should not be in bed with Nestlé

Linux Security, In Light of NSA Crypto-Subverting Attacks?

UK gov't wants to ban dirty words in UK domain names; tell them to #£@* off

NSA surveillance: A guide to staying secure

1) Hide in the network. Implement hidden services. Use Tor to anonymize yourself. Yes, the NSA targets Tor users, but it's work for them. The less obvious you are, the safer you are.

2) Encrypt your communications. Use TLS. Use IPsec. Again, while it's true that the NSA targets encrypted connections – and it may have explicit exploits against these protocols – you're much better protected than if you communicate in the clear.

3) Assume that while your computer can be compromised, it would take work and risk on the part of the NSA – so it probably isn't. If you have something really important, use an air gap. Since I started working with the Snowden documents, I bought a new computer that has never been connected to the internet. If I want to transfer a file, I encrypt the file on the secure computer and walk it over to my internet computer, using a USB stick. To decrypt something, I reverse the process. This might not be bulletproof, but it's pretty good.

4) Be suspicious of commercial encryption software, especially from large vendors. My guess is that most encryption products from large US companies have NSA-friendly back doors, and many foreign ones probably do as well. It's prudent to assume that foreign products also have foreign-installed backdoors. Closed-source software is easier for the NSA to backdoor than open-source software. Systems relying on master secrets are vulnerable to the NSA, through either legal or more clandestine means.

5) Try to use public-domain encryption that has to be compatible with other implementations. For example, it's harder for the NSA to backdoor TLS than BitLocker, because any vendor's TLS has to be compatible with every other vendor's TLS, while BitLocker only has to be compatible with itself, giving the NSA a lot more freedom to make changes. And because BitLocker is proprietary, it's far less likely those changes will be discovered. Prefer symmetric cryptography over public-key cryptography. Prefer conventional discrete-log-based systems over elliptic-curve systems; the latter have constants that the NSA influences when they can.

Until Next Week...

Contact us via Bitmessage!  Here's our address:

BM-2D827QEqWztqKZaRW4xkL8z7WPGu3qryyM

The Mind Set Facebook group

The Mind Set Google+ group

Support Mind Set Central

Suscribe or donate

Show More
Rate

Join Podchaser to...

  • Rate podcasts and episodes
  • Follow podcasts and creators
  • Create podcast and episode lists
  • & much more

Episode Tags

Do you host or manage this podcast?
Claim and edit this page to your liking.
,

Unlock more with Podchaser Pro

  • Audience Insights
  • Contact Information
  • Demographics
  • Charts
  • Sponsor History
  • and More!
Pro Features