为什么目前没有支持/不能在LE安全连接中配置WorkSun身份验证方法？

嗨，Zabor，
欢迎来到论坛！！
当您将安全级别设置为“加密与加密的身份验证配对”或“身份验证与加密的LLE安全连接配对”时，您应该进行身份验证意味着您的设备应该具有一些I/O身份验证功能。因此，如果将I/O能力设置为“无输入无输出”，则将您的设备推回UN身份验证配对，这是不可能的，因为您已经为“身份验证配对”设置了安全级别。
请找到一个与此反应附带的BLE规格屏幕截图。在这里您可以看到，当您设置“身份验证”配对时，将设置MITMFLAG，并检查I/O能力。现在，如果你没有I/O能力，你的配对应该是“只是工作”意思是“未经认证”。
所以基本上，在设置安全级别之前，你应该知道你的设备I/O能力。
希望这对你有帮助！！
如果你有任何进一步的疑问，请告诉我们。
当做，
吉安
PNG
51.7 K



     以下为原文
  Hi Zabor,
       Welcome to the Forum!!
    When you set the security Level as 'Authenticated Pairing with Encryption' or 'Authenticated LE Secure Connection Pairing with Encryption' you are supposed to go for Authentication means your device should have some I/O capabilities for authentication. So, if you set the I/O capabilities as 'No Input No output' you are pushing back your device for Un-authentication pairing which is not possible because you have set the security level for 'Authenticated Pairing before.
     
    Please find a screenshot of BLE spec attached with this response. Here you can see that when you set 'Authenticated' pairing ,the MITM flag will set and it will check for I/O capabilities. Now if you do not have I/O capabilities , your pairing should be 'just work' means 'Un-Authenticated' .
    So basically before setting the Security Level you are supposed to be known about your device I/O capabilities.
     
    Hope this will help you!!
     
    Please let us know if you have any further queries.
     
    Regards,
    Gyan

•   Security.PNG 51.7 K
  
  

听起来像你说的是你选择I/O能力和安全级别的顺序对IDE建立“公正工作”配对/认证产生了影响。
因此，如果我们先设置I/O能力，在设置安全设置之前，那么不会有错误吗？



     以下为原文
  @GYAN It sounds like you are saying that the order in which you choose the I/O capability and the security level makes a difference for the IDE setting up the "just works" pairing/authentication.
    Thus, if we set the I/O capability first, before setting the security settings, then there will be no error(s)?

不，配置IO能力和安全级别的顺序将无法解决这个问题。它仍然会抛出错误。
在VoL3，蓝牙规范的C部分中，声明了最后一个安全级别或安全级别4是“与加密配对的身份验证安全连接”。它还表示安全级别4也应满足安全级别3的安全要求。简单地说，安全连接总是带有“认证”。没有办法有一个未经验证的安全连接（我们可以辩称SMP说它是允许的，但是GAP说认证是强制性的）。



     以下为原文
  No, the order of configuring IO capabilities and Security level will not solve the issue. It will still throw the error.
 
In Vol3, Part C of the Bluetooth spec, it is stated that the last security level or security level 4 is "Authenticated LE Secure Connections pairing with encryption.". It also says that security level 4 shall also satisfy the security requirements for security level 3. In simple words, Secure Connections always comes with "Authenticated". There is no way to have an unauthenticated secure connection (we can argue that the SMP says it's allowed but the GAP says authentication is mandatory).