Make an instant fortune by shorting the market, and get free but mid quality root beer.
Make an instant fortune by shorting the market, and get free but mid quality root beer.
And I feel like half of that 20 years was based on FOMO. “I better get the next Assassin’s Creed or I’ll miss out”, and then it’s all the same crap but they still sold a million of them. People do eventually wise up to FOMO.
. . . our goal is not to push any specific agenda
This is the part they’re actually getting at. Not that the fundamental game design is for everyone (which, yes, is what they try and fail at), but rather they’re responding to people who think they’re failing because they put a woman as the protagonist in some game or another.
Always look at the eyes when someone smiles, especially in advertisements. They come off as creepy once you know this trick.
And then there’s this guy, which in the context of Babylon 5, is absolutely perfect:
Which, incidentally, would probably past legal muster. You can get pretty close to the source material, and as long as it’s your own custom art, it’s not infringement.
That said, lawyers can send a C&D letter for anything. Doesn’t mean it will hold up in court, but they’re betting the target won’t want to pay that kind of money to fight it.
Also, Iron Bands of Bilarro in DnD 5e, but I’m not sure how far back the history of that item goes. DnD 3.5 had Iron Flask that works kinda the same, but Iron Bands is more similar to a Pokeball.
Wouldn’t be the first dubiously legal copy of Windows I have.
“The Daily Mail, with its tales of red revolution financed by Moscow, was even more wildly wrong than usual.”
Daily Mail has been terrible since Orwell was in Spain.
If the end user is reusing passwords. Which, granted, a lot of people do.
On the flip side, we’re also forcing the use of JavaScript on the client just to handle passwords. Meanwhile, the attack we’re protecting against only works for reused passwords, and the attacker is inside the server and can see the password after transport layer encryption is removed. This is a pretty marginal reason to force the complexity of JavaScript.
Per your edit, you’re misunderstanding what Bitwarden does and why it’s different than normal web site password storage.
Bitwarden is meant to not have any insight into your stored passwords what so ever. Bitwarden never needs to verify that the passwords you’ve stored match your input later on. The password you type into Bitwarden to unlock it is strictly for decrypting the database, and that only happens client side. Bitwarden itself never needs to even get the master password on the server side (except for initial setup, perhaps). It’d be a breach of trust and security if they did. Their system only needs to store encrypted passwords that are never decrypted or matched on their server.
Typical website auth isn’t like that. They have to actually match your transmitted password against what’s in their database. If you transmitted the hashed password from the client and a bad actor on the server intercepted it, they could just send the hashed password and the server would match it as usual.
It doesn’t. It just means the attacker can send the hash instead of the password.
With comments like this all over public security forums, it’s no wonder we have so many password database cracks.
You could salt it. Distributing a unique salt doesn’t help attackers much. Salt is for preventing precomputing attacks against a whole database. Attacking one password hash when you know the salt is still infeasible.
It’s one of those things in security where there’s no particular reason to give your attacker information, but if you’ve otherwise done your job, it won’t be a big deal if they do.
You don’t hash in the browser because it doesn’t help anything.
Scrypt has the same limit, FWIW.
It doesn’t matter too much. It’s well past the point where fully random passwords are impossible to brute force in this universe. Even well conceived passphrases won’t get that long. If you’re really bothered by it, you can sha256 the input before feeding it to bcrypt/scrypt, but it doesn’t really matter.
Given the contemporary examples, they weren’t wrong to think so. Everyone was trying to make a console in the 16/32-bit era.
Some of these are better than others–I’m fond of the PC Engine–but none can be called successful. Neo Geo is somewhat of an exception because it was used as arcade hardware. Some others here are the butt of jokes. There’s also a bunch of Japanese consoles around this time that go nowhere, and are little more than fodder for retro gaming YouTube channels.
Sony took a big gamble and won.