I would say the story of KH1 is pretty great, it’s just that the gameplay and menus are quite dated and very frustrating to deal with. The platforming is still a bit of a problem but with dual-stick controls it’s at least bearable.
If you don’t want to play it, I would still recommend looking up the story beats in video form so you know the story. KH2 is where I would say the gameplay really takes off.
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.
Neat. I remember me and my friends trying to come up with enough stuff to build our own world. Pretty sure we didn’t but still cool to see all the player built stuff.
Looks like 1.4.1 is the first Graal Reborn revision. Don’t see a 1.4.0 anywhere. Are you running the server as well or just the client?
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.
I have used gocryptfs (https://github.com/rfjakob/gocryptfs) in the past, it creates an overlay mount that encrypts each dir and file separately, so no need to precreate a container. There are some security downsides to this approach though so be aware of that. https://nuetzlich.net/gocryptfs/threat_model/
A torrent is broken into pieces, and further into blocks. The torrent file contains hashes of all the pieces that make up the full torrent. The client validates each piece that is downloaded and will re-download from another peer if an invalid piece is encountered. The spec goes in to more depth if you’re interested. https://wiki.theory.org/BitTorrentSpecification
There are 4 pinned posts at the top, should be more posts below that.
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