Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp3942930ybe; Mon, 16 Sep 2019 04:09:19 -0700 (PDT) X-Google-Smtp-Source: APXvYqxWVfr0t6l5KPLvj+dzA1iEOarypcSBIaQDS+tiG/YSK+0c31l8XqqlPH0yvMpvZFSTFJvY X-Received: by 2002:a50:ab58:: with SMTP id t24mr60849822edc.131.1568632159089; Mon, 16 Sep 2019 04:09:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568632159; cv=none; d=google.com; s=arc-20160816; b=wz0btUCEzTJh51dRaV+aVBye0teZxotHm1G1Hs9dguF17hFY04xRcX3c6ma7MtIBt6 jOA8Dbm3hZo9FBdkSwkBIvb1ZOAr/hgY43UGXjdk9Dzbelko02aUEYudniHVhJ+KpHhx eoTi+VWQpOBAgjL/I+dmsUOCVm35y6LJhGe+CBO5zE8/Bznr9bd8jdfYY3W6CBbRd2BB Yd6xKncQ7Wv/MilhGSAxB4ZTXmSi1Wzxk7OpjIyx4OcpFuquSux/oRNetMBw0mH9dn14 PVtL7vqTA5TjP+EAWdGUWy1UHhzq8BPLqK4jevx3nwhQIc2fbpaS3nZSBt7T+LOrK9oG U00g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:mail-followup-to:message-id:subject:cc:to:from:date :dkim-signature; bh=gPL7LiuOjEExSlU8WxEfL+s/iuBK0S+TbS2/pWpVnFg=; b=CGxXOQTMl+zhAi6YYk8K+yzjUd/vo4UewasetXv5ta/k9dNXFuN0wP1yd1nFMeTqBL ByKYQ6u4Ko6OGkiT+rCKxQAC9Gd162RIy3Ri2o+g2ahB99ZFQNA3u08xD4P4OpG3TXmN mgfVDU9xhXgtuWbzoSvVsMhHthZmIDa5fszeGOyNpD7jb5+htOMIhUnHhXjezcgPfD9z AH6D6scFrTSLS9v9eMG7CUYQt0QgXtPlkdqlEQUk0pc373KbP5eJ6c2lXmM6ydvka6fE VCgio2omZXwhBYKFNS8+Bw1UoWbyUnv7clpqJFB4JyopN3z2LTBzH244ch1NSOE9INCA WEWw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@silvair-com.20150623.gappssmtp.com header.s=20150623 header.b=GfjgdcZg; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f8si2414870ejd.270.2019.09.16.04.08.53; Mon, 16 Sep 2019 04:09:19 -0700 (PDT) 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=@silvair-com.20150623.gappssmtp.com header.s=20150623 header.b=GfjgdcZg; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726059AbfIPLIn (ORCPT + 99 others); Mon, 16 Sep 2019 07:08:43 -0400 Received: from mail-wr1-f54.google.com ([209.85.221.54]:38031 "EHLO mail-wr1-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725850AbfIPLIn (ORCPT ); Mon, 16 Sep 2019 07:08:43 -0400 Received: by mail-wr1-f54.google.com with SMTP id l11so38362942wrx.5 for ; Mon, 16 Sep 2019 04:08:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=silvair-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=gPL7LiuOjEExSlU8WxEfL+s/iuBK0S+TbS2/pWpVnFg=; b=GfjgdcZg2cmeG4aNv6M2e9Hwi/oImojVbzmZNjDhi3Z/W/fUPW+zDRYnCeR0NrmwW7 yYGzOjtibtzQORpMqZ8gT0neA3TLAzH7dJP95jZ6unENpvxN33CjxpRRcUntV6E/samt NngEZ6jqvS71dkHP7ewKsUfM95jcQmVSEFEpcNH2oPUC68IJvjlq0LbP8haijnBRv8nq rCAYcjmjYdQ6Zp/LRy/jBQFjLNzi88z1TokNSEJOCpR3owHkrJQ/kWFYdQU0L9XAE+zA 3JGSa2Bf/iLGFe3bAx2TtK7Jq0OQv6dTGzbY0MwIqB6xNpDt3MHAnk21Rzm8QFXZyOea RHQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=gPL7LiuOjEExSlU8WxEfL+s/iuBK0S+TbS2/pWpVnFg=; b=awyKRevieQuUeQENmE9KNGLoCeO/k0LxEc93rpCpeH1o/tONUz8EFtV4HrV1HDHro2 GD2n4L4HYGO5YihdDhXcJUSO6WFft9CzaXcezWyIU5nGK9gOR3brLBufsLKyw9dtS/IW fMSucXMe8WWLnxYbSfyIkDfXQs85gSCVCLKc2XEgMHwb8yNT04vjlR8NM8+BEfk7RzFl DAf2usCDxt9s3SsWrbMM3dIU12eYLyQYzCCze8RqaM4dnKl3nDNTw/vkkL5LAAwGzOy6 sDj5tMX25zN3D1M/qkmwB+NrT5HrvY5jzuzxTh+h5vt21DKWo8q4iUno9YLmlVETGgoc rWcQ== X-Gm-Message-State: APjAAAXUgoRRz0tzSnMHjelbSz/DdoKThTYS4m1X0ggaKuM4YBcYHKuY 0oxh0MV75lIFhWK47mHnU8WT+RHYWn4= X-Received: by 2002:adf:e9ce:: with SMTP id l14mr25653079wrn.264.1568632121187; Mon, 16 Sep 2019 04:08:41 -0700 (PDT) Received: from mlowasrzechonek2133 ([217.153.94.18]) by smtp.gmail.com with ESMTPSA id b22sm6386486wmj.36.2019.09.16.04.08.40 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 16 Sep 2019 04:08:40 -0700 (PDT) Date: Mon, 16 Sep 2019 13:08:39 +0200 From: =?utf-8?Q?Micha=C5=82?= Lowas-Rzechonek To: "Gix, Brian" Cc: "linux-bluetooth@vger.kernel.org" , "Stotland, Inga" Subject: Re: [PATCH BlueZ 1/1] mesh: Add local/remote bools to DevKey transactions Message-ID: <20190916110839.jscnzmdnnrbefmqm@mlowasrzechonek2133> Mail-Followup-To: "Gix, Brian" , "linux-bluetooth@vger.kernel.org" , "Stotland, Inga" References: <20190915081408.18116-1-brian.gix@intel.com> <20190915081408.18116-2-brian.gix@intel.com> <20190916095845.htvyalekgr4k2ybt@mlowasrzechonek2133> <8DD9DDA0-1081-479F-B215-2E815B1A8F27@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <8DD9DDA0-1081-479F-B215-2E815B1A8F27@intel.com> User-Agent: NeoMutt/20180716 Sender: linux-bluetooth-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org Hi Brian, On 09/16, Gix, Brian wrote: > > 1. If the application would like to change Config Server states on the > > local node, it would need to: > > - call ImportRemoteNode, passing the address of a *local* node and > > the device key obtained from provisioner > > - call DevKeySend to a *local* address, with remote flag set to true > > - receive responses via DevKeyMessageReceived from *local* node, > > with remote flag set to true > > > > Essentially this means that talking to a local node using device > > security behaves in the same manner as if the node was a remote one. > > > > 2. If the application would like to implement an external model that > > uses device security, it would: > > - receive DevKeyMessageReceived calls from remote nodes, with remote > > flag set to false > > - send responses by calling DevKeySend to a *remote* address with > > remote flag set to false > > > > This means that calling DevKeySend to a *local* address with remote flag > > false would be forbidden, in order to force the application to use > > ImportRemoteNode first? > > I think that is all basically correct. I switched the Boolean > bit-sense such that the boolean parameter is “remote” on the send and > “local” on the receive. > > And most importantly, your last point is an emphatic yes.... you > will need to import your own device key to the key ring if you want to > talk to your own builtin servers. The one exception will be nodes > that have called “Create()” which are generating brand new mesh > networks with themselves as unicast 0001. Ok, sounds good! -- Michał Lowas-Rzechonek Silvair http://silvair.com Jasnogórska 44, 31-358 Krakow, POLAND