Received: by 2002:a25:c205:0:0:0:0:0 with SMTP id s5csp2240161ybf; Mon, 2 Mar 2020 04:55:07 -0800 (PST) X-Google-Smtp-Source: APXvYqwkXMLbByYPgMIOWWs2Ws4ldPlGK9di4Dr3E4ti8gudldWIaBxSurbZ4IrsaTs+sVf4BBXc X-Received: by 2002:a9d:5d09:: with SMTP id b9mr12823733oti.207.1583153707830; Mon, 02 Mar 2020 04:55:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1583153707; cv=none; d=google.com; s=arc-20160816; b=E6QIDgzVkAVfwIE8ly8W97P6npjdc/2qeUS+dKZ/ABJuzahGrB4eO2ajvjnmi/OYff qHJf2IZg9QjC7gVLFHQryFeXCCqgacj8BnCvuHbCSzUsSnevunOMb+7bKYnM4p8yPnE5 HwRfpnfaMhFwd4wXmgJSu9i+soCX9cI9ENnNWjchra7XgM2kTblr7s7PNsIYlDTTKgnZ TvUiengqh+B6Vl37cd/YoW0ykTzXWeMbloLmSJqYmNUEHQ/dEE5D4VH2ZuQy+74qYkTJ ePraAnMxeqxbsSCMJ71a2wZsQlgH13ZyrZYGMj4a3pWE2lL5J396QV0aa7imddqKYiKQ qsMg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:cms-type :content-transfer-encoding:date:message-id:cc:to:from:reply-to :subject:mime-version:dkim-signature:dkim-filter; bh=yc2Jy54D36WaqiistaUeieTfIgy8H5fccjt9Y75F0KA=; b=L6HeDo4uWSLU/SJew4fGIYGOmYVhBioOBVhcur7HpgvNzFrO0si6xmsbN6R2LdouN5 wlHA5Q9PN8bt4NGvTmpY5X57XQV3JF35Asw3ZI2DJX2KIXsGxc7ACb27bVtNci+0KdzI sAVVtqpUvefrgx6txWAJq5TkHRJKq0XhMmm5EbFpgaT2Utgp0S7GF0inSr0e3S0/KxJg +O9VREC0TACJ9nrICYZyqkmWHaI9PAbw10YeBB1g9nl/aOS5hje7C4W+QnzKUuuvjXwO yFWCJEp3sA6QHLv6wK44qmMgtKTZ7/tu0WoHtED8gSUuW9RlDiTlAEb/vJAQ6DR00aGJ rH0A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@samsung.com header.s=mail20170921 header.b=f0qnsr6v; spf=pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=samsung.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v81si5580483oia.114.2020.03.02.04.54.40; Mon, 02 Mar 2020 04:55:07 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@samsung.com header.s=mail20170921 header.b=f0qnsr6v; spf=pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=samsung.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727947AbgCBMy3 (ORCPT + 99 others); Mon, 2 Mar 2020 07:54:29 -0500 Received: from mailout4.samsung.com ([203.254.224.34]:40457 "EHLO mailout4.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727745AbgCBMy3 (ORCPT ); Mon, 2 Mar 2020 07:54:29 -0500 Received: from epcas5p3.samsung.com (unknown [182.195.41.41]) by mailout4.samsung.com (KnoxPortal) with ESMTP id 20200302125423epoutp043dfa0ed1f723205d666a778bc7a2b2e6~4fd6QEutc2993929939epoutp04t for ; Mon, 2 Mar 2020 12:54:23 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 mailout4.samsung.com 20200302125423epoutp043dfa0ed1f723205d666a778bc7a2b2e6~4fd6QEutc2993929939epoutp04t DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsung.com; s=mail20170921; t=1583153663; bh=yc2Jy54D36WaqiistaUeieTfIgy8H5fccjt9Y75F0KA=; h=Subject:Reply-To:From:To:CC:Date:References:From; b=f0qnsr6vO2MeA0yE+ux9EybId4780vx2xKO4wDbFyahol5TDa9BU62YjlU9vbf6Wj m4pp7Y4BYzuDSX9k2mtTwN9bFywWTsvUSSzGYN200qgBEGDfKPNVOM6vGihP4V07xi B6ZQNvNUtGtBtJ0j+q6BwlImaA+ZxCFGNSpji48I= Received: from epsmges5p3new.samsung.com (unknown [182.195.42.75]) by epcas5p3.samsung.com (KnoxPortal) with ESMTP id 20200302125423epcas5p3d000a22b07c08e0b5b19db948df2dc1e~4fd50FxKN2313223132epcas5p3w; Mon, 2 Mar 2020 12:54:23 +0000 (GMT) X-AuditID: b6c32a4b-32dff70000014cad-5b-5e5d01ff7bb9 Received: from epcas5p4.samsung.com ( [182.195.41.42]) by epsmges5p3new.samsung.com (Symantec Messaging Gateway) with SMTP id 24.85.19629.FF10D5E5; Mon, 2 Mar 2020 21:54:23 +0900 (KST) Mime-Version: 1.0 Subject: Regarding OOB authentication method & action for Mesh provisioner Reply-To: anupam.r@samsung.com From: Anupam Roy To: "linux-bluetooth@vger.kernel.org" CC: Semun Lee , Dohyun Pyun , Nitin Jhanwar X-Priority: 3 X-Content-Kind-Code: NORMAL X-Drm-Type: N,general X-Msg-Generator: Mail X-Msg-Type: PERSONAL X-Reply-Demand: N Message-ID: <20200302125344epcms5p3e31d97ef6263e0513b94f6306536269b@epcms5p3> Date: Mon, 02 Mar 2020 18:23:44 +0530 X-CMS-MailID: 20200302125344epcms5p3e31d97ef6263e0513b94f6306536269b Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Sendblock-Type: REQ_APPROVE CMS-TYPE: 105P X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrEIsWRmVeSWpSXmKPExsWy7bCmlu5/xtg4g/PbhS2WfP/IZjHnWh+z xbZ17cwWxzY9ZXJg8ejbsorR4/MmuQCmKC6blNSczLLUIn27BK6MmzsmMxUcY684s2oXewPj JLYuRk4OCQETiZvHrrJ3MXJxCAnsZpS43/qKuYuRg4NXQFDi7w5hkBphAS+J+zf6WUBsIQE5 icVT17KBlAgLaErc3JgCEmYTUJf49XAHWImIgLvEnv23GUFsZoFCidWL1jFDrOKVmNH+lAXC lpbYvnwrI4QtKnFz9Vt2GPv9sflQcRGJ1ntnoXoFJR783M0I07t1wVNmkJMlBLoZJV7vWM8E 4UxhlPh48S0TRJW5xP/ut2AdvAK+EvOuLgKLswioSrzpXwI1yUXi+KPbLBCXyktsfzsH7Hdm oMfW79KHKJGVmHpqHRNECZ9E7+8nTDDP7JgHYytJbL0+nxXClpDo27wLKu4h8fXELmi4BUqs +NfGPoFRfhYidGchWTwLYfECRuZVjJKpBcW56anFpgXGeanlesWJucWleel6yfm5mxjBKUHL ewfjpnM+hxgFOBiVeHh/MMTGCbEmlhVX5h5ilOBgVhLh9eWMjhPiTUmsrEotyo8vKs1JLT7E KM3BoiTOO4n1aoyQQHpiSWp2ampBahFMlomDU6qB0dNR+Y5ky6SnnrsCpj488qxQb2M770fv 5T2Zh5p8TweLZ1gkCS9MvPg+//stoWvn7xZ+WJf74PyreANpmSfeG+YWsLBHbmz+tmLycSXp WQEPbyp90D93aaFIuejpJ2XX1GolHiZK+5+3XD/3LP/iPzvfHei4u2mm5Wce1hNaXwNLRJxv 77hUHaDEUpyRaKjFXFScCAA/1h6MBQMAAA== X-CMS-RootMailID: 20200302125344epcms5p3e31d97ef6263e0513b94f6306536269b References: Sender: linux-bluetooth-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org Hello, Regarding remote node provisioning, currently, it seems 'meshd' is choosing Provisioning method & actions internally, based on remote node's capabilities. - Choosing Method :- /* Parse OOB Options, prefer static, then out, then in */ - Choosing Action:- Based on high bit set in the action octet: u16_high_bit(l_get_be16(data + 6)), in case of OUT OOB or u16_high_bit(l_get_be16(data + 9)) in case of IN OOB Is the above preference for choosing Authentication Method, based on some pre-defined security level? If yes, can such security levels can be made available to application for configuration? Also, I would like to know, whether there is any plan to Request external provisioning Agent to choose Provisioning method & specific action? The reason being, some *application* may be interested in a particular Security level & Authentication action, depending on its own I/O capabilities. BR, -Anupam Roy BR, -Anupam Roy