Differing passcode authentication with leading 0 |
||||||
Issue descriptionWhen pairing with devices that require passcode authentication, sometimes only 5 digits are sent. Fluoride devices (like Android Auto/Pixel phone) place a zero at the beginning while ChromeOS places a zero at the end. Though the codes look different, this is actually valid. Let's follow the same convention here.
,
Mar 1 2018
,
Mar 7 2018
,
Apr 10 2018
,
Apr 11 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/59d96a015305ce5b86b48008b103d0d78213f05f commit 59d96a015305ce5b86b48008b103d0d78213f05f Author: Sonny Sasaka <sonnysasaka@chromium.org> Date: Wed Apr 11 00:29:55 2018 bluetooth: Fix passkey string conversion Currently passkey is padded with trailing zeros if it's less than 6 digits. It should be padded with leading zeros instead. Bug: 817574 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: I3a27412c9c053141d28a6e7e7e609de28729ee20 Reviewed-on: https://chromium-review.googlesource.com/1005616 Reviewed-by: Steven Bennetts <stevenjb@chromium.org> Commit-Queue: Sonny Sasaka <sonnysasaka@chromium.org> Cr-Commit-Position: refs/heads/master@{#549695} [modify] https://crrev.com/59d96a015305ce5b86b48008b103d0d78213f05f/ui/webui/resources/cr_components/chromeos/bluetooth_dialog.js
,
Apr 11 2018
,
Aug 24
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by rjahagir@chromium.org
, Mar 1 20181.3 MB
1.3 MB View Download