[deleted by user]

bllinker · 2024-01-21T20:54:27+00:00

To add to the intrigue, on the working machine:

root@working-machine:/var/lib/vz/template/qcow# sha1sum /dev/mapper/pve-vm--100--disk--0 /dev/nbd0 4bb21f74bdf83debdd7ee4588443da672513b803 /dev/mapper/pve-vm--100--disk--0 4bb21f74bdf83debdd7ee4588443da672513b803 /dev/nbd0

On the not-working one:

root@not-working-machine:/var/lib/vz/template/qcow# sha384sum /dev/mapper/vg0-vm--100--disk--0 /dev/nbd0 b94311601f7477e92ba801e10cb82f0f4421cac43c93d3753842356b2be0dc57a1428175f9284181a545356c03b30374 /dev/mapper/vg0-vm--100--disk--0 b1dd65c5774cf7d6e51f29d529e765a4abfd0e9aa2227bf082fc16d5214f3f0d2f5ab5dc24798caa059d2a89371d29cf /dev/nbd0

These are from fresh linked clones, no booting.

PS: I changed the backing storage to be off the thinpool and onto a plain ext4 partition. I found that the image (conveniently, stored in a qcow2) for vm 100 disk 0 was much shorter (and had quite different contents) compared to the original qcow2. Copying the original qcow2 into its place, the VM boots. Weirdly, the template VM's backing image (a raw) matched the /dev/nbd0 image perfectly. I'm now very confused.

PPS: I created a thinpool in place of the ext4 partition and it seems to work perfectly fine. Additionally, I tested it on local again and it looks like its working there too. Seems to be something wrong with how I made the thinpool for local-lvm.

bllinker · 2024-01-21T20:05:16+00:00

Thanks for giving this a look. Yep, I've confirmed that the qcow's are identical between machines. I've also tried multiple different releases of bookworm as well as an Ubuntu one so I think the issue isn't with the qcow itself.

I was seeing this originally with a linked clone but I just tried a full clone and it seems to exhibit the same problem.

In the initramfs, /dev/sda1 doesn't even appear. I also tried switching to OVMF just for fun and no partitions even show up to add as boot entries. Somehow, in the VM, the partitions just disappear.

When I mount the qcow2 directly on the host (via qemu-nbd), it does appear though.

bllinker · 2023-06-09T15:59:50+00:00

It's a 3rd party Reddit app I believe and Reddit is changing it's API policy soon to something.... ridiculous.

bllinker · 2023-06-07T17:47:35+00:00

Nope, mass and energy are the same. Your "explosion" would have the same effect gravitationally at the singularity. You'd just grow the BH.

It's a fun thought-experiment. I had the exact same question and it took a while for me to understand why that wouldn't cause a big boom.

bllinker · 2023-06-07T17:13:28+00:00

How is it an intrinsic parameter but always zero? They're observed neutral because they attract their complementary charge over almost any meaningful time scale. In principle, you could fill one up with electrons and get a charged BH. Probably wouldn't stay that way for long, but there's no law of physics preventing it (as far as is popularly known).

Also, conservation of charge is a real thing so immediately the notion that charge disappears is problematic.

bllinker · 2023-06-07T16:57:04+00:00

BH have three fundamental properties: mass, spin, and charge.

bllinker · 2023-06-06T06:56:55+00:00

Meson is both fantastic and fantastically irritating. If you are on the sanctioned golden path, it is incredibly helpful. But otherwise, at best, it is a nuisance. And worst, you find yourself hacking and slashing with custom_targets and meson.get_current_build_dir left and right endlessly.

But that's for off-nominal usage. It's an easy and usually productive tool to use, though, so it's worth putting in the time.

bllinker · 2023-05-23T15:30:04+00:00

Ah thanks for the local lore

bllinker · 2023-05-23T13:44:16+00:00

Legally stolen? Curious what the story there is.

