I didn’t read it like that. What I take from it is that he’s implying that the government uses something much stupider than sql, like Lotus1-2-3 or plain txt files or excel. I really wouldn’t be surprised that there’s some government department that had their IT done during the first Bush administration and didn’t really upgrade from it since.
There are also probably some departments that don’t get much funding, so they organise part of their work into some shared excel files.l
Nothing really wrong with that. Unless he’s implying that the entire federal government works like that, which is preposterously stupid.
DahGangalang@infosec.pub 1 week ago
Just so I’m clear, you’re implying that a given SSN could appear associated to multiple “keys” because the key-value pair in a NoSQL database could have complex data.
An example I can imagine is a widow collecting her dead husband’s Social Security. Her SSN could appear in her own entry and also in her dead husband’s as a payee of that benefit, thus appearing as a “duplicate” SSN.
Is that in line with what you’re saying?
knightly@pawb.social 1 week ago
Indeed, that’s a possibility, but I’m not privy to the structure of the social security administration’s databases so I couldn’t say if it was indeed the case.
DahGangalang@infosec.pub 1 week ago
Thats how I feel too.
Lol, I’d love to see the data hes trying to speak about (not that that’d be any kind of concerning for privacy /s). I don’t think he’s outright lying, but it definitely feels like a misrepresentation / wrong conclusion from the data.
But thanks for your part in helping me understand all this!