blueskin_

I liked proper expansions where you got a good proportion of a whole game's extra content. I hate DLC where you are encouraged to buy large numbers of small items, because it's a 'death by a thousand cuts' model of sucking way more money out of the player with far less dev effort.

I never buy DLC for any game, on principle. If a game has a lot, I'll reconsider buying the game at all.

The whole standard it a mess; it should have opportunistic encryption on open networks, then clients can display a warning if this doesn't happen for whatever reason ("Anything you send or receive over this network may be readable by others" or similar).

>spoof ssl

Only if either they blindly accept invalid certs, or you somehow already installed a root CA on their boxen.

Sounds to me like you found an all-in-one tool, which doesn't make you understand how the process works or its limitations. I would agree that many wireless networks are hideously insecure (why I SSH tunnel my traffic when I'm on one), but it isn't that bad unless you're either running unauthenticated or using WEP.

The main drawback is that it doesn't work on Windows (wpa_supplicant on Linux already does this by default); on my laptops I just remove all networks when I am finished with them - entering a 15-20 char password every couple of months isn't so bad, especially as I only really use my laptop when travelling.

This always comes in a cycle.

The solution is to use Pry-fi: https://play.google.com/store/apps/details?id=eu.chainfire.p... . It also has a nice feature where it randomly cycles your MAC address quickly to ruin datasets of places who spy on wireless probes to track people's locations.

That's the messed up part. I guess the question is, does robots.txt override that or not? If it does, fine. If not, all you need to do is make a few "google ignores robots.txt" posts and the problem solves itself.

Well, it depends on the feature set you need, but to a level that most people might consider fact.

From memory, no support for TLS connections, SMTP AUTH, or SPF/DKIM on mail. That, plus it has very limited support in general and needs an arcane collection of patches to remain workable.

Other mail servers can work around its restrictions, yes, but that doesn't make it fit for purpose.

I'd probably use CentOS 6 (avoiding systemd) with full disk encryption, and either a RAID10 of some good-performing normal disks, or RAID1 of SSDs.

I'd put a backup MX on a VPS somewhere, preferably in a different location to act as a store-and-forward to my main MX. This one will need to have a copy of the user map to avoid the "accept any" backscatter problem backup MXes have.

Postfix as the mail server; Dovecot for IMAP. Make sure it uses Maildir for storage (unless you're going SQL) as mbox is a horrible format that needs to die. Use SpamAssassin, and reject any mail from IPs listed on Spamhaus.

Truthfully though, I use a server in a datacentre for a reason - because home connections just aren't reliable enough and the ISPs can't be trusted (I can make sure I only send mail over TLS, but not that other people will only send their inbound mail into my server over TLS), and I wouldn't trust a consumer ISP not to suddenly try some kind of fuckery like blocking SMTP ports. Linode would get my recommendation, they are great value, have good performance for a cheapish VPS, and great uptime.

Anyone who cares about privacy? :)

Qmail is too old to be usable these days, but Postfix does at least use its security model. It isn't perfect, but arguably the best mail server around for that reason.

Why not just follow the rest of the world and actually implement Chip and PIN instead? All the security benefits with none of the privacy drawbacks.

>anonymous

Very funny.

"Sure it's anonymous, just trust us..."

Pry-fi (randomise MAC address when probing for wireless networks), Titanium Backup (backup that doesn't suck), most advanced network tools, changing FDE password to be different to lock screen password, running an sshd, detecting IMSI catchers, most performance fixes/optimisations, even just basic full filesystem access - all need root too.

It filters permission requests so when an app tries to use one, it gives you a popup with allow/deny temporarily/permanently options, so if an app wants to access something it shouldn't (location, contacts, device ID, etc.), you can feed it empty/fake data transparently to it.

Yay security by obscurity.

Use XPrivacy. It should be mandatory for anyone who uses a phone and has a clue about privacy.

The everything-as-a-website concept is fatally flawed anyway, as while it is often possible to find a single-purpose site to do a specific thing such as converting file formats, you're completely at the mercy of an unknown third party and their privacy policy (as well as promise not to tamper with your file) if you do. It's a privacy disaster waiting to happen. That, and javascript is a horrible and inefficient language not fit for purpose even years ago, so certainly not on devices with weak CPUs and limited battery.

Very interesting analysis.