Client side verification is just security by obscurity, which gains you very little.
If someone is capable of MITM attacking a user and fetching a password mid-transit to the server over HTTPS, they are surely capable of popping open devtools and reverse engineering your cryptographic code to either a) uncover the original password, or b) just using the encrypted credentials directly to authenticate with your server without ever having known the password in the first place
You are acting like someone checked off a “log passwords” box, as if that’s a thing that even exists
Someone configured a logger to write HTTP bodies and headers, not realizing they needed to build a custom handler to iterate through every body and header anonymizing any fields that may plausibly contain sensitive information. It’s something that literally every dev has done at some point before they knew better.
This is only true for steam keys sold on other platforms afaik
It’s not necessary but there is no reason not to.
Pros:
Cons:
venv/bin/python3 instead of just python3 in the run line of your dockerfileMore, but not way more - they would be licensing window IoT, not a full blown OS, and they wouldn’t be paying OTC retail rates for it.
lol. Did this in my old building - the dryer was on an improperly rated circuit and the breaker would trip half the time, eating my money and leaving wet clothes.
It was one of the old, “insert coin, push metal chute in” types. Turns out you could bend a coat hanger and fish it through a hole in the back to engage the lever that the push-mechanism was supposed to engage. Showed everyone in the building.
The landlord came by the building a month later and asked why there was no money in the machines, I told him “we all started going to the laundromat down the street because it was cheaper”
It’s unavoidable - once the cheese gets hot enough the steam will either force the liquid cheese out of existing holes, or it will make its own holes.
Make sure they are fresh out of the freezer when you put them in, as this lets the outside crisp up more before the inside becomes lava. Once you get close to the prescribed cooking time, you need to just sit in front of the oven door and watch them, and as soon as 2-3 break open, take the whole tray out
Too bad it still can’t figure out how to do dead ass simple things the old assistant had no problem with, like setting a reminder or alarm
You can just point your domain at your local IP, e.g. 192.168.0.100
The feature is explicit sync, which is a brand new graphics stack API that would fix some issues with nvidia rendering under Wayland.
It’s not a big deal, canonical basically said ‘this isn’t a bug fix or security patch, it’s not getting backported into our LTS release’ - so if you want it you have to install GNOME/mutter from source, switch operating systems, or just wait a few months for the next Ubuntu release
GNOME said this update is a minor bug fix (point release)
Canonical said this is actually a major feature update, and doesn’t want to backport it into its LTS repositories
Not with 64gb ram and 16+ cores on that budget
They aren’t talking about system administrators. They are talking about 3rd party software presenting a privilege escalation prompt (administrator access) and changing your default browser without you knowing about it
You could set it up in docker whilst still on windows, and then all you need to do is copy/paste your compose file onto your new Linux machine, that way you aren’t struggling to learn two things at the same time (alleviates the “I don’t know if the problem is with my docker config or my host OS”)
Laptop, passport, cash beyond what I’m willing to keep in my wallet
“how dare they use the right tool for the job without taking the time to learn how to do it sub optimally first”
That’s still not that much data
Gaming is 10-20% of the ISPs total network load, and the MW3 launch constituted like a 110% increase over base network load, so yes it’s a lot of data.
Advertisements and crawlers constantly use up far more bandwidth.
Crawlers rely on private connections between datacenters, very little of that traffic touches residential ISPs
Fight the real problems instead of blaming the users.
Literally no one is blaming users - There are plenty enough reasons to hate most ISPs, we don’t have to make up facts to find new ways to be mad.
Literally why CDNs and bitorrent tech exist
Neither of these reduces the amount of bandwidth an end user requires to download a 120gb file. If anything torrenting makes it more problematic because the upload is spread amongst a dozen low density residential users rather than a single high throughput datacenter
This is just the ISPs posturing to raise rates.
Ya absolutely. Doesn’t change the fact that ‘gaming uses very little bandwidth’ is only considering the UDP packets sent during an online gaming session and ignoring all the other sources of usage.
I literally have 5-10gb of updates queued up the first time I open steam nowadays
Read the 2nd sentence of the article. They are talking about 120gb CoD patches
No it doesn’t, if they intercept an encrypted password over HTTPS they can resend the request from their own browser to get access to your account
What is the problem with that? The password is secure and only shared between you and the site you are intending to communicate with. Even if you sent an encrypted password, they wrote the client side code used to generate it, so they can revert it back to its plaintext state server side anyways
How would you verify it then?
If not sending plaintext passwords was best practice then why do no sites follow this? You are literally posting to a site (Lemmy) that sends plaintext passwords in its request bodies to log-in