Comment by hypeatei
9 months ago
Here is a strongly encrypted base64 version to keep hackers out:
bWFnbmV0Oj94dD11cm46YnRpaDozY2FhNzFmM2VjOGNiY2NjNmZjYTRmZWI3MTg1ZGEyYmFiMTQ5YmE3JmRuPU5QRCZ0cj11ZHA6Ly90cmFja2VyLm9wZW5iaXR0b3JyZW50LmNvbTo4MCZ0cj11ZHA6Ly90cmFja2VyLm9wZW50cmFja3Iub3JnOjEzMzcvYW5ub3VuY2U=
Allegedly, the password (also base64 encrypted) is:
aHR0cHM6Ly91c2RvZC5pby8=
Has anyone been able to reverse this base64 encryption? Whatever am I going to do with this?
It can't be reversed, unfortunately. base64 has been peer proven as mathematically unhackable.
Username checks out.
Same for base16. That's why those pesky hash digests always use it.
1 reply →
do you still hang out with CrashOverRide?
1 reply →
https://www.base64decode.org/
I hope this helps you
It was a joke, but thank you. The internet needs more helpful people.
Wasn't it a joke?
1 reply →
[flagged]
I'm not sure. There are 64 bases. Probably quantum proof.
[flagged]
7 replies →
I dug into this a little and one of the files is 164GB. How do you even work with these files? That is, how would I search for my SSN on my windows box?
That's not even that big? `cat big_file | grep -v my_term` would go line-by-line and show any lines matching your query. If you're doing a lot of queries, you'd probably want to index it, so you throw it into a sqlite database with the usual SQL utils.
Edit: I missed you said Windows. Probably Powershell have similar utilities, so you can do `ReadFileLineByLine \r \d big_file | ReturnHitBySearchTerm \v \t \s my_term` or something similar.
>ReadFileLineByLine \r \d ssn.txt | ReturnHitBySearchTerm \v \t \s trampas ReadFileLineByLine : The term 'ReadFileLineByLine' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1 + ReadFileLineByLine \r \d ssn.txt | ReturnHitBySearchTerm \v \t \s tra ... + ~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (ReadFileLineByLine:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException
:(
All I know about powershell I just learned by accident: ls works
You absolutely do not want to use "-v" with that grep.
Nor do you want to use cat (UUoCA) but that's very much a minor point in comparison.
1 reply →
Using sift on a 100GB txt file still takes multiple minutes. I haven't tried ag, but grep is supposedly slower.
1 reply →
I can't believe HN mods think it's ok to leave this comment up. I don't know of a way to report it myself unfortunately.
Excuse me, why is linking to something bad? Especially when it contains your own data?
https://en.wikipedia.org/wiki/Doxing?lang=en
2 replies →
I get it now, but I have so much imposter syndrome that I wasn't sure if this was ACTUALLY something I needed to figure out -__-
Anyone know the size after the 50GB file is un7zipped?
EDIT: answer: 2 files, 176GB and 120GB, total is 298GB.
Entire family is in the list, with every address they've lived at in the last 40 years.
Freeze your credit reports, folks.
Elsewhere in this thread I posted a detailed commentary on what the torrent contains.
FYI: This is only the two social security files, not the whole breach.
[dead]