jameshollyer

Most recent activity

• setSecurity not working as expected

  @jameshollyer started

  • 16 comments
  • 4,115 views

  @jameshollyer replied
• setSecurity not working as expected

  in Puck.js, Pixl.js and MDBT42 • 4 years, 4 months

  

  Ok it is all working now with the newest firmware. Thanks a million Gordon I really appreciate it.

  ps. That watch is awesome!

• setSecurity not working as expected

  in Puck.js, Pixl.js and MDBT42 • 4 years, 4 months

  

  Thanks for looking into this Gordon! How are you testing that this is working? I am using the NRFConnect app as a source of truth. I uploaded your code to my puck and tried to get the secure characteristic from that app and once I entered the passkey it just disconnects(same as before). I am also trying on an objective-c core bluetooth application I wrote to test connecting to the app and I get an "unknown error" after I type in the passkey(also, same as before). I am wondering what you are using to show that is does work as intended? I will try again with the new firmware.

• setSecurity not working as expected

  in Puck.js, Pixl.js and MDBT42 • 4 years, 5 months

  

  Ping

• setSecurity not working as expected

  in Puck.js, Pixl.js and MDBT42 • 4 years, 5 months

  

  I don't think it was ever working. When I said it was working it is because the passkey prompt popped up. I was never able to connect to it. I thought I was reproducing a reported Web Bluetooth bug in Chrome. However, when I dug further I found the issue was in the call to Core Bluetooth. I have now made a standalone Objective C OSX application that uses core bluetooth to connect and I am still getting the error. I then tried it on the NRF Connect app and it did not work there. I also tried through Chrome's web bluetooth on Windows and it did not work there either. This is leading me to believe the issue might be in the Puck.

  I did restart my Mac and try again and I am still not able to connect to the protected characteristic.

• setSecurity not working as expected

  in Puck.js, Pixl.js and MDBT42 • 4 years, 5 months

  

  I would like to open this back up. I am not sure this is working properly. It is now prompting me for the passkey on mac os and android(using the nrf connect app). In Mac when I enter the key it gives me an "unkown error" and on the NRF connect app it acctually disconnects me from the puck when I enter the passkey.

  My current code is :

  NRF.setSecurity({passkey:"123456", mitm:1, display:1});
  NRF.setServices({
    0xabcd : {
      0xAB40 : {
        value : "Hello",
        maxLen : 50,
        notify: true,
        readable: true,
        writable: true,
      },
      0xAB41 : {
        value : "Hello",
        maxLen : 50,
        notify: true,
        readable: true,
        writable: true,
        security: {
          read: {
            encrypted: true,
            passkey:"123456",
            mitm: true,
            lesc: true,
            signed: false
          },  write: {
            encrypted: true,
            passkey:"123456",
            mitm: true,
            lesc: true,
            signed: false
          }
        }
      }
    }
  }, {advertise: [ 0xabcd ]});
  var  on = false;
  setWatch(function(e) {
    on = !on;
    LED1.write(on);
    var pressTime = e.time - e.lastTime;
    NRF.updateServices({
      0xabcd : {
        0xAB40 : {
          value : "time: " + e.time,
          notify: true
        },
        0xAB41 : {
          value : "lastTime: " + e.lastTime,
          maxLen : 50,
          notify: true
        },
      }
    });
  }, BTN, { repeat:true, edge:"falling", debounce: 50 });
  

  everything works fine on characteristic 0xAB40 but I cannot get the secure 0xAB41 characteristic to work. Please advice.

• setSecurity not working as expected

  in Puck.js, Pixl.js and MDBT42 • 4 years, 6 months

  

  That did the trick. Much appreciated!

• setSecurity not working as expected

  in Puck.js, Pixl.js and MDBT42 • 4 years, 6 months

  

  Now http://www.espruino.com/binaries/travis/­master/ does not even have a file for puck js.

• setSecurity not working as expected

  in Puck.js, Pixl.js and MDBT42 • 4 years, 6 months

  

  The espruino_2v04_puckjs.zip file is not working for me. I even went and installed 2v03 to make sure it was not updating and that I was doing it properly. 2v03 worked just fine. That master branch version of 2v04 does not. The NRF Connect app says "Starting DFU" then immediately says "disconnecting..."

  I also wanted to say that I am using web-bluetooth to connect to the characteristic. Here is my code for that:

  connectClick(event) {
          console.log('clicked', event);
          navigator.bluetooth.requestDevice({
              filters: [{
                  services: [0xabcd],
                }]
          })
          .then(device => {
              console.log("requested", device);
              return device.gatt.connect();
          })
          .then(server => {
              console.log('got server', server);
              return server.getPrimaryService(0xabcd);
          })
          .then(service => {
              console.log('got service', service);
  
              service.getCharacteristic(0xAB40).then(c­haracteristic => {
                  this.startListeningForTime(characteristi­c);
              });
              service.getCharacteristic(0xAB41).then(c­haracteristic => {
                  this.startListeningForTime(characteristi­c);
              }).catch(error => {
                  console.log('error', error);
              })
          })
      }
  
      handleCharacteristicValueChanged(event) {
          var enc = new TextDecoder("utf-8");
          var value = event.target.value;
          console.log('Received ' + enc.decode(value))
          // TODO: Parse Heart Rate Measurement value.
          // See https://github.com/WebBluetoothCG/demos/­blob/gh-pages/heart-rate-sensor/heartRat­eSensor.js
      }
  
      startListeningForTime(characteristic) {
          characteristic.startNotifications()
          .then(char => {
              console.log('notification started', char)
              // Writing 1 is the signal to reset energy expended.
              char.addEventListener('characteristicval­uechanged', this.handleCharacteristicValueChanged.bi­nd(this));
          })
      }
  

  Just wanted to make sure that I should not be able to access that without entering a passkey if it is working.

• setSecurity not working as expected

  in Puck.js, Pixl.js and MDBT42 • 4 years, 6 months

  

  I am trying to get some sort of proof that there is any security things happening at all. Most notably is that there is no prompt for a pin at any point.

  Here is all the code I am uploading to my puck.js although I don't think anything but the first line(obviously copy pasted from the docs) is relevant.

  NRF.setSecurity({passkey:"123456", mitm:1, display:1});
  NRF.setServices({
    0xabcd : {
      0xAB40 : {
        value : "Hello",
        maxLen : 50,
        notify: true
      },
      0xAB41 : {
        value : "Hello",
        maxLen : 50,
        notify: true,
        security: {
          read: {
            encrypted: true,
            mitm: true,
            lesc: true,
            signed: false
          }
        }
      }
    }
  }, {advertise: [ 0xabcd ]});
  var  on = false;
  setWatch(function(e) {
    on = !on;
    LED1.write(on);
    var pressTime = e.time - e.lastTime;
    NRF.updateServices({
      0xBC10 : {
        0xAB40 : {
          value : "time: " + e.time,
          notify: true
        },
        0xAB41 : {
          value : "lastTime: " + e.lastTime,
          maxLen : 50,
          notify: true
        },
      }
    });
  }, BTN, { repeat:true, edge:"falling", debounce: 50 });
  

  Puck js is updated to 2v04.