Re: [OAUTH-WG] OAuth services/libraries wanted for security evaluation...

Dominick Baier <dbaier@leastprivilege.com> Thu, 25 June 2020 10:28 UTC

Return-Path: <dbaier@leastprivilege.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 247CE3A0909 for <oauth@ietfa.amsl.com>; Thu, 25 Jun 2020 03:28:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=leastprivilege-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kql7fbjjKlkx for <oauth@ietfa.amsl.com>; Thu, 25 Jun 2020 03:28:07 -0700 (PDT)
Received: from mail-il1-x12a.google.com (mail-il1-x12a.google.com [IPv6:2607:f8b0:4864:20::12a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 495983A0893 for <oauth@ietf.org>; Thu, 25 Jun 2020 03:28:07 -0700 (PDT)
Received: by mail-il1-x12a.google.com with SMTP id k1so3671747ils.2 for <oauth@ietf.org>; Thu, 25 Jun 2020 03:28:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leastprivilege-com.20150623.gappssmtp.com; s=20150623; h=from:in-reply-to:references:mime-version:date:message-id:subject:to; bh=NZ5Uz2faVblxGn+SsxS8YEq6TsKIB4E9uD97fpQLOus=; b=uHqbtG103oPq75pjbA+SGTd66mYEqH0IIHPG7LXUxXE6FGR79szeSOFcRlKJEhxew6 An4p8I0NPrZQZvsFvnWaJB/k9ys8XcT4flsEdyU2swAnDtkt/2aZQwckOfOrE1ugq5Gn vQZtoQfC/PUaGdaWgmIuqkArb2xDPOEGBTpTXUMPiKyr58xdGvtTM/ww5zMfQdiOBtau 874DoBVmoCdNqufRugKqcga4IQ8vuEi1ziW1Ok5SJb3oDbne/im2ZpSjxbG4591+eiid ZgV55W7O+MfWT67QmhhyemCurh4F/tKCeEDLmydhbI59w4Yga3dZlTcfYHiz4fbrUe0L SMPw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to; bh=NZ5Uz2faVblxGn+SsxS8YEq6TsKIB4E9uD97fpQLOus=; b=XJfO6NlAxwcfur9xKlBKeS/1ZM2tWtJuFUlWltVrANB9XGdYUVXsYvw4JotzaxZrCn OSILGQs9TRENn8STUTxIllLVgyo+Eba/rpDe9voi/4WQpU84G0dimb9/4mGy0OdwrO9s hpiE/kjgfd5DmmZFpZ+Dj8WWER3bW8dgCsMahtACKzCdLHzdRzE1sbBnC9cBLy585xS+ HM2A4Q6S8U/F4tTaBan3hmNueNTbb16/7Spt8eQfUzKa3qh26WY0ENuOPDjcrgJ48B6P 6Ubn0GLSWcxcbTipirTRRqnbD58iATOdWRvLFvMSK1TLYUJTXm2qoA22lItaO9eGJK6W 3tvQ==
X-Gm-Message-State: AOAM532DeUAu81mLRqL80L34ivW6V6X3DJTpbl/X4Lg+rwk1+rbrfNHx 26IWNpYepq469D+9AemNAH/iHsFcL+qjUdOP6ZIYieA=
X-Google-Smtp-Source: ABdhPJx2CBSkHJ3PEH4zB07HTsXXzPqAX7RWSZL5MUi45goZFLGPrTBjwjfd8JTTe7YcLTHgfaI9SUumF4vZ/HiSWRw=
X-Received: by 2002:a92:da46:: with SMTP id p6mr15752849ilq.48.1593080885891; Thu, 25 Jun 2020 03:28:05 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Thu, 25 Jun 2020 03:28:05 -0700
From: Dominick Baier <dbaier@leastprivilege.com>
In-Reply-To: <CADMp+sKBG4OE8NUC50xKU_6=6n37Zob8z=KxCttoMf4+iEwYcg@mail.gmail.com>
References: <1592833863766.52147@kuleuven.be> <33E98F20-6AF6-4A4D-A626-B9C4DA7C64C9@gmail.com> <CADMp+sKBG4OE8NUC50xKU_6=6n37Zob8z=KxCttoMf4+iEwYcg@mail.gmail.com>
MIME-Version: 1.0
Date: Thu, 25 Jun 2020 03:28:05 -0700
Message-ID: <CAO7Ng+vAS-XfXqHfTYioQwruRWckr4DwQuBKLsbokcQ1dQ3s8A@mail.gmail.com>
To: "oauth@ietf.org" <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004d69d005a8e60c1d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/m973SekVx_LgkrkgfBF6AzSU90Q>
Subject: Re: [OAUTH-WG] OAuth services/libraries wanted for security evaluation...
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jun 2020 10:28:09 -0000

Hey,

Have a look at https://github.com/IdentityServer/IdentityServer4

<https://github.com/IdentityServer/IdentityServer4>
I <https://github.com/IdentityServer/IdentityServer4>t’s an OIDC certified
.NET implementation

Thanks!
———
Dominick Baier

On 25. June 2020 at 11:27:34, Thibault Normand (thibault.normand@gmail.com)
wrote:

Hello Pieter,

I'm also interested (https://github.com/zntrio/solid), my OIDC framework is
not focused on building a compliant OIDC server but produce a restricted
and harmonized feature set according to your authentication use cases
(human, act as human, software, machine, iot). It mostly like libsodium is
(a high-level api) for low-level encryption operations (CHACHA20/Poly130).

The project is quite new and focused on authorization server building
blocks without the wire protocol constraints.
I tried to design flow without the wire protocol constraints in order to
make the building blocks useable in different context (standard / HTTP, or
IoT / CoAP).

Regards,

Le lun. 22 juin 2020 à 17:25, Filip Skokan <panva.ip@gmail.com> a écrit :

> Hello Pieter,
>
> I’m interested for my open source project.
>
> Filip
>
> Odesláno z iPhonu
>
> 22. 6. 2020 v 15:51, Pieter Philippaerts <pieter.philippaerts@kuleuven.be
> >:
>
> 
> Hello everyone,
>
> As part of a research project, I've created a test suite to test OAuth 2.0
> implementations and measure how well they implement the various
> MAY/SHOULD/MUST security recommendations in the OAuth standards. (It also
> includes test cases for the OIDC and FAPI RO/RW recommendations.) The tool
> is practically finished and will be made available to the public in a few
> months.
>
> I'm currently working on a security analysis of the OAuth2 ecosystem
> (i..e. I'm using the tool to test various OAuth/OIDC implementations) and
> I'm still looking for more candidates to test. If you are the author of an
> OAuth library or if you are running an OAuth service, feel free to contact
> me to get involved. Apart from my gratitude, I can offer you a free
> security audit of your product :-)
>
> Regards,
> Pieter
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>


-- 
Thibault Normand
"Il existe moins bien mais c'est plus cher !"
http://www.zenithar.org
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth