3 ms·
I don't get it, can anyone elaborate on what they are talking about there?
by barbazoo 6y ago
I don't get it, can anyone elaborate on what they are talking about there?
- TheGeminon 6y agoThey are implying that future versions of Signal will drop random files on your phone that "may or may not" cause damage to Cellebrite systems. They are basically putting the threat out that if you use Cellebrite on Signal in the future, you might not get the data you expect, and at worst, it may corrupt the report/evidence. This also brings into question the chain of custody, as an untrusted device being imaged can alter reports of unrelated devices.
- franga2000 6y agoDamn, a chain of custody where the thing in evidence is also part of not only its own chain but also those of other evidence acquired afterwards? I can't imagine what kind of case law exists around that, but I'm sure it's hilarious!
- cosmie 6y ago> also those of other evidence acquired afterwards And prior extracts on the device.
- deleted 6y ago[deleted]
- elliekelly 6y agoWhich is what I don't really understand - it seems like Cellebrite could spin this in their favor so law enforcement would need to purchase a new kit for each device?
- rodgerd 6y agoSignal is going to start attacking third-party tools once it's installed on your phone. It's as though Theo decided that OpenSSH should respond to portscanners by trying to pwn the source systems.
- spoonjim 6y agoAnd why shouldn’t OpenSSH do that?
- rodgerd 6y agoBecause I have zero interest in running attack software.
- oh_sigh 6y agoNo, because that would be active retaliation. More realistically it is like dropping a file on your private file server DONT_RUN_THIS_BLOWS_UP_YOUR_COMPUTER.exe. You never run it, but maybe somebody exploits your file server, gets all your files, and automatically runs them? Oh well.
- PeterisP 6y agoIt really is like dropping a file on your private file server DONT_RUN_THIS_BLOWS_UP_YOUR_COMPUTER.exe - but contrary to your expectations, it's not "oh well", if you placed it there with the intent to trap someone who you expect to be looking at your computer, you may well be liable if their computer blows up, there's no significant difference from active retaliation - the consequences are there, the intent is there, the act is there, it's pretty much the same. Of course, if some criminal exploits your file server, they are not likely to press charges, but if it triggers on law enforcement who have a warrant to scan your fileserver, that's a different issue. You'd be just as liable as for physical boobytraps on your property, with pretty much the same reasoning.
- chordalkeyboard 6y ago> if you placed it there with the intent to trap someone who you expect to be looking at your computer, you may well be liable if their computer blows up Liable for what? You haven’t promised that the code is safe, and they chose to run it. > there's no significant difference from active retaliation There is a significant difference, in active retaliation you choose to attack someone elseks computer, with a trap file the attacker chooses to run files they have stolen from you. Big difference. > You'd be just as liable as for physical boobytraps on your property, with pretty much the same reasoning. The reasoning is different, lethal or injurious man traps are prohibited because you don’t respond to trespassing with lethal force and you don’t know who or what may trigger the trap. Man traps that lock the intruder in a room without injuring them are fine, and used in high security installations.