dataprolet

joined 1 year ago
MODERATOR OF
[–] [email protected] 1 points 6 months ago (1 children)

The more you know.

[–] [email protected] 1 points 6 months ago (4 children)

You can't do LUKS on LVM either, right? Only LVM on LUKS, just like Btrfs on LUKS.

[–] [email protected] 4 points 6 months ago (6 children)

Just use Btrfs subvolumes.

[–] [email protected] 14 points 6 months ago (3 children)

+1 for Mull.

And yeah, on Android unfortunately you gotta choose between privacy (Firefox/Mull) or security (Chromium).

[–] [email protected] 4 points 6 months ago

Some contect, the tractor randomly appeared on an intersection in the middle of the city. My two teammates weren't able to see it and for them I appeared to be hovering mid air. It's obviously the rusty tractor, but why is it green? Where did it come from? And why couldn't my mates see it? We were in an empty lobby by ourselves by the way. https://gta.fandom.com/wiki/Tractor

[–] [email protected] 5 points 6 months ago

It's probably enough to save everything in ~/.config/lutris.

[–] [email protected] 8 points 6 months ago

It's simply a risk. Android is designed how it is for a purpose.

I still use a custom ROM, GrapheneOS - which also strongly recommends not to root your device!

[–] [email protected] 4 points 6 months ago
  1. This could be due to missing Google services?

I wouldn't say that GrapheneOS isn't ready for daily use just because you have some issues. It's a mature project with decent support for only a couple of devices and a lot of people use it on a daily basis without issues.

[–] [email protected] 2 points 6 months ago (1 children)

Don't use the Beta channel and expect everything to work.

I don't use Google at all but theoretically everything should work with the sandboxed Google services.

And I did use Nova Launcher and it's working without an issue. Importing a profile should also work.

[–] [email protected] 2 points 6 months ago (1 children)

Thanks, that did the trick!

[–] [email protected] 2 points 6 months ago

Looks perfect, thanks!

[–] [email protected] 1 points 6 months ago

I actually don't know. All I want to achieve is having access from my smartphone to my local network via the VPS, which is the only device with a public IP. So it's basically a point-to-site connection from my smartphone to my home server with the VPS in between.

And I just followed a tutorial and that's why I set up the 10.0.0.0/24 IP range.

 

Solved, see below.

I recently reinstalled my home server and was unable to open my LUKS-encrypted hard drive. Neither my usual passphrase nor a newly created keyfile were working. I tested on different distros, initially on my new Proxmox installation, later on a the Arch ISO. I eventually tried the disk on my main system, on which it used to be and I still had an old keyfile on - et voilá. So I created keyfiles as suggested in the wiki and occasionally md5sum returned a different hash for the keyfile! Why is this happening? I find' this extremely concerning because this could potentially result in massive data loss due to a keyfile apparently randomly not working as I was experiencing it. What am I missing?

For reference because I don't know how to share what I exactly did.

Scenario #1:
A directory on a mounted hard drive on my desktop.

$ echo -n '$mypassphrase' > ./dir/keyfile
$ md5sum ./dir/keyfile
 c6dd9329dbe030127ce5e19d85de4df9 ./dir/keyfile
# chown root:root ./dir/keyfile; chmod 400 ./dir/keyfile
# md5sum ./dir/keyfile
c6dd9329dbe030127ce5e19d85de4df9 ./dir/keyfile

Scenario #2:
My old keyfile in /etc on my desktop containing $mypassphrase.

# md5sum /etc/keyfile
a1c10c2d023c982259f6c945ebee664e /etc/keyfile

Scenario #3:
Booted from the Arch ISO on my server.

# echo -n '$mypassphrase' > keyfile
# chown root:root keyfile; chmod 400 keyfile
# md5sum keyfile
c6dd9329dbe030127ce5e19d85de4df9 keyfile

Scenario #4:
A directory in /home on my desktop.

$ echo -n '$mypassphrase' > ./keyfile
$ md5sum keyfile
a1c10c2d023c982259f6c945ebee664e keyfile

EDIT: I just moved the disk back into my server and tried echo'ing my passphrase into a keyfile which returned the hash starting with c6, whereas opening a file using nano and pasting the passphrase into the file returned the hash starting with a1.

EDIT: I moved the disk back into my server, reinstalled Proxmox and tried again. I was able to unlock the disk after I pasted the passphrase into a file and deleted all trailing spaces/newline. I also tried echo'ing the passphrase into a keyfile and that also did not work, no clue why but it seems to work on some systems on not on others.

view more: ‹ prev next ›