Re: [OAUTH-WG] Where / how do we report security risks?

"L. Preston Sego III" <LPSego3@gmail.com> Fri, 01 February 2013 15:34 UTC

Return-Path: <lt.sego@gmail.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 77B5921E803D for <oauth@ietfa.amsl.com>; Fri, 1 Feb 2013 07:34:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K54oW7vcXfIp for <oauth@ietfa.amsl.com>; Fri, 1 Feb 2013 07:34:11 -0800 (PST)
Received: from mail-vb0-f43.google.com (mail-vb0-f43.google.com [209.85.212.43]) by ietfa.amsl.com (Postfix) with ESMTP id CFE2C21E8030 for <oauth@ietf.org>; Fri, 1 Feb 2013 07:34:10 -0800 (PST)
Received: by mail-vb0-f43.google.com with SMTP id fr13so2544573vbb.30 for <oauth@ietf.org>; Fri, 01 Feb 2013 07:34:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=IK41Sy8QCSzyMNGyZJw5T+zIktyxFXQwg33TDKM57Ug=; b=UTCxEEoxVIxDXATSXeYu/GTmZeUuzMftv1z4zQnr1vUCjq2I9RM+XG0Ndk2cIrlgt+ bVhrrRcqL8iYYePOLGMj7WBERUQGiPaA8rxG3a685gunQhBCCSrwSZ7uXVpoYhIoiu/7 JMAbRSEhDt1JtF5E2wHoCsoRDdTwwpWdWarXCMVIFOnoF7hQX1IYvJfGJYe5N44+onka XhYDX9uTOENPkIFPRS5YBzlz441QJ2dKD4cmUuF0W/URbHj9oSC0DomQP8rhnCl+KCd/ DqTUDjSTAzdczGfwjIpVDq4IszYiVvTiC4CBrLKqjsi68XiPQNBdUH4DUuF1z6RsWWZo 2FSg==
X-Received: by 10.52.69.39 with SMTP id b7mr10081815vdu.124.1359732850329; Fri, 01 Feb 2013 07:34:10 -0800 (PST)
MIME-Version: 1.0
Sender: lt.sego@gmail.com
Received: by 10.58.238.166 with HTTP; Fri, 1 Feb 2013 07:33:50 -0800 (PST)
In-Reply-To: <1359732663.49190.YahooMailNeo@web31808.mail.mud.yahoo.com>
References: <CAEeqsMaCyF31X50=A6qM7QU2zbMLoSE4C-F8oe5NrWyiCb8hZA@mail.gmail.com> <1359732663.49190.YahooMailNeo@web31808.mail.mud.yahoo.com>
From: "L. Preston Sego III" <LPSego3@gmail.com>
Date: Fri, 01 Feb 2013 10:33:50 -0500
X-Google-Sender-Auth: UWYcC0lkQzdNpD8S3YFquwfTNiI
Message-ID: <CAEeqsMbM9YabORL6XudocmRkvJndt6CFJGjDPp60LbH-kvy2KQ@mail.gmail.com>
To: William Mills <wmills_92105@yahoo.com>
Content-Type: multipart/alternative; boundary="90e6ba475d4f88883804d4ab79c6"
X-Mailman-Approved-At: Mon, 04 Feb 2013 08:12:33 -0800
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Where / how do we report security risks?
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 01 Feb 2013 15:34:11 -0000

ok, cool. I don't have any sort of specific implementation or anything.
Just a concern. thanks!


On Fri, Feb 1, 2013 at 10:31 AM, William Mills <wmills_92105@yahoo.com>wrote:

> Here is probably your best bet if it's a design question.  If it's a
> specific implementation then send it to the company in question first if
> you think they have a vulnerability.
>
>   ------------------------------
> *From:* L. Preston Sego III <LPSego3@gmail.com>
> *To:* oauth@ietf.org
> *Sent:* Thursday, January 31, 2013 6:01 AM
> *Subject:* [OAUTH-WG] Where / how do we report security risks?
>
> Don't want hackers to try anything on oauth2-using applications...
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>
>
>