2 ms·
> You won't have fetched your key properly, but the Mega client automatically re-fetches the key when that happens. Is that something it could hypothetically d
by im3w1l 4y ago
> You won't have fetched your key properly, but the Mega client automatically re-fetches the key when that happens.
Is that something it could hypothetically do, or something that the current code does? In the latter case, is there any legitimate reason for doing that? And this would be detectable right, maybe not by a casual observer, but by a security researcher?
- tptacek 4y agoHow would you know? The whole point of the cryptosystem is you can't assume what the server code is doing.
- im3w1l 4y agoWell you said the client refetches the key, so that sounds like a network request you could observe.
- tptacek 4y agoSure; you could also look for all-zero SIDs. That relies on you knowing about this attack a priori, and if you know about it you can just not have the vulnerability.
- im3w1l 4y agoYeah, I was just trying to evaluate the risk that >Mega could have run this attack over long periods of time, in parallel for all its users; without anybody catching on. In light of our discussion, I don't think it's too likely.
- tptacek 4y agoNo, I don't agree at all. There is literally new science in this paper; the idea that random "security researchers" looking at benign-looking crypto code and monitoring all the connections their clients made (a thing nobody does) would ever have caught this is not plausible.