Leaving Spellcheck Enabled Is a Privacy Risk (2016)
github.com
github.com
The developer in me thinks that this is because nobody at Google cares about the experience if the user chooses incrementally slightly more privacy, and so it simply gets no attention.
In the spirit of trying to do constructive discussion, the original post references the long dead Signal Chrome app. The new desktop garbage they push is a Node.js app called Signal Desktop. They use native spellchecking provided by Node and Hunspell (even on Windows, which could use native windows API available for 8 and newer and which probably is privacy violating)
To the best of my knowledge, Hunspell is privacy conscious software.
EDIT: Additional context, https://github.com/electron-userland/electron-spellchecker also confirms it only uses Hunspell on windows.
Is repackaging/injecting hard to do?
Thanks!
[0] https://andydavies.me/blog/2019/12/12/capturing-and-decrypti...
That being said I don't think it's nearly as common for certificate pinning to be present as people think- in fact it was deprecated in 2017 because it caused so many problems. Instead things like HSTS and transparency logs are used to prevent damage from malicious issuance of certificates, and organizations can typically override things with their own CA.
If your software is pinned to a specific certificate (even if that certificate is a root CA) your software won't work in many corporate environments. One of the exact reasons mentioned- medical data- is a big driver in this. My company has APIs used by medical companies, and they have to whitelist our service in their firewalls because many of them MITM all traffic to ensure that PHI isn't sent out over an unapproved service by mistake.
Still kinda salty that pinning was deprecated from HTTPS. It wasn't perfect (accidental/malicious pinning was far too easy seeing how it was merely controlled by an HTTP header), but the current alternatives (Certificate Transparency, CAA DNS records) aren't an adequate replacement. Sure Certificate Transparency helps to detect a misused certificate, but it doesn't actively prevent it from being used, and CAA requires that the CA isn't "lying" about the header through a "bug" or otherwise.
That and iCloud Backup are the first two things I disable on a vanilla iOS.
https://support.google.com/googleone/answer/9149304?co=GENIE...
As far as I know, appleid's have some kind of password/authentication system that could be used to encrypt backups.
It also says you use Android messenger which hooks up to Google's services.
The text messages have to be stored somewhere.
What gets saved by Android
The following data is backed up in your Android settings. You don't need to turn on Google One's backup to save this data.
App data
Call history
Contacts
Settings
SMS messages
Note, "by Android", not "on Android" as you claim.Not if you don't have iMessage enabled in iCloud settings.
Apple has, of course, denied this:
“We have never heard of PRISM,” said Apple spokesperson Steve Dowling in a statement. “We do not provide any government agency with direct access to our servers, and any government agency requesting customer data must get a court order.”
Shortly thereafter, the heads of many of the affected companies met with Obama at the white house to coordinate their next steps at counteracting the damage. The initial cover story was that they were meeting to discuss the healthcare.gov disaster, but it turned out that the meeting was actually about the NSA's comprehensive illegal spying programs being disclosed.
https://www.nytimes.com/2013/12/18/us/politics/as-tech-indus...
Reuters reported in January of 2020 that an ex-Apple employee told them that Apple Legal scrapped a 2018-2020 project to do clientside end-to-end encryption of the iCloud device backups (which would render this collection useless) as a result of pressure from the US government.
"That person told Reuters the company did not want to risk being attacked by public officials for protecting criminals, sued for moving previously accessible data out of reach of government agencies or used as an excuse for new legislation against encryption."
https://www.reuters.com/article/us-apple-fbi-icloud-exclusiv...
Non-e2e-encrypted iCloud Backups are on by default for every single iOS device if it is set up with an Apple ID.
Please do not believe the Apple marketing narrative about individual privacy.
It seems like you're aware that the FISA court just rubber stamps everything, so resultantly it might as well just not exist because it's simply a farce to make it seem legitimate by invoking the term "court". You're right in pointing out that a second FISA "court" judge would not make any difference.
Ultimately though, even oversight would not solve the problem of the fact that they should just be getting warrants for doing police surveillance in the first place. The bar to getting a federal judge to sign off on any technical mumbo jumbo ("IP address this, ISP that") is hilariously bad/low and they amount pretty much to rubber stamps already. The mind reels when you think that they set up a special fake court simply to avoid that.
Also, misspelling is a profiling risk.
It detects what language the page is written in with an entirely client side model (which is why it's accuracy is poor).
Also, it's customary to add that notice on HN regardless of how timeless the content is.
What I mean is to that this same insecurity principle could apply to other situations.