Group items tagged

"new computer school in Paris has been overwhelmed by some 60,000 applicants. The school, called 42, was founded by a telecom magnate who says the French education system is failing young people. His aim is to reduce France's shortage in computer programmers while giving those who've fallen by the wayside a new chance. In the hallways of 42, suitcases and sleeping bags are piled, and people are stretched out on mattresses in some of the corners. There are showers and dozens of colorful bath towels. Living here for the next month are some of the 4,000 potential students who already made the first cut by passing cognitive skill tests online. Now they have to clear another hurdle. They're thrown together and challenged with computer problems for 15 hours a day. Only 800 students will get a place, says 42′s director, Nicolas Sadirac."

" Base64url encode the octets of the UTF-8 representation of the JWS Protected Header to create the Encoded JWS Header. If the JWS Protected Header is not present (which can only happen when using the JWS JSON Serialization and no protected member is present), let the Encoded JWS Header be the empty string. Compute the JWS Signature in the manner defined for the particular algorithm being used over the JWS Signing Input (the concatenation of the Encoded JWS Header, a period ('.') character, and the Encoded JWS Payload). The alg (algorithm) header parameter MUST be present in the JWS Header, with the algorithm value accurately representing the algorithm used to construct the JWS Signature. Base64url encode the representation of the JWS Signature to create the Encoded JWS Signature. The three encoded parts are result values used in both the JWS Compact Serialization and the JWS JSON Serialization representations. If the JWS JSON Serialization is being used, repeat this process for each digital signature or MAC value being applied. Create the desired serialized output. The JWS Compact Serialization of this result is the concatenation of the Encoded JWS Header, the Encoded JWS Payload, and the Encoded JWS Signature in that order, with the three strings being separated by two period ('.') characters. The JWS JSON Serialization is described in Section 7.2. TOC 5.2. Message Signature or MAC Validation When validating a JWS, the following steps MUST be taken. The order of the steps is not significant in cases where there are no dependencies between the inputs and outputs of the steps. If any of the listed steps fails, then the signature or MAC cannot be validated. It is an application decision which signatures, MACs, or plaintext values must successfully validate for the JWS to be accepted. In some cases, all must successfully validate or the JWS will be rejected. In other cases, only a specific signature, MAC, or plaintext value needs to be s