2023 Security Check-up Reminder

  • 🔧 At about Midnight EST I am going to completely fuck up the site trying to fix something.
Based except password managers are talmudic, use your memory. I use unique 25 character passwords on each website I'm registered on (not many) and I keep all of them only in my memory and nowhere else. How? The first 15 or so characters are the same for each website and it's only there to provide entropy so you're safe against brute force attacks; the second part of the password is unique and based on a common pattern you can deduce when you want to log in, e.g. the pattern could be each site's name in reverse like smrafiwik or elgoog. This part is useful so if a databreach happens on that site, you won't be compromised on other websites. I obviously don't use this particular pattern, but you can get creative and then you only have to remember the pattern and the universal part of the password, this way you don't have to rely on software and it also gets your noggin joggin.
You may give me the autistic rates now.

I think this method is possibly quite dangerous.
While it means you aren’t using the same password for different sites, any actual human looking through a leaked list of email addresses and passwords for a given site might very well spot the pattern of [weirdword][sitename], start guessing other sites, and be in with a good chance of getting in.

And how long until scripts using AI to do the pattern recognition and guessing are out there.
 
I wanted to start implementing the use of passphrases instead of passwords a while ago, but roughly 0 of the websites I tried it on allowed it because they needed special characters and numbers and all that shit and I ended up just sticking with "normal passwords" like nig6er?.
 
  • Like
Reactions: biggacracka
Just write your passwords on paper.
Store them in your autistic brain.
Or, if that's not an option for you, write them in an inconspicuous .ini file in System32 folder on an old shitbox that isn't connected to anything. Also don't store them in plain text, so that it won't get picked up by file search - the easiest way to do this is write them in an MSPaint file, then change the extension from .bmp to .ini.
 
You know the point of computers is actually so you don't have to do all this menial shit yourself in the first place. Just use something like keepass which is local only. Keepass2android for mobile, simply copy the database file from your pc to your phone. People these days are seriously so fucking lazy that they think copying one small file is a chore that should be offloaded to a cloud computing program instead. Just lol.

