News for hackers. Stuff that matters.
Re:Signal on Android: Images sent to wrong contacts by hnarn on Sunday July 25, 2021 @02:59PM (#27951881)
Some details on how this assumption was made would be nice, but I think it's pretty obvious that any developer involved in a project can make a reasonable assumption of how rare a bug is depending on the technical details on what is required for the bug to happen. For example, if we say for the sake of argument that a hypothetical bug requires you to have more than ten contacts of the exact same name and these also need to share the same country and area code, one can make the assumption this use case is very rare without knowing the exact number of users that this applies to, just based on common sense regarding how the application is normally used.

edit: The linked github issue says:

> The TL;DR is that if someone had conversation trimming on, it could create a rare situation where a database ID was re-used in a way that could result in this behavior. It was very difficult to track down, with earlier phases involving getting additional logging into builds. Once we had some more information, it did in fact become our top priority, a fix was made, and we got it out as quickly and as safely as possible. The fix itself should make it so that database issues like the one that caused this bug can't happen again.

Re:Signal on Android: Images sent to wrong contacts by WesolyKubeczek on Sunday July 25, 2021 @04:02PM (#27952424)
> a hypothetical bug requires you to have more than ten contacts of the exact same name and these also need to share the same country and area code

Sounds like the village a part of my family tree comes from.

Re:Signal on Android: Images sent to wrong contacts by Griffinsauce on Sunday July 25, 2021 @05:26PM (#27953067)
> just based on common sense regarding how the application is normally used

Just based on assumptions of how the application is used.

"falsehoods programmers believe" comes to mind. The uniqueness of names in your example could be false in some (or many? No idea) cultures.

Re:Signal on Android: Images sent to wrong contacts by z3t4 on Sunday July 25, 2021 @03:35PM (#27952219)
> The fix itself should make it so that database issues like the one that caused this bug can't happen again.

I've said that a few times, and been wrong about it. :D

I don't know what they mean by "where a database ID was re-used", but I guess it had to do with caching, and cache invalidation is one of the hardest part in computer programming.

Re:Signal on Android: Images sent to wrong contacts by dane-pgp on Sunday July 25, 2021 @10:06PM (#27954774)
> cache invalidation is one of the hardest part in computer programming.

Yes, famously it is one of the two hardest parts of computer programming, the other being naming things, and off-by-one errors.

Re:Signal on Android: Images sent to wrong contacts by varispeed on Sunday July 25, 2021 @04:28PM (#27952639)
Why would anyone think that re-use of ID was a good idea?
Re:Signal on Android: Images sent to wrong contacts by hnarn on Sunday July 25, 2021 @04:32PM (#27952665)
I'm not defending the practice of re-using a database ID, but it's absolutely something that can happen (or change) as an oversight rather than an active choice from the developer.
Re:Signal on Android: Images sent to wrong contacts by doctor_eval on Sunday July 25, 2021 @06:44PM (#27953640)
Perhaps that’s why it was a bug?
Re:Signal on Android: Images sent to wrong contacts by jakequade on Monday July 26, 2021 @12:26AM (#27955661)
> it's pretty obvious that any developer involved in a project can make a reasonable assumption of how rare a bug is

... is it? The fact that a bug exists means there's a logic gap. You can try and patch it with theory, but that's just adding assumption to a scenario created from broken assumptions. Also, the job of telemetry in incident reporting isn't to be vague - its to add precision.

Re:Signal on Android: Images sent to wrong contacts by lmeyerov on Monday July 26, 2021 @01:04AM (#27955893)
There's probably a ratio of bug-report-to-occurrences that they're used to for difference kinds of bugs. Ex: If user-visible security bugs have good report rates, say 100-1000 leaks per 1 report, and 10 reports, then 1K-10K incidents. This is harder in b2b, but in b2c, PM's should have a feel for it..
Re:Signal on Android: Images sent to wrong contacts by conradev on Monday July 26, 2021 @01:37AM (#27956044)
You’d be surprised how difficult it is to estimate the frequency that someone sees a bug. The only way to have a “feel for it” is to base it on… other data.

Say there is a bug that happens in the photo taking flow – you’d need to know how often people take photos in Signal. You’d think you could spitball something for that, but it is actually really hard. But if you log how often photos are taken, then that is a great starting point.

But further, lower level logic errors like this, especially ones involving race conditions, are even harder to pin down. That is why on iOS you can log “faults” which are non-fatal but very not-expected events:

https://developer.apple.com/documentation/os/logger/3551617-...

They generate reports with stack traces that you can use to a) judge the prevalence of an issue and b) see where it originated

Re:Signal on Android: Images sent to wrong contacts by NullPrefix on Sunday July 25, 2021 @03:15PM (#27952037)
>for the sake of argument that a hypothetical bug requires you to have more than ten contacts of the exact same name and these also need to share the same country and area code

This is only rare if you have a small social circle. My circle has multiple first name-collisions of at least 5 participants, but my circle is not very big and the area code is also quite small.

Some countries do not use area codes for mobile phone numbers, which are used for Signal, meaning country code is the only area limiting factor.

Re:Signal on Android: Images sent to wrong contacts by hutrdvnj on Sunday July 25, 2021 @03:34PM (#27952208)
Well he just wanted to make an example. One could also construct an example, where the bug only occurs for people with a rare sequence of unicode symbols (e.g. U+2600 U+2601 U+2602) in their username and have a specific date (e.g. 05.04.1920) as their birthday.
Re:Signal on Android: Images sent to wrong contacts by NullPrefix on Sunday July 25, 2021 @04:06PM (#27952455)
Your argument depends on Signal implementing username support, because we do not support unicode in phone numbers.
Re:Signal on Android: Images sent to wrong contacts by hutrdvnj on Sunday July 25, 2021 @04:11PM (#27952499)
My argument depends on an alternate universe in which signal supports it, everything else being equal, because why not.
Re:Signal on Android: Images sent to wrong contacts by NullPrefix on Sunday July 25, 2021 @04:20PM (#27952571)
Does that alternate universe support phone numbers with unicode characters too?
Re:Signal on Android: Images sent to wrong contacts by ChrisKnott on Sunday July 25, 2021 @04:49PM (#27952794)
You are arguing against a hypothetical situation of your opponent's creation. This is like when Ross tried to beat Chandler at Cups
Re:Signal on Android: Images sent to wrong contacts by hutrdvnj on Sunday July 25, 2021 @04:57PM (#27952846)
I go to bed now and dream of a universe in which NullPrefix is Ross and continues to argue endlessly.
Re:Signal on Android: Images sent to wrong contacts by NullPrefix on Sunday July 25, 2021 @06:19PM (#27953470)
I'll argue with anyone about anything. For free.
Re:Signal on Android: Images sent to wrong contacts by webmaven on Monday July 26, 2021 @04:54AM (#27957192)
> I'll argue with anyone about anything. For free.

No, you won't.

Re:Signal on Android: Images sent to wrong contacts by NullPrefix on Monday July 26, 2021 @07:04AM (#27957998)
Obviously that was a hyperbolic statement.
Re:Signal on Android: Images sent to wrong contacts by webmaven on Monday August 02, 2021 @08:51AM (#28035839)
Don't argue with me!
Re:Signal on Android: Images sent to wrong contacts by NullPrefix on Sunday July 25, 2021 @06:30PM (#27953560)
I am curious how different that alternative universe needs to be for my argument to be invalid.
Re:Signal on Android: Images sent to wrong contacts by desine on Sunday July 25, 2021 @07:09PM (#27953789)
It's not that your argument was incorrect. It's that it is tangential to the parent comment. hnarn was not making the point of something being rare, they were demonstrating that a developer can estimate the rarity based on the conditions that trigger it. The rarity itself is no matter.

Arguing over small semantic or circumstantial differences is often considered impolite

Re:Signal on Android: Images sent to wrong contacts by johnisgood on Sunday July 25, 2021 @05:54PM (#27953284)
It is a hypothetical scenario for the purpose of an example. It could have been literally anything, the point is for it to be rare.
Re:Signal on Android: Images sent to wrong contacts by NullPrefix on Sunday July 25, 2021 @06:20PM (#27953478)
Yes, but the fact that scenario is hypothetical doesn't counter my argument that whatever the developer thinks is rare is actually rare.
Re:Signal on Android: Images sent to wrong contacts by johnisgood on Monday July 26, 2021 @07:31PM (#27966812)
I do not know why I keep replying to this... but regardless, here it comes: your counter-argument is irrelevant! It does not require any counter-argument, because it is hypothetical! He could have said anything else that is rare, something that you think is rare, too. Just assume he said something that you think is rare as well. It is a hypothetical scenario, so you can do that; in fact: you should have done that, because all that is important is that it is rare, whatever that is. Again, argument over what he said is rare or not is not needed. Just assume it is rare, or assume he said something you think is rare.

I hope this gets the point across. Yes, maybe what he said is not rare, but that is besides the point.

Re:Signal on Android: Images sent to wrong contacts by desine on Sunday July 25, 2021 @03:26PM (#27952129)
>for the sake of argument
Re:Signal on Android: Images sent to wrong contacts by NullPrefix on Sunday July 25, 2021 @04:03PM (#27952435)
Yes.

And for the sake of the same argument I made a counter argument, stating that some initially believed to be rare circumstances are actually not that rare.

Re:Signal on Android: Images sent to wrong contacts by hnarn on Sunday July 25, 2021 @04:22PM (#27952583)
"For the sake of argument" does not mean "I invite you to debate this", it means the exact opposite: "let's assume this is correct/we agree/etc. for a while and debate what comes after". So in this case you are doing the exact opposite of what the phrase "for the sake of argument" is requesting.

https://idioms.thefreedictionary.com/for+the+sake+of+argumen...

> I know you want to go to Stanford, but just for the sake of argument, let's talk about what some of the other schools you got into have to offer.

This does not mean "I invite you to make a counter-argument as to why no other schools than Stanford are worth going to".

Re:Signal on Android: Images sent to wrong contacts by qu4z-2 on Sunday July 25, 2021 @04:58PM (#27952853)
It sounds to me like NullPrefix accepted the hypothetical bug, for the sake of the argument, and then addressed the rarity assumptions made about that bug. "For the sake of argument" doesn't mean "No debating" it means "Let's assume some thing x is taken as a given and go from there."
Re:Signal on Android: Images sent to wrong contacts by hnarn on Sunday July 25, 2021 @05:02PM (#27952885)
The whole point was that "given this assumed rare bug, one can know it's pretty rare". Whether the example is actually rare enough is completely beside the point. If it's not rare enough for you, replace it. The argument comes next: given a rare bug, a developer can make an assumption of how rare it is. Debating the example of rareness is splitting hairs.
[dead]
Re:Signal on Android: Images sent to wrong contacts by hnarn on Sunday July 25, 2021 @04:47PM (#27952784)
English is my second language.
Re:Signal on Android: Images sent to wrong contacts by johnisgood on Sunday July 25, 2021 @05:57PM (#27953298)
There is no argument, and it did not require a counter-argument, because that is not the point. He could have used literally anything else, it just has to be rare.