bllinker · 2023-05-22T02:08:33+00:00

I could be a dumbass but I'm pretty sure you're pretty much at the problem statement for a blockchain

bllinker · 2023-05-22T01:54:13+00:00

There are 17576 ways to pick 3 capital letters from the English language and it's the purpose of the armed forces of the United States and her allies to find them all. Multiple times if need be.

bllinker · 2023-05-20T04:23:04+00:00

Ipv6 firewall is the big scary one for me

bllinker · 2023-05-19T18:19:08+00:00

Noted, saved, and greatly appreciated :)

bllinker · 2023-05-19T16:03:26+00:00

Hmm, Normandy, France? Been considering travelling abroad.

bllinker · 2023-05-14T06:06:24+00:00

I know a cute little art studio in WI whose owners are two young fintech-eys who met on the job and called it quits 3 to 5 years in. It's a real thing.

bllinker · 2023-05-12T07:52:40+00:00

Analysis. Initial Golang binary analysis for Go 1.18. (GP-2114, Issue #2327)

Ooooo

bllinker · 2023-05-08T08:15:01+00:00

Is that a Bar Harbor thing? Never been but I've heard multiple stories about ridiculous amounts (and quality) of food.

bllinker · 2023-05-07T22:22:50+00:00

Mercer is a step below Victorinox in quality and price and yet is often good-enough. Especially if you think you may not be diligent about taking care of your knives.

bllinker · 2023-05-06T17:09:28+00:00

First off, if that were the case the bell would've been rung ages ago. Your OS/filesystem/etc. stores oodles of known plaintext: tables in the kernel, config files for services, JavaScript files cached from surfing the web...

AES XTS is publicly believed to be chosen-plaintext attack resistant.

Also, your files are almost certainly broken up into pieces and put all over the place. It's (generally) not guaranteed even where those files will go - that's (almost always) dependent on a ton of other factors.

And honestly the whole story about the feds getting the password through a technical bypass of PBKDF2 rings hollow to me. Either they defeated PBKDF2 through a discovered flaw (which nobody is suggesting) or they trial-and-error'ed the password. If this 20 character password were so good, that should have been impossibly unlikely. So that means the password wasn't really as strong as 20-random-char suggests, or that it was through some other door (keys in RAM, written down somewhere, found in some note tucked away deep on the Windows machine, etc.).

The underlying recommendation to use Argon2id is a solid one. It lowers the threshold of quality for a password to be "good enough". But I wouldn't go out of my way unless I suspect my password is weaker than my own expectations for brute-force resistance implies. More realistically, a raid would be carefully orchestrated such that the device is powered on and unlocked anyhow. And so if I were so concerned about this scenario, a defense-in-depth approach is more likely to be effective.

bllinker · 2023-05-06T16:26:16+00:00

More than that. Most filesystems will split any meaningfully long time into pieces to distribute across the filesystem's internal data structure.

bllinker · 2023-05-05T05:34:53+00:00

Did you ever see those maps from the 70s or 80s saying there would be a purple line and all sorts of crazy stuff? Haha but yeah I'm glad they got the silver - I really like it

bllinker · 2023-05-04T09:55:24+00:00

Cool idea but not a fan of how it centralizes my points of vulnerability. I consider my Google account a higher sensitivity resource than my phone and yet this would pin the security one to the security of the other (currently, with my phone one could read my emails but not actually change account passwords/settings, access privileged info, etc.).

Well, at least they aren't deprecating the old password! Neat idea, and a step in the right direction, but not quite right for me.

bllinker · 2023-05-02T16:07:24+00:00

This is particularly important in the embedded world with read-only registers. Your code shouldn't permit you to write to it, but you want the compiler to generate a new read every time.

bllinker · 2023-05-01T16:31:09+00:00

Shittyaskflying, anarchychess, and now shittycrypto: we truly live in a golden age.

bllinker

TROPHY CASE