Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Accidental Google Pixel Lock Screen Bypass

bugs.xdavidhu.me

Post reply on HN
Print view View original

241–250 of 475 posts

Re: Accidental Google Pixel Lock Screen Bypass

#241

Post by ZiiS »

Gasp0de wrote: post #224
bawolff wrote: post #149

Earlier quoted context omitted.

Do you mean each new person should get a new bounty, or all reporters should split the bounty? The latter does not really incentivize much, but the former incentivizes reporters to collude with other reporters (i.e. you find a bug, tell your 40 friends to report the same bug, you get a kickback from all your friends who also reported it. $$$$).

The latter does incentivize everyone who stumbles across the bug to not disclose it. At the same time, it's sad for the original researcher whose bounty gets smaller with every new person stumbling across it.

It dose imply that finding it was easier then ones where you are the only reporter; partially justifying lower rewards.

Re: Accidental Google Pixel Lock Screen Bypass

#243

Post by ZiiS »

PragmaticPulp wrote: post #154
ZiiS wrote: post #133

Earlier quoted context omitted.

Everyone who reports a undisclosed bug should get a share of the bounty; this incentivizes them to stick to the embargo. If too many people are reporting the bug before you fix it then you have other problems. I also start to feel that at Google's scale bounties this serious should start doubling every month.

> Everyone who reports an undisclosed bug should get a share of the bounty; this incentivizes them to stick to the embargo. Having worked with but bounty programs, I can guarantee this would be abused to no end. Reporters would enlist their friends and family to submit as many duplicate reports as possible. There are a lot of good security researchers out there doing work in public, but bug bounty programs also get f…

I mean you all share the fixed bounty amount. You could only game the system if you expected other people had already found the bug. However this would be risky as it is fairly easy to detect and penalize. The common case is still you only get one reporter per bug.

Re: Accidental Google Pixel Lock Screen Bypass

#244

Post by Edman274 »

I went to buy a phone maybe two months ago. Before I had my current Google Pixel 6, I used a OnePlus 3T for six years, and even then I only stopped because I sat in a hot tub with it on. At the T-Mobile store, I announced to the salesman that I would be back to buy a Pixel 6 when they had it in stock, and a man pulled me aside and privately asked me why I wanted to buy a Pixel.

He explained to me that he was actually working in the hardware division at Google and that the team that he was managing was responsible for some parts of the Pixel's design. But he added that he had never actually talked with anyone out "in the wild" who owned a Pixel or made a positive attempt to buy one. He went on to explain that most of his team didn't use a Pixel either - they were all pretty much using iPhones, but some were even using Samsung devices.

I understand that this was someone from the hardware team and it doesn't necessarily reflect on the people who work on the Android OS, but I feel silly for not having taken what he said into consideration when I finally bought a phone. If the people working on a device don't even want to use it themselves and can't figure out a compelling reason for anyone else to use it, shouldn't that have been a strong signal to me that I shouldn't have selected it? But I did, and I've been regretting it since. Great camera though.

Re: Accidental Google Pixel Lock Screen Bypass

#246

Post by Anderkent »

Edman274 wrote: post #244

I went to buy a phone maybe two months ago. Before I had my current Google Pixel 6, I used a OnePlus 3T for six years, and even then I only stopped because I sat in a hot tub with it on. At the T-Mobile store, I announced to the salesman that I would be back to buy a Pixel 6 when they had it in stock, and a man pulled me aside and privately asked me why I wanted to buy a Pixel. He explained to me that he was actually…

roll to disbelieve. i think someone was pulling your leg

especially the bit with samsung devices, i've had the misfortune of setting up a samsung phone for a family member and the amount of crap on those is just unbelievable

Re: Accidental Google Pixel Lock Screen Bypass

#248

Post by rippercushions »

Edman274 wrote: post #244

I went to buy a phone maybe two months ago. Before I had my current Google Pixel 6, I used a OnePlus 3T for six years, and even then I only stopped because I sat in a hot tub with it on. At the T-Mobile store, I announced to the salesman that I would be back to buy a Pixel 6 when they had it in stock, and a man pulled me aside and privately asked me why I wanted to buy a Pixel. He explained to me that he was actually…

Out of curiosity, why have you been regretting it? I've been using Pixels for quite a while now and generally been quite happy.

Re: Accidental Google Pixel Lock Screen Bypass

#249

Post by Gasp0de »

endisneigh wrote: post #42
ApolloFortyNine wrote: post #30

Earlier quoted context omitted.

Who knows how many bugs live in iOS as well. Security through obscurity (iOS is closed source) isn't usually considered that great a strategy. Besides the whole "can't install user software" issue.

The number of bugs is not the issue. The issue is that apple supports their devices longer than all android vendors. Bugs are inevitable and so the difference is support duration and speed.

Really, how long?

Re: Accidental Google Pixel Lock Screen Bypass

#250

Post by julianlam »

Edman274 wrote: post #244

I went to buy a phone maybe two months ago. Before I had my current Google Pixel 6, I used a OnePlus 3T for six years, and even then I only stopped because I sat in a hot tub with it on. At the T-Mobile store, I announced to the salesman that I would be back to buy a Pixel 6 when they had it in stock, and a man pulled me aside and privately asked me why I wanted to buy a Pixel. He explained to me that he was actually…

Did this self-reported hardware engineer from Google tell you WHY his colleagues don't use a Pixel?

You could have just as likely been listening to hot air from a random individual. Perhaps an Apple store employee with an axe to grind.

Post reply on HN