My grandfathered $140/month mobile plan has 14GB of data; 320MB is 70% of a day's bandwidth, or 2% of the month's.
If I wanted to add another GB I could accrue $100 in overages ($0.10/MB), or pay another $25/month. But Bell will charge for another month in advance if you change the current month's plan.
Strangely enough it was only $5/month to up it from 13GB to 14GB :<
All this despite being able to download at 7MB/s; I could blow my cap in half an hour, and another half hour would cost $1,400 if I didn't up the plan.
Edit: I use my cellphone's data heavily, but 20, 40, 50GB cable internet caps are common with a lot of people not understanding what that means for streaming video / downloading pictures.
I think it's somewhat frequent to have app submissions denied, but I haven't heard of Apple banning future submissions in the same way that I hear of Google permabanning developers.
I agree with Android it's slightly different because side loading is at least possible, but I doubt many people are going to find your widget if it's not on the play store.
He talks about it very briefly at the end, but basically says it doesn't pass Occam's Razor: there are better ways to implement the hack which can't just be detected with visual inspection.
Honestly it feels like splitting hairs, unless I'm misunderstanding something.
What is there to gain "cracking" the TPM itself, if you can get the keys fine by sniffing?
Apple's Secure Enclaves aren't vulnerable to sniffing, as the AES keys used for encryption live only in silicon, with access to use them granted to the Enclave.
The keys never exist in a software-readable form, even to the coveted Enclave firmware. Do TPMs offer this functionality, and Bitlocker needs to take advantage of it? Or do TPMs just not protect their keys against physical access?
MD5 and SHA are specifically designed to be fast to compute, they shouldn’t be used for passphrases.
Figured I’d bring it up in case there’s still PHP floating around with the once-typical practice of MySQL + MD5.