bjorney

It’s really not that complicated. At a high level:

• $5/mo for having the service turned on
• $5/mo for every TB storage above and beyond the first 1TB
• $1 for every TB of data transfer beyond the first 1TB in a month

And then divide those numbers because it’s actually billed by the hour

That assumes that an adversary has control of the browser

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

The big reason you don’t want to send passwords over https is that some organizations have custom certs setup

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

It is better to just not send the password at all.

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

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

deleted by creator

The word ‘decipher’ is doing a lot of heavy lifting. I’m wondering if they socially engineered or just found it written somewhere in the house?

You can plausibly brute force up to 4, maybe 5 words of a seed phrase. It takes longer than a normal password because every seed phrase is technically valid, so the only way to know if your brute force is successful is to generate thousands of addresses at each of the different derivation paths you may expect funds to exist at.

The same seed phrase is used for Bitcoin, Ethereum, Monero, etc, but each currency uses the seed phrase to generate addresses in a slightly different standard. Additionally, each wallet uses a slightly different variation of that. Within each wallet is a notion of accounts, and within each account you could have dozens of addresses. You need to generate each of those addresses, and scan each cryptocurrencies blockchain to see if those addresses have ever been used.

Realistically one of three things happened: his seed phrase was written down and they found it, it was password protected or on a drive with weak AES encryption and they cracked THAT instead, or finally, he used a hardware wallet and they exploited a firmware vulnerability to lift the PIN and transfer out funds and/or read the seed from the device

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.

Does Google Cloud not count as “own hardware” for google?

That’s why the bars are so different. The “cloud” price is MSRP

This is only true for steam keys sold on other platforms afaik

Yes but if it’s first instinct is “go left” on 1-2, it’s pretty apparent the reward function could use some tuning

It’s not necessary but there is no reason not to.

Pros:

• production and development programs are more similar
• upgrading your base image won’t affect your python packages
• you can use multi stage builds to create drastically smaller final images

Cons:

• you have to type venv/bin/python3 instead of just python3 in the run line of your dockerfile

When you teach a child what a dinosaur is, you have to do a lot more explaining than when you try and teach an adult what a dinosaur is in french - the child isn’t just learning a language for those 10 years.

You gotta donate to planned parenthood for every dollar spent there. It’s like buying carbon offsets, but for sandwiches. /s

More, 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.

deleted by creator

I haven’t used dual shock so I can’t speak to that, but as far as Xbox 1/S controllers, there is no 1st party support - literally all the drivers are from some non-MS affiliated GitHub page. 360 controllers required the xpad driver as well - that isn’t 1st party support. Yes they work out of the box with steam if you are using a wired connection, but that’s because it’s going through steaminput (not 1st party either), and making the controls of the submarine dependent on being launched through steam is even more absurd. Gen 2 series 1/S controllers didn’t work via Bluetooth for a long time after they (silently) launched on most LTS Linux OSs due to the kernel missing requisite BLE functionality

That’s only assuming the sub was running windows, where Xbox controllers work out of the box. On Linux there are no first party drivers, and Bluetooth support on the 1/S controllers simply didn’t exist at the time this happened. If it was an embedded system there would be no support whatsoever.

https://www.theverge.com/2017/9/19/16333376/us-navy-military-xbox-360-controller

US Army used to spend $38,000 per controller until they found out Xbox controllers were better

For what?

You will probably have waaaay more issues trying to get the windows client working through wine than dealing with any hiccups on the Linux client. It was buggy but passable like 5-6 years ago so I’m sure it’s much better now

You can try running it through a VM first before making the switch - 3d performance will be horrendously bad, but at least it will give you some piece of mind.

If unity gives a different download for each, you would have the best luck with whatever version matches closest (so the 22.04 download on current pop_os). Basically the more system dependencies the program has the more likely you will run into conflicts installing on a mismatched OS, but it isn’t guaranteed to cause problems (e.g. program requires openSSL version 1.2, but my OS ships with 1.1). I think unity just bundles everything with the binary, so it should be fine.

For what it’s worth, i used it on Ubuntu back when it was still in beta and it was super buggy (the installer and account stuff mostly, the engine itself seemed ok), so hopefully their Linux offering has since improved.