In the US they are usually governed as real estate legally. You can resell it, but most people aren’t interested in paying the maintenance fees. You’ll find all sorts of timeshares out there being resold for 1$ because they just don’t want to pay the maintenance fee anymore.

The -k argument on my openssl accepts a passphrase, not a file. You likely encrypted with the filename as the secret, not it’s contents. Perhaps you should use -kfile instead.

$ openssl aes-256-cbc -help
Usage: aes-256-cbc [options]

General options:
 -help               Display this summary
 -list               List ciphers
 -ciphers            Alias for -list
 -e                  Encrypt
 -d                  Decrypt
 -p                  Print the iv/key
 -P                  Print the iv/key and exit
 -engine val         Use engine, possibly a hardware device

Input options:
 -in infile          Input file
** -k val              Passphrase**
 -kfile infile       Read passphrase from file

Perhaps they should ask Copilot how their templating system works.

As an aside, these are the client logs, check the /var/log/ auth.log or secure files or journalctl to see if the server logged why the access was denied.

You seem to be misinformed on how the internet works. Nothing is “free”. ISPs have to buy equipment, pay for expensive physical connectivity (without disturbing existing infrastructure), and usually have to deal with constant, ever increasing bandwidth requirements.

I’m all for a bit of net neutrality, but ISPs tend to get a lot of flak for policies like this, for seemingly no reason. For example, let’s say ISP A and Upstream B have a mutual bandwidth sharing policy (called Peering) where both sides benefit equally from the connectivity. ISP A determines that N is using all the bandwidth to Upstream B. ISP A has three options: N gets all the bandwidth to Upstream B (disturbing other traffic to/from that network), N has to be throttled to allow all traffic equally, or ISP A and Upstream B need to expand their network again (new equipment, new physical links) which will cost a lot of money. N doesn’t even pay ISP A or Upstream B, they just pay their ISP C. In the end, ISP A has to throttle N, and N is the one who had to expand/change their business model to deliver content to their customers. They had to go out and buy services from many upstream providers to even the load and designed a solution to install Caching boxes inside each ISP’s datacenter so their traffic could reach end users without going upstream.

I mean it was not too long ago there was a bug which could lead to an unauthenticated RCE against Bluetooth on Android.

https://nvd.nist.gov/vuln/detail/CVE-2022-20345

So yea, reducing surface area of attack when a feature is not needed is kinda important.

Yes, but as I’ve found recently AES-NI is only as good as your software support for it. Had a team using an ancient version of winscp and they kept complaining about download speeds on our 10Gb circuit. Couldn’t replicate it on any other machine with the newest version of winscp so I installed their exact version. AES-NI support wasn’t added until like 2020 and it gave them 5x better download speed after upgrading.

Does cryptsetup/luks do that? I thought that was only software encryption.

You can, sure, but you probably shouldn’t. Encrypting and decrypting consume additional cpu time, and you won’t gain much in terms of security.

Running stock 14, but rooted with Pixel Xpert. I also have a dark mode quick tile and I don’t think it was added by Pixel Xpert.

This is funny because most object storages now use keys that represents a path. For example, you can host a website on S3 with folders for js/css/etc and it “just works”.

Based on your edit about getting the public IP: Most firewall/routers are not configured to do this operation by default (called Hairpinning). If you request your firewall/router’s external IP address from the internal network you won’t get a response unless Hairpinning is enabled and some devices don’t allow you to do that. If you have an internal dns server, you should override the internal dns to return the private ip address so it goes to your nginx reverse proxy instead of the firewall/router.

Since this is a github pages site, the whole thing can be downloaded from the git repo: https://github.com/xenevel/dark-souls-2-sotfs-cheat-sheet

Easiest is to select the green Code button and click Download ZIP. You should be able to open the index.html page in your browser and use it like normal. YMMV if this uses content/data from other sources/sites.

I’ve been watching this guy’s backlog on building a kernel and bootloader from scratch. A bit monotone but amazing technical knowledge. https://youtube.com/@nanobyte-dev