Oauth-security-reports -- Information about security vulnerabilities concerning the OAuth specifications and OAuth implementations | |
|
|
About Oauth-security-reports | |
This list was created to allow security researchers and other parties to submitting information related to discovered security vulnerabilities concerning the OAuth specifications and OAuth implementations. The aim is to provide those who discover security problems to have an easy way to report their findings to a small group of standardization experts, which includes the OAuth working group chairs, in a confidential manner. The group then has to decide on how to utilize the obtained information to initiate discussions on IETF mailing list or with impacted implementers.
To see the collection of prior postings to the list, visit the Oauth-security-reports Archives. (The current archive is only available to the list members.) |
|
Using Oauth-security-reports | |
To post a message to all the list members, send email to
oauth-security-reports@ietf.org.
You can subscribe to the list, or change your existing subscription, in the sections below. |
|
Subscribing to Oauth-security-reports | |
Subscribe to Oauth-security-reports by filling out the following form. You will be sent email requesting confirmation, to prevent others from gratuitously subscribing you. Once confirmation is received, your request will be held for approval by the list moderator. You will be notified of the moderator's decision by email. This is also a private list, which means that the list of members is not available to non-members. | |
Oauth-security-reports Subscribers | |
|
![]() version 2.1.39 |
![]() |
![]() |