Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp3839970pxb; Fri, 11 Feb 2022 08:52:54 -0800 (PST) X-Google-Smtp-Source: ABdhPJz1CqlIUko9ZHGjfDptrACIBBSyLqA0ikxYHT0Zo29uTs5d8fPNLR8gcKcx+xyHqGjUJc5O X-Received: by 2002:a17:902:d34b:: with SMTP id l11mr2255908plk.137.1644598374043; Fri, 11 Feb 2022 08:52:54 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1644598374; cv=none; d=google.com; s=arc-20160816; b=kmOvNnqdI6tg1gTq2h4rhLMKH1pEyQSZ6Z0XXC9+XwPbk8IBGz0U1c511JUvFottuW G55mHc/0fMDMF4Ts0BhWXqHj27Lblj5FzZrIKocUNq4fuQuphcKWoi0R0ND0d3zMi4+w Z7j6hjen0XDx8u0omx5BqfXxMpegQmMcYWD0AaZE2xeAqS9w3PDm+sBkzt/ocOtVyirF DsiyL+jIk24/H770HdwlqyfbX31lunphYIQbMVBYdDxy+OodK6FKgjRapsxEviQfAOXW 2+0L5COMbz5t4hq5xPFooz9Blzw4tLTGsgvG1OEQX47aVBvb4Z8wC0ZfA2cbolHkL9cg Og6w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=3fCgT38Arn4wQQoi+ovyGr4e/8ACygaFfOcJVPGk/8U=; b=rpkkBLf40RxeTcSvsJgX6tc4SSNykGmIFM9b8nVF/yS65WtCM+BdI/CYx0YvMRMDWF zU0bfMds1/O/qdzBY2zUsdDZCriECcW0Wx1qqUZTdwL/KAMg3ZYgSqcjjiATeCD6gu5C kFGHbX672UVcC1H96plYF8gF1IQoO+KF7m2/LPbwlik+6I2jRc3c642wPBh59QI5Al4k r36JoC4z8NQ0ua0gL4TutrcKox7A7/7/9KBQ32Ru3fVbIhQwhwH2y9fADpNKHIGa1MwZ p31QZ2M4XW+pRFTcEFXgeHrtVvR0w6ickp5GbCJ7Cce9ZP/M3CkmcIGpUvom3WDkgLj4 Z5kg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=X1kqHrKw; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id 7si12377881pgc.71.2022.02.11.08.52.26; Fri, 11 Feb 2022 08:52:54 -0800 (PST) Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=X1kqHrKw; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1345954AbiBKACQ (ORCPT + 99 others); Thu, 10 Feb 2022 19:02:16 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:59478 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239080AbiBKACP (ORCPT ); Thu, 10 Feb 2022 19:02:15 -0500 Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D9BC4B43 for ; Thu, 10 Feb 2022 16:02:15 -0800 (PST) Received: by mail-ed1-x535.google.com with SMTP id cf2so13680131edb.9 for ; Thu, 10 Feb 2022 16:02:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3fCgT38Arn4wQQoi+ovyGr4e/8ACygaFfOcJVPGk/8U=; b=X1kqHrKw7icmlX1Mahkh5QLIq4eK2VmAD8BGlp8hIHuBP0Ysb/rbRk7sk80wOMlcy5 f2q2BqE50X8zzxUgAqScG8LawmQwk7n84WeIrQBWBiVe1poHQ/U8e5XV3EJphpHp2AKV xuHQCpSciLiGCK8tD6HqsRUM9mPUX+ZhbEIok= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3fCgT38Arn4wQQoi+ovyGr4e/8ACygaFfOcJVPGk/8U=; b=RYaTJgPKqXt3zp1E5oUVuutEKX/gsxLF3wZl6msqdw3tBzTxDb+xQZ169mi36rHY8M X6nAx8GKvTVM2Ut1rJPXdMv4F/ARLAlToFIe1e6sJXfumKhgLlod6wBo3MqJ/VDNzaU7 MIXZGpCglJA+p2XtnOUizBd9onjAwLEJEoe6+KEnHqrkolxUCQqsCcbBFtkpPLpq5wWp 7rg9bBvnT4LAaYuhH12mzk2yQzzA8sD7ExwOjd85Xqj16tjzrDg8rKwuW54RnC2xj6XI CU9rSqk1anJFBFCow3HVOhrWiI7Go66+CPVLzC840/sr6lUPVoN8dXv1kVfouYJDve9D ZnvQ== X-Gm-Message-State: AOAM531qPaysAqMFiXBJmI2ngslSH6+wmLHjGrEQ2aBZCuopEBseArWQ WfpKi+TZDZ0w7lCiWk2veQ+YLBtSq4/OX0xW X-Received: by 2002:aa7:c04d:: with SMTP id k13mr10781113edo.301.1644537733673; Thu, 10 Feb 2022 16:02:13 -0800 (PST) Received: from mail-wr1-f44.google.com (mail-wr1-f44.google.com. [209.85.221.44]) by smtp.gmail.com with ESMTPSA id h8sm10286273edk.14.2022.02.10.16.02.13 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 10 Feb 2022 16:02:13 -0800 (PST) Received: by mail-wr1-f44.google.com with SMTP id v12so12402528wrv.2 for ; Thu, 10 Feb 2022 16:02:13 -0800 (PST) X-Received: by 2002:a05:6000:1e15:: with SMTP id bj21mr8110680wrb.222.1644537732577; Thu, 10 Feb 2022 16:02:12 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Sonny Sasaka Date: Thu, 10 Feb 2022 16:02:01 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Question about Trusted property To: Luiz Augusto von Dentz Cc: BlueZ Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org Hi Luiz, Thanks for the clarification. So my guess was right that it does not have to do with bondedness. In that case, do you think it makes sense to add a "Bonded" flag property to org.bluez.Device1? There are some use case flows that pair with a peer device but do not actually bond, and just with Paired property the UI can't know whether to show this device as "Bonded" or not. On Thu, Feb 10, 2022 at 1:30 PM Luiz Augusto von Dentz wrote: > > Hi Sonny, > > On Thu, Feb 10, 2022 at 11:23 AM Sonny Sasaka wrote: > > > > Dear maintainers, > > > > Friendly ping on this question. Does adding "Bonded" property to > > org.bluez.Device1 make sense? > > > > On Fri, Feb 4, 2022 at 4:02 PM Sonny Sasaka wrote: > > > > > > Hi Luiz/BlueZ maintainers, > > > > > > What is the purpose of the Trusted property on org.bluez.Device1 > > > interface? Does it mean whether the device is bonded? My experiment > > > with BlueZ shows that sometimes a device with "Trusted" property set > > > is not bonded (does not have pairing key stored) and also vice versa, > > > so I am assuming that the Trusted property means something else. What > > > is an example use case of the Trusted property? > > > > > > Eventually, what I am trying to achieve is for BlueZ clients to find > > > out whether a device is Bonded or not. Using the Paired property is > > > not very accurate because it is set to true during connection although > > > the device is not bonded (pairing key does not persist after > > > disconnection). For this purpose, I am about to propose adding > > > "Bonded" property to org.bluez.Device1. Some use cases include when > > > there is a temporary pairing with a peer device we don't want UI to > > > show that the device is in the Bonded device list. What do you think > > > about exposing the Bonded state via D-Bus? I will do the > > > implementation if this idea makes sense. > > > > > > Thanks! > > Trusted primary use is to bypass agent authorization, so when set the > agent will not have to authorize profile connections, and yes you can > set a device to be Trusted even without having it paired since the > bonding procedure refers to authentication rather than authorization > which is what Trusted controls. > > > -- > Luiz Augusto von Dentz