by julian37 on 6/29/19, 5:56 AM with 137 comments
by motohagiography on 6/29/19, 12:56 PM
I could see someone making the choice where they would elect not to manage a nonce because its permuting effect was achieved by other parts of the protocol. Apple also has keys in a TEE, and a nonce generated and synchronized outside of that could have been interpreted as creating additional attack surface.
If the OpenID letter is correct, there are exploitable vulnerabilities in Apples implementation that could be demonstrated. If they are not correct, they could just be angry Apple is leveraging its TEE to assert it doesn't need governance from this standards body because the standard is written for products without a separate hardware keystore.
by blue_devil on 6/29/19, 9:07 AM
Also
>Are there live production deployments of OpenID Connect? Yes. Some examples include Google, Gakunin (Japanese Universities Network), Microsoft, Ping Identity, Nikkei Newspaper, Tokyu Corporation, mixi, Yahoo! Japan and Softbank. There are also mature deployments underway by Working Group participant organizations, such as Deutsche Telecom, AOL, and Salesforce.
For an example of OpenID Connect at work, look at Google+ Sign-In, Google’s flagship social-identity offering, which is entirely based on OpenID Connect.
by toyg on 6/29/19, 8:59 AM
Some sort of accompanying commentary from OIDF people, explaining the reasoning behind the letter, would be appreciated.
by jchw on 6/29/19, 12:15 PM
by slics on 6/29/19, 2:03 PM
by frenchman99 on 6/29/19, 8:41 AM
Is it currently not possible to use standard OpenID clients for "Sign-in with Apple" authentication ? Does Apple not provide some sort of SDK that makes this easy ? And if so, what is the advantage of "Sign-in with Apple" being interoperable ?
by nereid on 6/29/19, 9:37 AM
by ForHackernews on 6/29/19, 9:59 AM
by jjtheblunt on 6/29/19, 9:01 PM
Quoting wikipedia for convenience:
"OAuth 2.0 has had numerous security flaws exposed in implementations.[17] The protocol itself has been described as inherently insecure by security experts and a primary contributor to the specification stated that implementation mistakes are almost inevitable.[18][19]".
by huffmsa on 6/29/19, 12:27 PM
> Oh, you've all agreed on USB type-c? Well we're going to use thunderbolt. Except for when we don't and our customer have to buy a type-c to thunderbolt adapter.
> Two button mouse with a scroll wheel? How about a 1 button mouse that you click with two fingers.
> Linux? Sure, but it's called MacOsx and doesn't have a native package manager.
They've always done stuff like this.
by pyman on 6/30/19, 10:10 AM
by MaxBarraclough on 6/30/19, 10:19 PM
'Not Invented Here syndrome'.
by alt_f4 on 6/29/19, 11:45 AM
by Sephr on 6/29/19, 8:55 AM
It's not really an "invitation" if they expect Apple to give them money.
by marmada on 6/29/19, 2:09 PM