News for hackers. Stuff that matters.
Re:Facebook probably has your phone number, even if you neve... by autoexec on Tuesday November 01, 2022 @05:16PM (#33427587)
> "You can ask us to confirm whether we have your phone number or email address," the firm states. "If we do, you can request that we delete it from our address book database. To prevent it from being uploaded to this database again through someone's address book, we need to keep a copy in our block list."

I wouldn't doubt if they remove your information from their "address book database" and add it to one or more others where they keep it forever. There's zero oversight, and zero accountability. It makes no sense at all to just assume that facebook will do anything they aren't forced to when not doing that thing could make them money. Facebook doesn't care about you, your privacy, or even the law. Facebook cares only about facebook.

Re:Facebook probably has your phone number, even if you neve... by krono on Tuesday November 01, 2022 @06:24PM (#33428475)
Not too dissimilar from Google Analytics official global opt-out browser extension. It injects a consistent/unchanging item into the global window scope of every single page you visit.

https://tools.google.com/dlpage/gaoptout/index.html

License prohibits sharing its code so I won't - setting a good example for our artificially intelligent friends :)

Re:Facebook probably has your phone number, even if you neve... by cyberphobe on Tuesday November 01, 2022 @06:34PM (#33428597)
I'm sure are artificially intelligent friends give precisely zero fucks what you do and will steal your shit with impunity. If you do crime on a large enough scale, it's called innovation.
Re:Facebook probably has your phone number, even if you neve... by dataflow on Tuesday November 01, 2022 @08:05PM (#33429668)
> It injects a consistent/unchanging item into the global window scope of every single page you visit

Confused, are you saying they inject a unique ID or something? Do you have an example of what they insert?

Re:Facebook probably has your phone number, even if you neve... by easrng on Tuesday November 01, 2022 @09:50PM (#33430521)
Re:Facebook probably has your phone number, even if you neve... by dataflow on Tuesday November 01, 2022 @09:52PM (#33430542)
Would you mind explaining what's wrong with that code? I'm especially confused how it's similar to Facebook saving purportedly your info when you opt for erasure.
Re:Facebook probably has your phone number, even if you neve... by easrng on Tuesday November 01, 2022 @11:04PM (#33430985)
There's nothing wrong with that code, though it is a potential fingerprinting vector.
Re:Facebook probably has your phone number, even if you neve... by easrng on Tuesday November 01, 2022 @09:49PM (#33430515)
Fuck the license, here's the code it injects:

  /* Copyright 2010 Google Inc. All Rights Reserved. http://tools.google.com/dlpage/gaoptout/intl/en/eula_text.html */ (function () {
    var a = document.createElement("script");
    a.type = "text/javascript";
    a.innerText =
      'window["_gaUserPrefs"] = { ioo : function() { return true; } }';
    document.documentElement.insertBefore(a, document.documentElement.firstChild);
  })();
Re:Facebook probably has your phone number, even if you neve... by marcosdumay on Tuesday November 01, 2022 @10:58PM (#33430951)
Looks like a really convoluted way to add a "tracking disabled" mark. But I don't see any more than a bit of information on it.
Re:Facebook probably has your phone number, even if you neve... by MonkeyClub on Wednesday November 02, 2022 @08:05AM (#33434359)
> Fuck the license

Exactly. If you don’t want it shared, then don’t inject it in the first place.

Re:Facebook probably has your phone number, even if you neve... by 1vuio0pswjnm7 on Tuesday November 01, 2022 @10:05PM (#33430622)
"License prohibits sharing its code so I won't - setting a good example for our artifically intelligent friends :)"

What if the person sharing it is not a licensee. License terms would only bind licensees, assuming the purported licensee has properly assented to the license terms.

Re:Facebook probably has your phone number, even if you neve... by _hyn3 on Tuesday November 01, 2022 @11:23PM (#33431104)
In which case that person would have no license to use it at all.
Re:Facebook probably has your phone number, even if you neve... by dylan604 on Wednesday November 02, 2022 @12:25AM (#33431422)
posting code to a forum isn't using it though since the code isn't executed
Re:Facebook probably has your phone number, even if you neve... by EMIRELADERO on Wednesday November 02, 2022 @12:44AM (#33431528)
It's actually the other way around. Copyright doesn't regulate use, but it does regulate distribution. Posting it without permission is a copyright violation.
Re:Facebook probably has your phone number, even if you neve... by dylan604 on Wednesday November 02, 2022 @12:50AM (#33431544)
change a couple of var names, and you're good to go

also, fair use would definitely apply in this case as it's not the entire work and is a small sample. nothing different than playing a small clip/scene from a movie in a review write up. and commentary is definitely being had around said snippet

Re:Facebook probably has your phone number, even if you neve... by edf13 on Wednesday November 02, 2022 @02:28AM (#33431996)
Exactly - Google themselves have been making use of fair use for a while with news exerts…
Re:Facebook probably has your phone number, even if you neve... by dylan604 on Wednesday November 02, 2022 @03:46AM (#33432444)
There's also the pages of the books they scanned and made available was pretty egregious. The snippets of webpages they display in search results so that users never actually have to click through to the actual website so they can get those precious impressions.

Just Googs being dicks to everyone, essentially

Re:Facebook probably has your phone number, even if you neve... by ritzaco on Tuesday November 01, 2022 @05:43PM (#33427961)
Of course, it's not a technical problem. They could keep a hash instead of a copy. But I'm sure people who find the 'hidden tool' and request to have their information removed are interested in specific products, so a list of these people is very valuable to train machine learning models on..
Re:Facebook probably has your phone number, even if you neve... by kadoban on Tuesday November 01, 2022 @05:47PM (#33428019)
Hashes of phone numbers is unfortunately not actually useful in almost any circumstance. You can trivially reverse them by iterating through every phone number and computing the hash.

Hashes of emails is not quite as useless, but not far off (consider 90+% of emails are at like ~3 domains, and also that lists of vaguely ~valid email addresses aren't hard to get).

Re:Facebook probably has your phone number, even if you neve... by gerdesj on Tuesday November 01, 2022 @06:40PM (#33428690)
"You can trivially reverse them by iterating through every phone number and computing the hash."

Well yes and no. What exactly is your understanding of a phone number 8)

Not everyone is blessed with the NANP. I'm a Brit and we have an eye wateringly complicated nonsense of a numbering plan and our's isn't the worst.

What do you hash? Perhaps the standardised international representation or one of them (no that is not a joke - telephony is weird). For a laugh you could try one of the many colloquialisms. For example a UK number might be 00441395112233 or 441395112233 or +44 (0)1395 112233 - the final part might be displayed as 112 233 or 112-233. Imagine if the database works by operating on all numbers in locally correct colloquial mode and hashes that!

Now let's really get silly: There are hashes that are nasty to compute but easy to check and vv. We'll use whatever is indicated.

Anyway this is all a very well researched problem, there is no need for silly games: passwords.

Re:Facebook probably has your phone number, even if you neve... by kadoban on Tuesday November 01, 2022 @06:44PM (#33428733)
Phone numbers get complicated, yeah, but US numbers are pretty trivial (and so are they in several other places, and even for UK it's just more annoying, not really computationally harder).

So at _best_ the security analysis is: "okay, all US phone numbers and a bunch from other places might as well be in cleartext", which is already broken enough that it's basically useless.

Re:Facebook probably has your phone number, even if you neve... by groffee on Tuesday November 01, 2022 @06:49PM (#33428794)
So normalise the data first? Your comment literally makes no sense at all.
Re:Facebook probably has your phone number, even if you neve... by ajsnigrutin on Tuesday November 01, 2022 @09:14PM (#33430235)
This data is normalized before it's even saved to the database.

You cannot send an sms to "+44 (0)1395 112-233", so they remove the stuff in parenthesis, the dashes, spaces, etc. first, and then store.

Re:Facebook probably has your phone number, even if you neve... by qxmat on Tuesday November 01, 2022 @06:25PM (#33428484)
Slow hash function + salt would solve this.. e.g. you'd be lucky to do more than 10 hashes a minute with bcrypt and 20 salt rounds.
Re:Facebook probably has your phone number, even if you neve... by m4jor on Tuesday November 01, 2022 @06:41PM (#33428698)
Yeah but with hashcat supporting cracking with multiple GPUs, even bcrypts can be cracked quickly now. There are also a ton of cloud cracking services like GPUHash.me and entire cracking forums where ppl crowdsource and help out like HashKiller.
Re:Facebook probably has your phone number, even if you neve... by kadoban on Tuesday November 01, 2022 @06:55PM (#33428863)
You can try that, but it's really difficult to tune so it's useful. The amount of time the server has to waste computing hashes is too close to the amount of time an attacker has to waste to break at least some of them.

It's just not hard enough to guess a potentially valid phone number. With passwords, hashing only helps because the probability of a valid password is _very_ low, and because you don't need to look up a password, only check if it's the right one for joeblow (so you can salt them individually).

Re:Facebook probably has your phone number, even if you neve... by popcalc on Tuesday November 01, 2022 @06:03PM (#33428213)
This is the same reason hashing a SSN is purely security through obscurity. Anyone with a couple GB of space to spare for a text file can easily perform a reverse lookup.

https://gist.github.com/stouset/4322307

Re:Facebook probably has your phone number, even if you neve... by lotsofpulp on Tuesday November 01, 2022 @09:21PM (#33430290)
This is why any business that uses SSN as authentication should be liable for any losses that result from fraudulent usage of the SSN, as opposed to the SSN’s owner being liable.
Re:Facebook probably has your phone number, even if you neve... by addingadimensio on Tuesday November 01, 2022 @06:15PM (#33428380)
Hash and salt
Re:Facebook probably has your phone number, even if you neve... by kadoban on Tuesday November 01, 2022 @06:41PM (#33428695)
If you salt, then either you can't lookup a number, or you've only changed the problem to: iterate over all the possible phone numbers, _add the salt_ and hash them. No big difference.
Re:Facebook probably has your phone number, even if you neve... by galeaspablo on Tuesday November 01, 2022 @06:24PM (#33428481)
How could I match an incoming unhashed value to an existing salted hash?
Re:Facebook probably has your phone number, even if you neve... by m4jor on Tuesday November 01, 2022 @06:40PM (#33428684)
hashcat
Re:Facebook probably has your phone number, even if you neve... by ohbtvz on Tuesday November 01, 2022 @06:24PM (#33428482)
There are only about 3 billion valid US phone numbers. How many hashes can your GPU compute per second?
Re:Facebook probably has your phone number, even if you neve... by m4jor on Tuesday November 01, 2022 @06:39PM (#33428678)
Most people crack with multiple GPUs. For example, I have a 5 GPU (3080s) rig that I used for mining ETH but now can use to crack with hashcat. tl;dr crack fast af boiii.
Re:Facebook probably has your phone number, even if you neve... by parker_mountain on Tuesday November 01, 2022 @07:31PM (#33429286)
Back of the hand math, and some benchmarking, suggests that a consumer laptop GPU from about 2015 could bang it out in a month. And, that's being (extremely) pessimistic.

(Assuming a GPU takes .001s to do a sha3 hash, which is more than double the actual benchmarks).

I would estimate that a single, high end GPU from the last or current generation could probably chew through it in under a week.

Re:Facebook probably has your phone number, even if you neve... by DenisM on Tuesday November 01, 2022 @09:59PM (#33430588)
One can easily devise a hash function that a GPU can only compute once per second. Or per year, even, although that would be impractical.
Re:Facebook probably has your phone number, even if you neve... by nemothekid on Tuesday November 01, 2022 @07:13PM (#33429078)
The salt doesn't buy you anything, given that Facebook also knows the salt.
Re:Facebook probably has your phone number, even if you neve... by parker_mountain on Tuesday November 01, 2022 @07:27PM (#33429242)
While a secret salt is effective in the short term, it's an un-rotatable value. Which means, if the salt gets leaked, you are screwed (or rebuilding the entire table by brute forcing it, or adding another layer of salting - not great!).

For a company operating at Facebook's scale, with their kind of scrutiny around handling PII, this is unfortunately functionally useless.

For some data types where hashing isn't super effective, and where associative identifying information is attached (such as a user id), a more effective mechanism might be to encrypt the data with a strong random value appended, and decrypt to do the lookup. This would require a correctly provisioned HSM to do properly - the private key secrets should NEVER be exported.

While hashing seems like a good idea, it's actually particularly and deceptively tricky for these kinds of use cases.

Re:Facebook probably has your phone number, even if you neve... by lost_tourist on Tuesday November 01, 2022 @09:37PM (#33430435)
I would say it's better than doing nothing though.
Re:Facebook probably has your phone number, even if you neve... by parker_mountain on Thursday November 03, 2022 @08:25PM (#33460009)
It's complicated. Your local security engineer might be wringing their hands about this. Definitely an avoid at any cost kinda situation.
Re:Facebook probably has your phone number, even if you neve... by m463 on Tuesday November 01, 2022 @06:27PM (#33428520)
I wonder what happens if someone blocks their phone number, then switches it.

Will the re-used number be blacklisted forever with a hash scheme?

Re:Facebook probably has your phone number, even if you neve... by robertlagrant on Wednesday November 02, 2022 @06:45AM (#33433763)
That's my thought as well. Maybe they should just stop using phone numbers for discovery purposes.
Re:Facebook probably has your phone number, even if you neve... by SanjayMehta on Tuesday November 01, 2022 @08:05PM (#33429667)
They used to backup to Blu-Ray, so there's that.

http://www.businessinsider.com/facebook-uses-10000-blu-rays-...

Re:Facebook probably has your phone number, even if you neve... by magic_hamster on Tuesday November 01, 2022 @08:26PM (#33429862)
They also seem to care about fighting windmills in VR.
Re:Facebook probably has your phone number, even if you neve... by jiveturkey on Tuesday November 01, 2022 @09:46PM (#33430493)
it's like cookies. to refuse cookies you "have to" accept a cookie saying you refuse the other cookies.

the difference between the "address book" and the "block list" is that one can be used for marketing/targeting purpose. the other one presumably is on the other side of a chinese wall (could easily be so under FTC condition) where FB can't use it for said purpose. this would generally serve the intended purpose of "removing" your phone number.

your other contacts that felt they should upload an address book in the first place may find surprise or random inconvenience that they can't upload your number.

Re:Facebook probably has your phone number, even if you neve... by 1vuio0pswjnm7 on Tuesday November 01, 2022 @10:15PM (#33430699)
Changes to the interpretation of Section 230 are coming.

Deperately-needed, long overdue "regulation" will come in the form of liability if mega-sized websites like Facebook choose to algorithmically curate and use other web users' content as a means of generating profits.

People who develop free, open source alternatives for communicating directly over the internet should be ready for a possible mass exodus away from using so-called social media websites for communication.

The Twitter mess is only going to make it more clear to everyone, including Supreme Court justices, that "social media" is a moral hazard, not a legitimate business model.

Re:Facebook probably has your phone number, even if you neve... by ls15 on Wednesday November 02, 2022 @12:56AM (#33431571)
> To prevent it from being uploaded to this database again through someone's address book, we need to keep a copy in our block list.

Don't they know hashing at facebook?

Re:Facebook probably has your phone number, even if you neve... by littlecranky67 on Wednesday November 02, 2022 @01:27AM (#33431712)
To be fair, hashing phone numbers is mostly pointless since the search space is too small.
Re:Facebook probably has your phone number, even if you neve... by marginalia_nu on Wednesday November 02, 2022 @04:51AM (#33432901)
> we need to keep a copy in our block list.

If only there was a function that was deterministic, but somehow incredibly difficult to invert, that would sure make a hash of this requirement to store things you're required not to store.

Re:Facebook probably has your phone number, even if you neve... by noja on Wednesday November 02, 2022 @05:03AM (#33433007)
Apple does this. It is even more frustrating! If you ever had two Apple accounts, and close one, you can _never_ add the e-mail from the deleted account as an alias to the remaining account.

You can imagine the headaches this causes.

Re:Facebook probably has your phone number, even if you neve... by hashhar on Wednesday November 02, 2022 @05:25AM (#33433168)
I ran into this myself. It's even more frustrating that they don't warn you about it upfront when closing the account (at least they didn't back when I ran into this).

I was hoping to start over with a fresh account and instead ended up having to create a new email alias in Outlook to use to create a new Apple account - luckily I used an alias the first time as well so the impact wasn't as bad.

Re:Facebook probably has your phone number, even if you neve... by noja on Wednesday November 02, 2022 @05:33AM (#33433239)
Apple support suggested I "simply change my e-mail address". Sure! I will just contact everyone I have ever known, and ask them to update it. Oh and every website I have ever created an account on! sigh
Re:Facebook probably has your phone number, even if you neve... by Tepix on Wednesday November 02, 2022 @05:55AM (#33433416)
Sure, there are hashing functions, but with a search space that is as small as a 10 digit phone number it is easy to create rainbow tables that covers them all.

Signal has spent some time thinking about this problem, see https://signal.org/blog/private-contact-discovery/

Re:Facebook probably has your phone number, even if you neve... by wuiheerfoj on Wednesday November 02, 2022 @06:02AM (#33433471)
Multiple hashing rounds or bcrypt would likely be a fine solution for this
Re:Facebook probably has your phone number, even if you neve... by eps on Wednesday November 02, 2022 @06:56AM (#33433852)
Pray tell the details.
Re:Facebook probably has your phone number, even if you neve... by MonkeyClub on Wednesday November 02, 2022 @08:02AM (#33434336)
Yeah I initially thought as GP, perhaps some salting, hence my comment above. But the only salt worth its salt (sorry, had to) would be the number itself. Otherwise, you’d need a database associating the number with its salt. And if you use the number itself as the salt, then rainbow tables it is.
Re:Facebook probably has your phone number, even if you neve... by Tepix on Wednesday November 02, 2022 @08:26AM (#33434604)
Even if you tweak your hashing algorithm to take 1 second on a fast CPU, you get 31 years of CPU time to search the entire space. That's simply not enough! And going beyond 1 second is probably also not practical.
Re:Facebook probably has your phone number, even if you neve... by patrec on Wednesday November 02, 2022 @06:01AM (#33433456)
Hash functions are only incredibly difficult to invert when the input domain is large, which is not the case with phone numbers. Even if you use a password hashing function that takes 1s to run (and if you need to frequently compare the hash, that's on the high side), you could practically invert the hash of an individual phone number. For this use case making it relatively expensive to obtain a single number in the clear would probably be good enough though.
Re:Facebook probably has your phone number, even if you neve... by robertlagrant on Wednesday November 02, 2022 @06:35AM (#33433700)
Salting exists for this reason.
Re:Facebook probably has your phone number, even if you neve... by ShowalkKama on Wednesday November 02, 2022 @06:49AM (#33433784)
even with salting it'd be trivial
Re:Facebook probably has your phone number, even if you neve... by eps on Wednesday November 02, 2022 @06:57AM (#33433865)
And how exactly would salting fit into matching plaintext phone numbers against a large blacklist?
Re:Facebook probably has your phone number, even if you neve... by Vinnl on Wednesday November 02, 2022 @07:04AM (#33433909)
How would that work if someone re-uploads your phone number? If it's not hashed with the same salt, then that wouldn't be blocked?
Re:Facebook probably has your phone number, even if you neve... by robertlagrant on Wednesday November 02, 2022 @08:48AM (#33434854)
Well, quite :) I don't see how the thing is supposed to work, given that people get other people's phone numbers when they change number. The only way to actually fix it is to stop uploading a user's contacts to their servers in the first place.
Re:Facebook probably has your phone number, even if you neve... by ilyt on Wednesday November 02, 2022 @06:16AM (#33433561)
Go and calculate how much time would it take to hash every 9-11 digit number...
Re:Facebook probably has your phone number, even if you neve... by BiteCode_dev on Wednesday November 02, 2022 @06:37AM (#33433714)
Salts are a thing for this very reason. And some hashes like scrypt can be parametrized to take time no matter what.

There is no rainbow table entry for 0123456789+=i=i_fy82dnuf720g%2+70)(k$0@*qsijyn9&19n@1r0-l4ee) with 10000 scrypt rounds.

We are not in 2005 anymore, and we have better tools than md5, or even sha1 to do the job.

Re:Facebook probably has your phone number, even if you neve... by eps on Wednesday November 02, 2022 @07:04AM (#33433906)
Salting won't work in this particular case. You need to match plaintext against a blacklist. Salt per entry is too expensive, salt per blacklist is exploitable.
Re:Facebook probably has your phone number, even if you neve... by BiteCode_dev on Wednesday November 02, 2022 @07:09AM (#33433931)
Were it be a small company, we would try sharding salts + increasing the number of rounds of scrypt or some mix with a bloom filter.

However, this is facebook. It's not too expensive for them.

Re:Facebook probably has your phone number, even if you neve... by compsciphd on Wednesday November 02, 2022 @07:33AM (#33434112)
how does a salt help?

a salt for a password is when we know the username and the salt so can combine the salt and provided password to compare against the generated hash value.

in this case all we know is the phone number, how does a salt help us look up a given phone number in a set of salted / hashes if we dont know what salt to combine it with?

Re:Facebook probably has your phone number, even if you neve... by BiteCode_dev on Wednesday November 02, 2022 @08:30AM (#33434649)
You shard the number into groups with a salt for each, until you reach a number of combinations that is computable for FB size on a check request, but way too long pre-generate. You can combine it with some bloom like filter to increase efficiency.
Re:Facebook probably has your phone number, even if you neve... by compsciphd on Wednesday November 02, 2022 @08:32AM (#33434682)
Can you more explain that as an example. I understand the words, but doesn't extend to me seeing the design of it.
Re:Facebook probably has your phone number, even if you neve... by KaiserPro on Wednesday November 02, 2022 @06:29AM (#33433663)
you are forgetting that this is not just a technical problem.

For GDPR you need to legally prove that you have taken reasonable steps to remove and keep out of your system, the data the user has requested. This means that you need to be able to legally prove you've got a system in place.

Keeping a hash is fine technically, but its a pain in the dick to defend in court, especially as its really simple to shower a jury/judge with FUD to make it look like its not a reasonable step.

Re:Facebook probably has your phone number, even if you neve... by MonkeyClub on Wednesday November 02, 2022 @07:51AM (#33434237)
Spot on, “need a copy for blocking purposes” just preys on public computer illiteracy.[1]

In the devil’s defense, the explanation was probably written by a computer illiterate person.

Then again, there may very well have been this one meeting, where a dev went “hold on, I got an idea to avoid storing the number!”, before being politely but briskly advised to stfu. Not impossible.

[1] littera : illiteracy :: numera : innumeracy :: digita : ildigitacy? Iddigitacy?

Re:Facebook probably has your phone number, even if you neve... by wooptoo on Wednesday November 02, 2022 @05:51AM (#33433384)
It most probably flips a boolean flag in their db. is_hidden=True. Done.