that officers from the United States Customs and Border Protection repeatedly pressured him to unlock his phone so that they could scroll through his contacts, photos, apps and social media accounts. https://www.nytimes.com/2017/02/14/business/border-enforcement-airport-phones.html 6
for a lawyer,” he said. “They just started attacking me verbally. ‘Why do you need a lawyer? Are you a criminal? What are you hiding?’ ” After allowing the Homeland Security officer to examine his phone, he said, he was immediately released. 7
at the United States border that a police officer on the street wouldn’t. Laws that allow agents to search bags without a judge’s approval, for the purposes of immigration or security compliance, have been extended to digital devices. 8 BORDERS
your entire hard drive before the trip 3. Encrypt entire data on hard drive 4. Change your login password and give the password to a friend. 5. Use a disposable computer for every trip? (like ChromeBook) 10
digital daily life 2. Change your internet usage habits 3. Follow security best practices for communication and data transfer 4. No personal social media accounts and applications 5. No browser plugins (Except maybe EFF plugins) 6. Use internet like you are always being recorded. 7. Do not trust online services. 11
wikileaks AES-256-gcm, AES-256-ctr or AES-256-cbc algorithms are strong enough to trust. It is one of the strongest algorithms. https://wikileaks.org/ciav7p1/cms/files/NOD%20Cryptographic%20Requirements%20 v1.1%20TOP%20SECRET.pdf 14
media applications ▪ Important keys and 2FA apps on a backup phone. ▪ Encrypted disk/card ▪ Auto lock ▪ Disable auto connect to unknown public Wifis ▪ Hide your screen 18
Do not connect them if possible ▪ Watch your back ▪ Do not use mechanical keyboards, I love them but easy to extract from sound. ▪ Not too bright screen 19
basis 2. Do not install or open unknown/suspicious files, websites (virustotal.com) 3. Do not plug in unknown physical devices. 4. Do not connect unknown WiFis 5. Do not believe everything in your inbox. 24
2. No public WiFi, No Third-party plugins 3. No personal data through social media, reduce social media usage 4. Disable JS by default (also CSS if possible) 5. HTTPS & End to end encryption communications 6. Do not share your data 25
your mobile device before the trip by 1. Using an encrypted cloud storage, store and use your files directly on the cloud. 2. Using online mail clients (E2E supported) 3. Creating disposable virtual environments in your OS 26
the network, using a directory server to get a list of active nodes. For each hop along that path, it negotiates a separate session key. It encrypts the packet data, along with a destination address, once per node in the path, building up a packet with multiple layers of encrypted information. https://lwn.net/Articles/249388 34
within the Tor network, but the encryption of your traffic to the final destination website depends upon on that website. ” More on https://www.eff.org/pages/tor-and-https 35
across all your devices and applications acts like you are a toilet brush fetish. You will see all kinds of toilet brushes and even maybe candies shaped like toilet brushes. Google does this with and agreement of the users. But we do not read. 40 DuckDuckGo
S/Mime is not broken by design. It’s how the messages are processed by the user’s email client that introduces the vulnerability. The many of the implementations are wrong. 44
combine public sources regarding when various PGP vendors were notified about Efail. Starting from 2017.10.25 with Thunderbird contact by Efail team. http://flaked.sockpuppet.org/2018/05/16/a-unified-timeline.html 46
like trying to blame GPG (but it was not like that). So the developers started to defend S/Mime or (G)PGP ▪ S/Mime by IEFT uses AES for encryption (symmetric encryption) ▪ PGP encryption uses a serial combination of hashing, data compression, symmetric-key cryptography, and public-key cryptography. PGP also supports asymmetric 47
to decrypt and encrypt messages using a separate application and disabling automatic decryption process in mail clients. Because of the complexity of integrating encryption softwares into mail clients, developers may follow some non-standard ways. 50
updated their softwares. But it is always good to disable HTML. It is still suggested not to use PGP just to create a clean ecosystem. “Sending PGP messages to others also increases the risk that your recipients will turn to a vulnerable client to decrypt these messages. Until enough clients are reliably patched, sending PGP-encrypted messages can create adverse ecosystem incentives for others to decrypt them.” https://www.eff.org/ 51