Take SSL/TLS. Are they going to demand both parties stash the session key, or do their handshaking through a proxy logging each packet?

Probably not. You're thinking like a geek instead of a politician. Politicians don't get their way by understanding technology. They get their way by finding people who do and forcing them to obey their will.

In this case, what Cameron means by banning encryption is passing laws that say something like, "If your website is used by people in the UK, you must always be able to comply with a warrant demanding data and you must provide all data, even if it is encrypted". The exact details of how that works is neither here nor there to them.

Now of course the interesting thing is how this interacts with jurisdictions, and whether it would be enough to make GCHQ shut up (probably not). The UK may or may not be able to force the hands of Facebook/Google/etc because the UK is such a huge market and they all have offices there, but China was a huge market too and Google walked away from that anyway. So it's hard to know how things would play out. For companies that have no UK exposure it's not clear what they'd do - probably use ad-hoc blocking of any website they suspect might be used by The Evil Terrorists if it doesn't comply. Could be a mess depending on how heavily they enforce it.

All those figures say is that birds of a feather flock together. Tory voters tend to live near each other and because the UK has a political system designed a long time ago for resolving local issues, not surprisingly it doesn't translate votes to seats directly at the national level. As local politics becomes less and less relevant, of course, people feel this system no longer works well for them.

However, as you note, it would not have mattered if Labour had won, or any other party. There are NO parties in the UK that believe people should be able to keep secrets from the government. It's just not something that fits into the political worldview. And because the voting system collapses thousands of decisions down to just one every so many years, surveillance and encryption is simply not democratically decided at all. Basically the wheel of power is decided by the economy, and that's about it.

Unfortunately this is not specific to the UK and is true nearly everywhere, France is even worse for example, and the USA pretends to care but realistically lots of Congressmen would very much like total surveillance of Americans .... and only feel they can't demand it openly because of that darned constitution. That won't stop them doing it in secret though!

Ha ha, did you think he meant warrants?

He meant warrant. Unfortunately as is often the case with the Tories, they use words differently to how ordinary people do. By warrant he means a ministerial rubber-stamp. For instance Theresa May last year alone "signed" nearly 2,800 warrants, a number that clearly shows zero attempt to investigate their legitimacy and indeed almost certainly means some anonymous flunky is signing them on her behalf.

I meant password, of course. Sorry, not fully awake.

Also, don't give your SSID to anyone who does or might in the future use Windows 10, or have a Windows phone.

+1

Not to be sexist, but most women prefer jobs that include more interaction with people and less time spent in solo problem solving, so it's not terribly surprising that she does't love coding. This isn't to say there aren't women who really like coding, or even introverted women who find working with people all day to be unpleasant. There are all kinds... but on average my observation is that women prefer more human interaction.

So, assuming that your wife falls into that category, there are lots of roles in and around software development that are more people-focused. Project management requires an additional set of skills, both people skills and management skills, but it's eminently learnable, and having a technical background is very valuable -- as long as it doesn't cause her to second-guess what the developers are telling her (always a risk with PMs, and even more with those whose technical background is shallower than they think it is. There's a tendency to assume that everything they don't know how to do is easy.)

Business Analyst is another good one. It, again, requires some additional skills she probably doesn't have but can learn. Industry knowledge tends to be important, but most companies are okay with analysts learning that context on the job. She also needs to learn how to gather and document requirements. A technical background is useful there because good requirements need quite a bit more precision than most non-technical people are used to. There's also a risk; formerly-technical BAs have a tendency to overspecify. An important skill for this role which isn't so easy to learn is writing. Good BAs are excellent writers, able to concisely and accurately boil complex issues down to simple statements.

Another option that might be excellent if she can swing it is Systems or Application Architect. Companies generally want experienced, senior developers to move into these roles, but smart but less-experienced people can do it as well. Architects take the business requirements and convert them into high-level technical plans/architectures. Architects tend to spend less time interacting with people than PMs or BAs, but still quite a bit since they provide the primary interface between the technical and business teams. Architects need to have good technical skills and good "taste", meaning a good feel for what sorts of structures are easy to build, easy to maintain and flexible, and for how to intelligently trade those issues off. They also need to be good at translating technical issues into language the business people can understand. Honestly I expect that your wife probably doesn't have the depth of experience needed to make a good architect, but I thought I'd throw it out.

Another that might be good if she's a good writer and enjoys writing is technical writing. Good tech writers have greater need for writing skill than they do technical skill, but the latter is very valuable because it enables them to more quickly and accurately understand the information that needs to be documented.

In smaller companies a lot of these roles get mixed and combined with other business roles, so another good option is to look for a position that isn't necessarily directly related to software development, but could benefit from having a deeply IT-literate person.

Finally, the option that I've long thought I'd take if I ever got tired of writing code is the law. It's a lot of additional training, but I think there is a deep and growing need for attorneys who understand technology. This is especially true in the areas of patent and copyright law, but I think it applies in many areas. Of course, the law may not have any attraction whatsoever for your wife.

Whatever, I'd really encourage her to take the time to figure out what she wants to do, and do that, rather than settling for something she doesn't really like. We so much of our lives working that it's really a waste to spend it doing something we don't like.

This is completely untrue. The electorate is pretty divided, and whether you can find a majority depends which poll you look at, and which week. The fact is that there is a significant part of the electorate that thinks bulk surveillance is fine because they have nothing to hide and it keeps us safe. That they're wrong on both counts doesn't change their opinion, or their votes

And yet they passed the USA Freedom Act which, although better than the PATRIOT Act, still authorizes way too much surveillance. And in the process they failed to do anything to curtail article 702 of the FISA, which is the basis for the FISA court's ruling -- as was completely predictable before passage of USA Freedom. The argument is that while article 702 authorizes only surveillance of foreign people, the court considers it perfectly reasonable for the NSA to hoover up ALL the data and then figure out later what they can and cannot look at. This all comes back to the NSA's choice to define "collect" as "look at", since the law hadn't defined the term.

Congress had a perfect opportunity to define "collect" as "collect", and chose not to.

The problem is fundamentally the electorate, which isn't sufficiently convinced that bulk data collection is a bad thing. If 80% of the voters wanted it shut down, enough to make it a major election issue, it would be shut down. But as is Congress knows that with a slim majority (at best) concerned about data collection, if they shut it down and then Something Bad happened the voters would turn on them like a rabid dog.

The system isn't perfect, but it is basically working as intended. We just need to convince more of our fellow Americans that surveillance is bad.

No, but this particular comparison is. Besides all of the stuff s2n doesn't provide, s2n actually uses OpenSSL's libcrypto to provide the implementations of all of its crypto algorithm. A useful comparison could be made between OpenSSL's TLS layer and s2n, with some caveats listing the TLS features s2n doesn't provide.

Note that none of this means that s2n doesn't have value. If you don't need the other OpenSSL features, it's a lot less code to audit.

So you don't have a good reason.

The question is not corporate adoption but developer adoption. Airplanes have a very low adoption percentage among all people who use automated transportation but a high adoption rate among pilots.

touch response, camera, display quality, battery life per mAh, 64 bit- CPU

I currently have a web radio transceiver front panel application that works on Linux, Windows, MacOS, Android, Amazon Kindle Fire, under Chrome, Firefox, or Opera. No porting, no software installation. See blog.algoram.com for details of what I'm writing.

The one unsupported popular platform? iOS, because Safari doesn't have the function used to acquire the microphone in the web audio API (and perhaps doesn't have other parts of that API), and Apple insists on handicapping other browsers by forcing them to use Apple's rendering engine.

I don't have any answer other than "don't buy iOS until they fix it".