Comment on Sorry, Humble. You lived long enough to see yourself become the villain.
churrodestroyer@lemmy.zip 12 hours agoDo you know what a chosen-plaintext attack is?
Comment on Sorry, Humble. You lived long enough to see yourself become the villain.
churrodestroyer@lemmy.zip 12 hours agoDo you know what a chosen-plaintext attack is?
Undeclared_Mustard@lemmy.ca 12 hours ago
So, no. Got it.
churrodestroyer@lemmy.zip 8 hours ago
I think I can run strings through the same visual hash until I find a match, but you do you.
mushroommunk@lemmy.today 11 hours ago
Emails have two known symbols in them, the ‘@’ and the ‘.’, and you’ve said what two blurs you used. I would have called it a birthday attack myself (where the blur steps are the encryption key and depends on letters roughly blurring differently, aka hashing differently).
Of the people here they’re not the one showing what they don’t know
Tanoh@lemmy.world 7 hours ago
Aaaaaaaaackthually… You do not need a dot. Putting an MX record on a TLD is perfectly valid. Though pretty much 100% of all email validation forms are doing it wrong and requiring it. So in this case it almost certainly has a dot.
mushroommunk@lemmy.today 6 hours ago
Oh what’s technically valid as an email is insane. I’ve looked into it before for work and went “nope” and just grabbed one of the standard “wrong” regexes everyone uses.
Undeclared_Mustard@lemmy.ca 10 hours ago
You’re saying that this is reversible when you don’t know any of the parameters?
Have fuckin fun proving that.
mushroommunk@lemmy.today 9 hours ago
Bet, post your credit card info and I’ll put in the effort
Natanael@infosec.pub 3 hours ago
With text? Yes absolutely. The font is all I need, I will calculate the parameters based on how I observe the text to have been modified.
StupidBrotherInLaw@lemmy.world 7 hours ago
Based on just your comments here, you have no right to judge anyone else’s intelligence.