OBi110 firmware updated Aug-24-2014 to Ver 1.3.0 (Build 2872)
SteveInWA:
Dude: just use a unique, strong password for your OBiTALK portal account. BFD.
No, nobody is going to get into hacking the token exchange procedure here.
Willy-Bill:
I'm not concerned with the token being stored, and sent to the device during provisioning updates. However, passwords not being stored anywhere is kind of moot, as it has to be stored somewhere. If you use online provisioning, if that password wasn't stored, then it would be erased upon update of the provisioning.
BTW, Hey Steve (aka Bluescat).
SteveInWA:
Quote from: Willy-Bill on March 15, 2015, 10:44:57 pm
I'm not concerned with the token being stored, and sent to the device during provisioning updates. However, passwords not being stored anywhere is kind of moot, as it has to be stored somewhere. If you use online provisioning, if that password wasn't stored, then it would be erased upon update of the provisioning.
BTW, Hey Steve (aka Bluescat).
Hey Willy-Bill! Do I know you? My cat in my profile photo is Willie, btw.
I'm not sure what point you are making, but I think you are referring to password entry during the process. Just to clarify: when a user goes through the OBiTALK portal to set up OAUTH 2.0 authentication, Obihai is not involved in the user's Google password exchange. The user first signs on to their Google account, on a typical Gmail or GV web page, which is a authenticated and encrypted channel between Google and the user's browser. Obihai isn't involved in that at all. After the user is signed in, as indicated by various session cookies, the user logs into the OBiTALK portal in another browser tab, and kicks off the OAUTH 2.0 setup. At this point, OBiTALK sends a request to Google to grant OBiTALK permission to access a service on the (already signed-on) Google user's account. Then, the user gets a pop-up window, on a new, secure Google web page, already signed into their Google account. This pop-up is where the user says "yes, OBiTALK can access service xyz on my account", and after that point, the secure token is transferred from Google to OBiTALK to the device. So, at no point does Obihai have the user's Google password. In fact, right after performing this procedure, the user can change their Google password, and not have to go through the setup again.
At any time, a Google user can view and, if necessary, revoke this permission, here:
https://security.google.com/settings/security/permissions
I hope this helps.
-DC-:
I updated the firmware on my OBi110 to 2872 and now when I'm in the middle of a phone call the device likes to reboot itself, which also terminates the call. I've done a reset and that didn't fix the problem. At this point I'd be satisfied with downgrading back to the older (working) firmware but alas, it is nowhere to be found! Help?
SteveInWA:
Quote from: -DC- on March 31, 2015, 06:44:17 pm
I updated the firmware on my OBi110 to 2872 and now when I'm in the middle of a phone call the device likes to reboot itself, which also terminates the call. I've done a reset and that didn't fix the problem. At this point I'd be satisfied with downgrading back to the older (working) firmware but alas, it is nowhere to be found! Help?
Your issue is unrelated to the firmware upgrade, or to this discussion thread. I haven't seen any significant reports from a large number of 110 users with this symptom. It's more likely due to a home network issue. I suggest you start a new discussion specific to your issue.
Navigation
[0] Message Index
[*] Previous page