langley

The article has a link to Adam Langley suggesting this for some uses of signatures in TLS.

In the US you have Samuel Pierpont Langley and the Pennsylvania Railroad to thank for the modern time zone system.

For example - Langley to UBC is the same distance as Hamilton to Toronto.

The Wrights also had a propeller design that was 90% efficient, compared with the flat design (used on the Langley machine) that was 50% efficient.

There has always been the intention to make light rail through Surrey and Langley and the plan has always been to improve the bike lanes and roads.

Well if you follow the second link you will find Adam Langley (one of the initial developers of Go) saying that the type system precludes a generic map, grep, etc.

You can't see the code inside Google's network so even though the client app is open you have no more proof that all your calls aren't being streamed to Langley or Beijing than you do with skype.

The only arguable chink in the ctgrind armor is integer division, which I don't know whether Adam Langley remembered to count as having an execution time that possibly depends on the value of its arguments—as pointed out in another thread).

(As well as having a bucket of JS restrictions (no eval() can be used, apparently ever) Adam Langley said something about enforcing secure TLD restrictions in Chrome a while ago, not sure if that ever got done.

> attempting to make them part of the official Go build for the good of the community Would be interesting to hear what Adam Langley thinks about this, but I couldn't find anything recent on the golang-dev list.

If I'm understanding this right, this article is claiming that the CIA served up [edit: could serve up, not proven they did, see comments below about plausibility] poisoned versions of XCode, which would then be used to make App Store apps that eventually phoned home to Langley with either app-specific data or whole-phone data.

Many people believe that SSL/TLS takes a lot of CPU time and we hope the preceding numbers will help to dispel that." - Adam Langley, Google.

That assumption failed when Google moved to BoringSSL, Adam Langley's rewrite to improve security.

The F-22 is currently deployed 4 AFB's, Langley(Virginia, basically covering DC), Elmendorf(Alaska), Hickam(Hawaii) and Holloman(New Mexico).

This issue was reported to OpenSSL by Adam Langley/David Benjamin (Google/BoringSSL).