Also gregtech is the best minecraft mod.
How are you calling someone lazy for not using your technique while also praising your technique for saving someone from the menial task of typing in passwords themselves. I can type extremely fast, and I simply like having access to all my passwords on any device I ever want to use (because it's in my brain). If you want to use your passwords on any external devices you're shit out of luck, unless you back it up into the cloud in that case you have to put faith in whichever hosting service you're using. Unless you self host it yourself, which is respectable but I simply don't want to. I self host a lot of things from my own email server to a matrix chat instance, but I simply don't want to bother with password managers. It's not a matter of laziness, it's just simple and it also enhances opsec and I have a 110 wpm typing speed so I don't give a shit about typing in my password manually every time.

I think this method is possibly quite dangerous.
While it means you aren’t using the same password for different sites, any actual human looking through a leaked list of email addresses and passwords for a given site might very well spot the pattern of [weirdword][sitename], start guessing other sites, and be in with a good chance of getting in.

And how long until scripts using AI to do the pattern recognition and guessing are out there.
That's the point of the pattern, it's not supposed to be the sitename itself. Mine is incomprehensible gibberish and you wouldn't get the part where the universal part of it ends and the unique part begins. I just gave the example of reverse website name for demonstration purposes. Besides this is such an obscure method that I guarantee absolutely no hacker at all ever attempts to reverse engineer passwords to guess on different sites. It's just not happening.
Also, if the pattern part is gibberish then you're pretty much safe from dictionary attacks. If you also have a large enough universal part then you're safe from brute force attacks. And you only have to remember 2 things with this method and all of it is stored in your brain and nowhere else.
 
Last edited:
Just for fun, I tried to see if "mypasswordistotalshit!!" was a secure passphrase (it's not mine, I just came up with it off the top of my head) to see how long it would take a computer to crack. And this is why passphrases are better.

Screen Shot 2023-03-09 at 9.22.03 AM.png
Cool. It lasted 4 seconds to a combinator attack protected by md5.

Host memory required for this attack: 1475 MB

Dictionary cache built:
* Filename..: phpbb.dict
* Passwords.: 184390
* Bytes.....: 1574356
* Keyspace..: 33999672100
* Runtime...: 0 secs

97bf74ef9110392e2ff0446ea8b7bec5:mypasswordistotalshit!!

Session..........: hashcat
Status...........: Cracked
Hash.Mode........: 0 (MD5)
Hash.Target......: 97bf74ef9110392e2ff0446ea8b7bec5
Time.Started.....: Thu Mar 09 12:07:46 2023 (2 secs)
Time.Estimated...: Thu Mar 09 12:07:48 2023 (0 secs)
Kernel.Feature...: Pure Kernel
Guess.Base.......: File (phpbb.dict), Left Side
Guess.Mod........: File (phpbb2.dict), Right Side
Speed.#1.........: 7489.4 MH/s (15.31ms) @ Accel:32 Loops:1024 Thr:128 Vec:1
Recovered........: 1/1 (100.00%) Digests (total), 1/1 (100.00%) Digests (new)
Progress.........: 11039408128/33999672100 (32.47%)
Rejected.........: 0/11039408128 (0.00%)
Restore.Point....: 0/184390 (0.00%)
Restore.Sub.#1...: Salt:0 Amplifier:95232-96256 Iteration:0-1024
Candidate.Engine.: Device Generator
Candidates.#1....: 123456ikucat!! -> doublyi2i3i4!!
Hardware.Mon.#1..: Temp: 50c Fan: 0% Util: 98% Core:1935MHz Mem:7300MHz Bus:16

Started: Thu Mar 09 12:07:45 2023
Stopped: Thu Mar 09 12:07:49 2023
With SHA512 it lasted 7 seconds.

Host memory required for this attack: 1475 MB

Dictionary cache built:
* Filename..: phpbb.dict
* Passwords.: 184390
* Bytes.....: 1574356
* Keyspace..: 33999672100
* Runtime...: 0 secs

5552266ae4b71d617003f69f0d153d093eeba83187bf5cbd7875d49fcb4c51d6c1d01e0c3997c9f3959636ed80e35d793aa39b073135a498f7a231658771a323:mypasswordistotalshit!!

Session..........: hashcat
Status...........: Cracked
Hash.Mode........: 1700 (SHA2-512)
Hash.Target......: 5552266ae4b71d617003f69f0d153d093eeba83187bf5cbd787...71a323
Time.Started.....: Thu Mar 09 12:13:15 2023 (4 secs)
Time.Estimated...: Thu Mar 09 12:13:19 2023 (0 secs)
Kernel.Feature...: Pure Kernel
Guess.Base.......: File (phpbb.dict), Left Side
Guess.Mod........: File (phpbb2.dict), Right Side
Speed.#1.........: 349.5 MH/s (10.29ms) @ Accel:4 Loops:256 Thr:128 Vec:1
Recovered........: 1/1 (100.00%) Digests (total), 1/1 (100.00%) Digests (new)
Progress.........: 1379926016/33999672100 (4.06%)
Rejected.........: 0/1379926016 (0.00%)
Restore.Point....: 0/184390 (0.00%)
Restore.Sub.#1...: Salt:0 Amplifier:96000-96256 Iteration:0-256
Candidate.Engine.: Device Generator
Candidates.#1....: 123456iamxkd!! -> jepjepi2i3i4!!
Hardware.Mon.#1..: Temp: 55c Fan: 74% Util: 99% Core:1957MHz Mem:7300MHz Bus:16

Started: Thu Mar 09 12:13:13 2023
Stopped: Thu Mar 09 12:13:20 2023

You guys aren't as clever as you think.
 
Last edited:
Cool. It lasted 4 seconds to a combinator attack protected by md5.

Now do Bcrypt. By the way, I'm not trying to come across as an asshole, even if my post sounds like it.

Websites that use MD5 are fucking garbage anyway. I know that rainbow tables exist and I can't do anything to stop them (I have one, myself), so I'll chalk it up to lazy devs being lazy.

This is why I use different passwords for each website. If the admins of a site are lazy shits, it's not my problem, as long as the attackers only have one password.
 
I don't get the reasoning of people NOT using password manager.

If you happen to be swatted for some random reason and your things like papers are sized, all your accounts would be fucked. For those true and honest nothing to hide types - There is no such thing as innocence, only degrees of guilt (c). At least think about your girlfriend / mom discovering those "papers" and your extreme autism afterwards.
The most compelling reason to use a password manager is that you get to copy and paste your complicated 20+ signs passwords instead of typing them every single time, which, let's be honest, you wont.
 
I think this method is possibly quite dangerous.
While it means you aren’t using the same password for different sites, any actual human looking through a leaked list of email addresses and passwords for a given site might very well spot the pattern of [weirdword][sitename], start guessing other sites, and be in with a good chance of getting in.

And how long until scripts using AI to do the pattern recognition and guessing are out there.
Crackers do this with leaked password dumps already. They use the dumps as their core dictionary and start modifying the entries to broaden their attack.

What is useful though is: Using myEmail+registeredOnSite@provider.tld
The sites can of course filter this, but you can easier sort incoming mail and possibly see when a site had a leak.
The "+registeredOnSite" part is ignored during email routing and you get the mail at myEmail@provider.tld.
(Similar to Gmail, where it ignores anything appended with a . to your regular address name)

This works, because one of the biggest implementations used as MTA does this. So you need to
check if it actually works with your provider!

The world ended in 1945.

Capitals, numbers, punctuation, impossible to bruteforce, and easier to remember than nig6ernig6er and many more times secure.
Too bad lots of sites limit the password lengths or won't allow spaces (underscores work ok though).
I just don't understand why they would limit the length so much. Often only 16, 20 or 32 characters are allowed. 32 are borderline ok...
 
Last edited:
Chudbud? Isn't that the thing from the game all the kids play with the funny John Wick man?
 
Every web developer who still uses MD5 in $CURRENT_YEAR should be taken out back and shot.

But since devs are lazy and they don't care about security, half of the websites everywhere would be offline.
Best if it's a diy solution not using any salt at all.
And let's not forget there are still plaintext leaks here and there too...
 
  • Like
Reactions: Neo-Nazi Rich Evans
How are you calling someone lazy for not using your technique while also praising your technique for saving someone from the menial task of typing in passwords themselves. I can type extremely fast, and I simply like having access to all my passwords on any device I ever want to use (because it's in my brain). If you want to use your passwords on any external devices you're shit out of luck, unless you back it up into the cloud in that case you have to put faith in whichever hosting service you're using. Unless you self host it yourself, which is respectable but I simply don't want to. I self host a lot of things from my own email server to a matrix chat instance, but I simply don't want to bother with password managers. It's not a matter of laziness, it's just simple and it also enhances opsec and I have a 110 wpm typing speed so I don't give a shit about typing in my password manually every time.


That's the point of the pattern, it's not supposed to be the sitename itself. Mine is incomprehensible gibberish and you wouldn't get the part where the universal part of it ends and the unique part begins. I just gave the example of reverse website name for demonstration purposes. Besides this is such an obscure method that I guarantee absolutely no hacker at all ever attempts to reverse engineer passwords to guess on different sites. It's just not happening.
Also, if the pattern part is gibberish then you're pretty much safe from dictionary attacks. If you also have a large enough universal part then you're safe from brute force attacks. And you only have to remember 2 things with this method and all of it is stored in your brain and nowhere else.
Glad to see that you have a robot brain but for us humans with dozens if not hundreds of different accounts, memorizing that many variations requires an easily understood pattern, a huge mental effort every time to keep track of everything, or passwords that aren't nearly complex enough. Typing speed doesn't matter here, you want to use at least some special signs and typing them makes it even more annoying than just a few words.

You're going through convoluted explanations to defend not using the simplest and best solution, which is fine for you to do but don't encourage other people to engage in suboptimal practices.

I just don't understand why they would limit the length so much. Often only 16, 20 or 32 characters are allowed. 32 are borderline ok...
You won't be bruteforcing 20+ characters passwords over a web service. Locally, sure, but online is another story.
 
Last edited:
Now do Bcrypt. By the way, I'm not trying to come across as an asshole, even if my post sounds like it.
Time.Estimated...: Wed Mar 22 01:32:38 2023 (12 days, 12 hours)

Guessing the trouble is the size of my dictionaries. 184391 * 2. Someone who's actually good at cracking passwords would probably be using something better than a random password list downloaded online to crack bcrypt. Still, 12 days is not 9 quintillion years. And I'm using a freshly downloaded hashcat with no attempts to optimize for my system. Just downloading and running.

Point is that randomness is good. You want your password to only be crackable by brute force, because if you allow for human patterns you allow for angles of attack that use methods other than brute force to crack your passwords.

This article is almost 10 years old. That's how good cracking was back then. It's definitely more sophisticated now. "correct horse battery staple" is not a good password, because no password crackers rely on brute force these days and the xkcd meme password falls to a simple combinator attack.
 
Last edited:
Best if it's a diy solution not using any salt at all.
And let's not forget there are still plaintext leaks here and there too...
Ok, that made me amend my last post.

Web devs who store passwords in plaintext in $CURRENT_YEAR should be taken out back and shot.

Web devs who store passwords in MD5 in $CURRENT_YEAR should be demoted (or should at least upgrade to bcrypt.)

I'll take bcrypt over MD5 any day of the week, but if I find out that a website stores my password in plain text I'll be upset (then change everything else, even though I use different passwords for everything.)

Genuinely, we should have a law that says you must run bcrypt or higher or get fined. Maybe that would entice web devs (and businesses) to put security ahead of profits.
 
I feel really bad for this woman. I don’t know anything about her or her site but I can’t imagine doing this to somebody, even they were really stupid. I know nobodies opsec is not gonna be watertight but there’s basics she could have done to have minimised the damage here. I can’t imagine the malice that goes into doing something this deliberate. It’s as bad as the troon DDOS attacks.

Don’t have nudes, keep all your files on encrypted drives on external HDD’s or mega folders, different devices for different things. Just basic stuff. Providing people aren’t stupid the password leak shouldn’t be the end of the world.
 
Back