{"action":"created","issue":{"url":"https://api.github.com/repos/copperhead/bugtracker/issues/280","repository_url":"https://api.github.com/repos/copperhead/bugtracker","labels_url":"https://api.github.com/repos/copperhead/bugtracker/issues/280/labels{/name}","comments_url":"https://api.github.com/repos/copperhead/bugtracker/issues/280/comments","events_url":"https://api.github.com/repos/copperhead/bugtracker/issues/280/events","html_url":"https://github.com/copperhead/bugtracker/issues/280","id":157333969,"number":280,"title":"password to access recovery","user":{"login":"subproc","id":18900406,"avatar_url":"https://avatars.githubusercontent.com/u/18900406?v=3","gravatar_id":"","url":"https://api.github.com/users/subproc","html_url":"https://github.com/subproc","followers_url":"https://api.github.com/users/subproc/followers","following_url":"https://api.github.com/users/subproc/following{/other_user}","gists_url":"https://api.github.com/users/subproc/gists{/gist_id}","starred_url":"https://api.github.com/users/subproc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/subproc/subscriptions","organizations_url":"https://api.github.com/users/subproc/orgs","repos_url":"https://api.github.com/users/subproc/repos","events_url":"https://api.github.com/users/subproc/events{/privacy}","received_events_url":"https://api.github.com/users/subproc/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/copperhead/bugtracker/labels/enhancement","name":"enhancement","color":"84b6eb"},{"url":"https://api.github.com/repos/copperhead/bugtracker/labels/priority-low","name":"priority-low","color":"d4c5f9"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2016-05-28T11:17:39Z","updated_at":"2016-06-14T06:19:27Z","closed_at":null,"body":"could be a security feature having a password (or pin or fingerprint,...) to access the recovery? 'cause now everyone can start the phone in recovery an try to hack it...or not?  "},"comment":{"url":"https://api.github.com/repos/copperhead/bugtracker/issues/comments/225789833","html_url":"https://github.com/copperhead/bugtracker/issues/280#issuecomment-225789833","issue_url":"https://api.github.com/repos/copperhead/bugtracker/issues/280","id":225789833,"user":{"login":"thestinger","id":1505226,"avatar_url":"https://avatars.githubusercontent.com/u/1505226?v=3","gravatar_id":"","url":"https://api.github.com/users/thestinger","html_url":"https://github.com/thestinger","followers_url":"https://api.github.com/users/thestinger/followers","following_url":"https://api.github.com/users/thestinger/following{/other_user}","gists_url":"https://api.github.com/users/thestinger/gists{/gist_id}","starred_url":"https://api.github.com/users/thestinger/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/thestinger/subscriptions","organizations_url":"https://api.github.com/users/thestinger/orgs","repos_url":"https://api.github.com/users/thestinger/repos","events_url":"https://api.github.com/users/thestinger/events{/privacy}","received_events_url":"https://api.github.com/users/thestinger/received_events","type":"User","site_admin":false},"created_at":"2016-06-14T06:19:27Z","updated_at":"2016-06-14T06:19:27Z","body":"If OEM unlocking is disabled from within the OS, yes. Otherwise the bootloader can be unlocked, and unlocking wipes the data. OEM unlocking would be useless without removing the wipe option from recovery since you could just wipe, boot the OS and enable OEM unlocking.\r\n\r\nWe still have the power to wipe it via a properly signed sideloaded package but that isn't exposed in the recovery. A user building and signing their own OS would have that power instead."}}
{"actor":{"display_login":"thestinger"}}