Please stop playing in my face because you purposely know you blocked me and locked up my so personal accounts from this website! Just like you didn't come across abandoned websites. Why would you want to pull it off by illegally claiming my domain's privately owned URL? But it's why my Gmail account is locked up, and I'm requesting that you stop abusing my accounts before I have to act the property legal avenues. Please stop stealing my data on something that you know wasn't abandoned property. Nothing should ever be misused or falsely considered as free access to steal from others. You knew that it wasn't free assets just laying around the internet for anybody to share in the EU for business US, American-based products. Just unsubscribe you're closer than me!
On Sun, May 4, 2025, 3:45 AM <oauth-requ...@ietf.org> wrote: > Send OAuth mailing list submissions to > oauth@ietf.org > > To subscribe or unsubscribe via email, send a message with subject or > body 'help' to > oauth-requ...@ietf.org > > You can reach the person managing the list at > oauth-ow...@ietf.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of OAuth digest..." > > Today's Topics: > > 1. Re: ABNF error in draft-ietf-oauth-selective-disclosure-jwt-18 ? > (Brian Campbell) > 2. Weekly github digest (OAuth Activity Summary) > (Repository Activity Summary Bot) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 3 May 2025 07:55:16 -0600 > From: Brian Campbell <bcampb...@pingidentity.com> > Subject: [OAUTH-WG] Re: ABNF error in > draft-ietf-oauth-selective-disclosure-jwt-18 ? > To: Carsten Bormann <c...@tzi.org> > Cc: dick.ha...@gmail.com, oauth@ietf.org > Message-ID: > <CA+k3eCT8wKcbpopfih+uQnRbUpa9ag16j8= > bbbxbw4q5-jm...@mail.gmail.com> > Content-Type: multipart/alternative; > boundary="00000000000072ea4d06343b9f59" > > Thanks Carsten for pointing that out. I've created issue 570 > <https://github.com/oauth-wg/oauth-selective-disclosure-jwt/issues/570> to > track this and, with the support of a different tool, tried to document why > the use of () is equivalent to but also more correct than []. > > In my own defense, I was somewhat reluctant to add ABNF at all. But some > folks do find it useful. So, with the support of the ietf author tool for > abnf, I was able to transmute the provided suggestion that was > syntactically invalid and semantically incorrect into the content that's in > the draft now (some of that saga was documented in issue 393) > <https://github.com/oauth-wg/oauth-selective-disclosure-jwt/issues/393>. > And if that made you smile, I will celebrate. > > > > On Fri, May 2, 2025 at 11:29 PM Carsten Bormann <c...@tzi.org> wrote: > > > > SD-JWT = JWT "~" *[DISCLOSURE "~"] > > > > made me smile... > > I.e., Zero or more of [DISCLOSURE “~”], each of which is optional (can be > > empty) due to the [] > > > > (Simple-minded ABNF validators tend to loop on something like this.) > > > > Anyway, I’m writing this to point out that languages such as ABNF should > > never be used without tool support. > > > > Here, abnfgen [1][2] would be my tool of choice. > > > > Or, if that is too difficult to install, you can embed the ABNF in CDDL > > and use a CDDL tool [3]: > > > > foo = text .abnf 'SD-JWT-KB > > ALPHA = %x41-5A / %x61-7A ; A-Z / a-z > > DIGIT = %x30-39 ; 0-9 > > BASE64URL = 1*(ALPHA / DIGIT / "-" / "_") > > JWT = BASE64URL "." BASE64URL "." BASE64URL > > DISCLOSURE = BASE64URL > > SD-JWT = JWT "~" *(DISCLOSURE "~") > > KB-JWT = JWT > > SD-JWT-KB = SD-JWT KB-JWT > > ' > > > > (Fixed the [] in the above.) > > > > $ cddl sd-jwt.cddl generate 10 > > > > …yields a bunch of EDN (JSON) text strings: > > > > "_0_.-._J~P.O._J_" > > "z_-_._i58.5a5_~_7.L.9-8_" > > "-_2n.-d0.42~__._ueM.z3" > > "yTw.--89.0l--~-_2.Y._8Y" > > "9.-.-~__.7-_._" > > "-.-5h1.-0R~B~K-7~-4.i5-_.42-" > > "-__.-4.6_~bO~y~--9.0d-8.-U" > > "-.4i-.3~_~5.--.3_" > > "0.-k4.1H~-se6~-~_1.H-4_.q" > > "3.-V.68-~-p5_.1U6_.Dl" > > "-q2.-4AY.XY29~e-c8.-.-C" > > "__.2--.--1~Y_c~_7V~9~-.Hxo.w" > > > > … with tilde characters clearly in view (even more clearly in [4]). > > > > Grüße, Carsten > > > > [1]: https://www.quut.com/abnfgen/ > > [2]: https://www.quut.com/abnfgen/abnfgen.1.html > > (`brew install abnfgen` for those who have homebrew) > > [3]: https://www.rfc-editor.org/rfc/rfc8610#appendix-F > > > > [4]: _______________________________________________ > > OAuth mailing list -- oauth@ietf.org > > To unsubscribe send an email to oauth-le...@ietf.org > > > > -- > _CONFIDENTIALITY NOTICE: This email may contain confidential and > privileged > material for the sole use of the intended recipient(s). Any review, use, > distribution or disclosure by others is strictly prohibited. If you have > received this communication in error, please notify the sender immediately > by e-mail and delete the message and any file attachments from your > computer. Thank you._ > -------------- next part -------------- > A message part incompatible with plain text digests has been removed ... > Name: not available > Type: text/html > Size: 4631 bytes > Desc: not available > > ------------------------------ > > Message: 2 > Date: Sun, 4 May 2025 00:39:50 -0700 (PDT) > From: Repository Activity Summary Bot <do_not_re...@mnot.net> > Subject: [OAUTH-WG] Weekly github digest (OAuth Activity Summary) > To: oauth@ietf.org > Message-ID: <20250504073950.19d4b2483...@mail2.ietf.org> > Content-Type: multipart/alternative; > boundary="===============7775725007161556741==" > > > > > Events without label "editorial" > > Issues > ------ > * oauth-wg/oauth-identity-chaining (+0/-1/💬0) > 1 issues closed: > - Security Considerations > https://github.com/oauth-wg/oauth-identity-chaining/issues/131 > > * oauth-wg/oauth-transaction-tokens (+0/-0/💬1) > 1 issues received 1 new comments: > - #164 Expanding scope of permitted actions (1 by PieterKas) > https://github.com/oauth-wg/oauth-transaction-tokens/issues/164 > > * oauth-wg/oauth-sd-jwt-vc (+1/-1/💬9) > 1 issues created: > - Update intro text to PID example (by danielfett) > https://github.com/oauth-wg/oauth-sd-jwt-vc/issues/309 > > 1 issues received 9 new comments: > - #307 cnf, x5c, or other public key certificates (9 by alenhorvat, > bc-pi, danielfett) > https://github.com/oauth-wg/oauth-sd-jwt-vc/issues/307 > > 1 issues closed: > - cnf, x5c, or other public key certificates > https://github.com/oauth-wg/oauth-sd-jwt-vc/issues/307 > > * oauth-wg/oauth-cross-device-security (+0/-0/💬2) > 2 issues received 2 new comments: > - #153 Shepherd Feedback: Normative References (1 by PieterKas) > https://github.com/oauth-wg/oauth-cross-device-security/issues/153 > - #152 Shepherd Write-up: Add reference to FIDO/WebAuthn (1 by PieterKas) > https://github.com/oauth-wg/oauth-cross-device-security/issues/152 > > * oauth-wg/oauth-selective-disclosure-jwt (+2/-14/💬4) > 2 issues created: > - evalutate for misleading language around encoding (by bc-pi) > https://github.com/oauth-wg/oauth-selective-disclosure-jwt/issues/571 > - celbrations must conform to protocol (by bc-pi) > https://github.com/oauth-wg/oauth-selective-disclosure-jwt/issues/570 > > 2 issues received 4 new comments: > - #571 evalutate for misleading language around encoding (1 by bc-pi) > https://github.com/oauth-wg/oauth-selective-disclosure-jwt/issues/571 > - #570 celebrations of ABNF must conform to protocol (3 by bc-pi) > https://github.com/oauth-wg/oauth-selective-disclosure-jwt/issues/570 > [has-PR] > > 14 issues closed: > - Add the wording "one-time use digital credentials" in the context of > "batches of credentials". > https://github.com/oauth-wg/oauth-selective-disclosure-jwt/issues/562 > [help wanted] [pending-close] > - Proposed rewording in Section 1.1 about SD-JWT+KB > https://github.com/oauth-wg/oauth-selective-disclosure-jwt/issues/561 > [help wanted] [pending-close] > - The definition of an Issuer would need to be polished > https://github.com/oauth-wg/oauth-selective-disclosure-jwt/issues/560 > [help wanted] [pending-close] > - Figure 1 should illustrate the involvement of an End-User and be > closer to the data structures that are exchanged > https://github.com/oauth-wg/oauth-selective-disclosure-jwt/issues/559 > [help wanted] [pending-close] > - Proposed rewording in Section 1.2 for the term Holder > https://github.com/oauth-wg/oauth-selective-disclosure-jwt/issues/558 > [help wanted] [pending-close] > - In Section 1.2, the term End-User should be defined as it is a > fundamental entity in ISO 29100 > https://github.com/oauth-wg/oauth-selective-disclosure-jwt/issues/557 > [help wanted] [pending-close] > - Editorial change. In section 10.3, both confidentiality and integrity > during Transport are essential > https://github.com/oauth-wg/oauth-selective-disclosure-jwt/issues/551 > [help wanted] [pending-close] > - Editorial. In draft -14, ISO 29100 was mentioned in section 10 but > has been removed in draft -15 > https://github.com/oauth-wg/oauth-selective-disclosure-jwt/issues/550 > [help wanted] [pending-close] > - Editorial: About the none algorithm in section 4.1 > https://github.com/oauth-wg/oauth-selective-disclosure-jwt/issues/549 > [help wanted] [pending-close] > - About KB-JWT replay detection in section 7.3 (Verification by the > Verifier) > https://github.com/oauth-wg/oauth-selective-disclosure-jwt/issues/548 > [help wanted] [pending-close] > - About KB-JWT replay detection in section 4.3 > https://github.com/oauth-wg/oauth-selective-disclosure-jwt/issues/547 > [help wanted] [pending-close] > - Checking SD-JWT suspension or revocation is missing in section 7.1 > (Verification of the SD-JWT) > https://github.com/oauth-wg/oauth-selective-disclosure-jwt/issues/546 > [help wanted] [pending-close] > - the phrase "non-selectively disclosable claims" is confusing > https://github.com/oauth-wg/oauth-selective-disclosure-jwt/issues/563 > [has-PR] > - [KB-JWT] exp recommended? > https://github.com/oauth-wg/oauth-selective-disclosure-jwt/issues/545 > [has-PR] > > * oauth-wg/oauth-v2-1 (+1/-0/💬5) > 1 issues created: > - Refresh Tokens (by PieterKas) > https://github.com/oauth-wg/oauth-v2-1/issues/211 > > 1 issues received 5 new comments: > - #210 Add definitions for client_secret_basic, client_secret_post and > none client authentication methods (5 by ThisIsMissEm, dickhardt) > https://github.com/oauth-wg/oauth-v2-1/issues/210 > > > > Pull requests > ------------- > * oauth-wg/oauth-identity-chaining (+3/-1/💬0) > 3 pull requests submitted: > - Kelley/privacy considerations (by kburgin3) > https://github.com/oauth-wg/oauth-identity-chaining/pull/152 > - Add refresh token consideration (by arndt-s) > https://github.com/oauth-wg/oauth-identity-chaining/pull/151 > - Security Considerations for Authorization Grants (by PieterKas) > https://github.com/oauth-wg/oauth-identity-chaining/pull/150 > > 1 pull requests merged: > - Security Considerations for Authorization Grants > https://github.com/oauth-wg/oauth-identity-chaining/pull/150 > > * oauth-wg/oauth-transaction-tokens (+2/-1/💬1) > 2 pull requests submitted: > - Strengthen prohibition on expanding scope (by PieterKas) > https://github.com/oauth-wg/oauth-transaction-tokens/pull/173 > - Transaction tokens are not authentication creds (by PieterKas) > https://github.com/oauth-wg/oauth-transaction-tokens/pull/172 > > 1 pull requests received 1 new comments: > - #173 Strengthen prohibition on expanding scope (1 by tulshi) > https://github.com/oauth-wg/oauth-transaction-tokens/pull/173 > > 1 pull requests merged: > - Transaction tokens are not authentication creds > https://github.com/oauth-wg/oauth-transaction-tokens/pull/172 > > * oauth-wg/oauth-sd-jwt-vc (+0/-0/💬1) > 1 pull requests received 1 new comments: > - #306 Update PID example (1 by bc-pi) > https://github.com/oauth-wg/oauth-sd-jwt-vc/pull/306 > > * oauth-wg/oauth-cross-device-security (+2/-0/💬0) > 2 pull requests submitted: > - Update references for FIDO2/WebAuthn (by timcappalli) > https://github.com/oauth-wg/oauth-cross-device-security/pull/155 > - Shepherd Feedback - Added Definition of Authenticated Channel (by > PieterKas) > https://github.com/oauth-wg/oauth-cross-device-security/pull/154 > > * oauth-wg/oauth-selective-disclosure-jwt (+3/-3/💬0) > 3 pull requests submitted: > - Update the ABNF to be cleaner, less ambiguous, and more idiomatic (by > bc-pi) > https://github.com/oauth-wg/oauth-selective-disclosure-jwt/pull/572 > - updates from AD's review of comments (by bc-pi) > https://github.com/oauth-wg/oauth-selective-disclosure-jwt/pull/569 > - to -19 (by bc-pi) > https://github.com/oauth-wg/oauth-selective-disclosure-jwt/pull/568 > > 3 pull requests merged: > - to -19 > https://github.com/oauth-wg/oauth-selective-disclosure-jwt/pull/568 > - Terminology improvements around the phrase "non-selectively > disclosable claims" and "not disclosable" > https://github.com/oauth-wg/oauth-selective-disclosure-jwt/pull/567 > - Suggest against using extra claims/headers in the KB-JWT without a > good reason > https://github.com/oauth-wg/oauth-selective-disclosure-jwt/pull/566 > > > Repositories tracked by this digest: > ----------------------------------- > * https://github.com/oauth-wg/oauth-browser-based-apps > * https://github.com/oauth-wg/oauth-identity-chaining > * https://github.com/oauth-wg/oauth-transaction-tokens > * https://github.com/oauth-wg/oauth-sd-jwt-vc > * https://github.com/oauth-wg/draft-ietf-oauth-resource-metadata > * https://github.com/oauth-wg/oauth-cross-device-security > * https://github.com/oauth-wg/oauth-selective-disclosure-jwt > * https://github.com/oauth-wg/oauth-v2-1 > * https://github.com/oauth-wg/draft-ietf-oauth-status-list > * > https://github.com/oauth-wg/draft-ietf-oauth-attestation-based-client-auth > > > -- > To have a summary like this sent to your list, see: > https://github.com/ietf-github-services/activity-summary > -------------- next part -------------- > A message part incompatible with plain text digests has been removed ... > Name: not available > Type: text/html > Size: 13809 bytes > Desc: not available > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > OAuth mailing list -- oauth@ietf.org > To unsubscribe send an email to oauth-le...@ietf.org > > > ------------------------------ > > End of OAuth Digest, Vol 199, Issue 9 > ************************************* >
_______________________________________________ OAuth mailing list -- oauth@ietf.org To unsubscribe send an email to oauth-le...@ietf.org
