I brought up emanations in my first reply…

I even couched it with a “might be” because I’m aware there’s lots I don’t know.

It wasn’t that you may be wrong. It was your overconfidence and hyper-fixation on one type of security.

My brother in christ, you are still missing the point.

So you pick up a message that reads “867-5309” and the receiver picks up their landline and calls.

So you have a phone number now. One that you probably already had given the organization we’re talking about. If the call is staying landline and within the boundaries of their country, you aren’t picking up shit with your SDR. You need to have a physical tap somewhere.

They swapped cell phones which send and receive for pagers that receive only. Think for 2 seconds what that means for tracking. To say nothing of also losing the fucking microphone, camera, GPS…

There’s a reason pagers are allowed into SCIFs where phones and other devices which send are not.

There’s more to security than your experience picking up unencrypted shit with an SDR.

They might be in regards to emanation.

It’s funny how confident comments like these are without really thinking it though.

Sigh… I listen to David’s podcast, Volts.

WTF is he still doing on Twitter?

Already saving lives.

Bro keep up. They doin’ it again.

Wait till this crowd hears about smoke detectors.

Yeah that was fun times.

Luckily, thanks to using docker, it was easy enough to “pin” a working version in the compose file while I figured out what just broke.

For everyone’s reference, here’s my fstab to give you an idea of what works with linuxserver.io’s qbittorrent

## Media disks setup for mergerfs and snapraid

# Map cache to 1TB SSD
/dev/disk/by-id/ata-Samsung_SSD_860_EVO_1TB_S3Z8NB0K820469N-part1 /mnt/ssd1 xfs defaults 0 0

# Map storage and parity. All spinning disks.
/dev/disk/by-id/ata-WDC_WD100EZAZ-11TDBA0_JEK39X4N-part1 /mnt/par1         xfs defaults 0 0
/dev/disk/by-id/ata-WDC_WD100EZAZ-11TDBA0_JEK3TY5N-part1 /mnt/disk01       xfs defaults 0 0
/dev/disk/by-id/ata-WDC_WD100EZAZ-11TDBA0_JEK4806N-part1 /mnt/disk02       xfs defaults 0 0
/dev/disk/by-id/ata-WDC_WD100EZAZ-11TDBA0_JEK4H0RN-part1 /mnt/disk03       xfs defaults 0 0
/dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N4XFT0TS-part1 /mnt/disk04 xfs defaults 0 0
/dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N4XFT1YS-part1 /mnt/disk05 xfs defaults 0 0
/dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N4XFT3EK-part1 /mnt/disk06 xfs defaults 0 0
/dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N6CKJJ6P-part1 /mnt/disk07 xfs defaults 0 0

# Setup mergerfs backing pool
/mnt/disk* /mnt/stor fuse.mergerfs defaults,nonempty,allow_other,use_ino,inodecalc=path-hash,cache.files=off,moveonenospc=true,dropcacheonclose=true,link_cow=true,minfreespace=1000G,category.create=pfrd,fsname=mergerfs 0 0

# Setup mgergerfs caching pool
/mnt/ssd1:/mnt/disk* /mnt/cstor fuse.mergerfs defaults,nonempty,allow_other,use_ino,inodecalc=path-hash,cache.files=partial,moveonenospc=ff,dropcacheonclose=true,minfreespace=10G,category.create=ff,fsname=cachemergerfs 0 0

I do this with mergerfs.

I then periodically use their prewritten scripts to move things off the cache and to the backing drives.

I should say it’s not really caching but effectively works to take care of this issue. Bonus since all that storage isn’t just used for cache but also long term storage. For me, that’s a better value proposition.

Goddamn I really hate that shit.

https://addons.mozilla.org/en-US/firefox/addon/don-t-fuck-with-paste/

I wonder if you and your social circle skews younger.

While I wasn’t able to find myself, my spouse, or my younger siblings, I was able to find both my parents, their friends, and older family.

There is duplicate data and address history in the dump.

# of records ≠ # of people.

deleted by creator

Forgot to add this bit in my first reply:

This is especially bad since I’m more confident that GV is less susceptible to a SIM swap type of attack since I can disable it on my account which is of course protected by real 2FA (not SMS).

Meanwhile T-Mobile has shown a few times that they’re vulnerable to SIM swap attacks.

It might not be any more private but I give out my Google voice number to people/businesses I don’t really want to hear from or suspect my data will be sold by.

What’s really frustrating is that some services detect GV (and other VOIP providers) and just say you can’t use it.

No, it’s an AI company now bro. Trust me.

Same. Upper middle class and work for a large hyperacaler.

Tesla was the only one excluded from my recent EV search. Loving the Polestar 2 so far.

To add to this point,

I was using ProtonMail when I finally got serious about generating new email aliases for everything. I went as far as upgrading my plan and started setting up SimpleLogin when I ran into the fact that I couldn’t just send from arbitrary addresses using a domain THAT I OWN. I couldn’t even reply to emails to a particular alias, FROM that alias. It looks mighty sketchy to the other party when you reply from some address they didn’t know about with the contents of someone else’s email (for all they know). Trying to explain this to others was a terrible experience.

I came across Fastmail, saw they integrated with Bitwarden via API so Bitwarden could create aliases (Fastmail calls them “masked emails”), and verified that I could both send from arbitrary addresses using my own domain and easily reply from masked addresses properly. I moved over and I’ve loved it ever since.

As I understand it, Proton is still working on the sending feature I wanted but it’s obviously not a priority for them.

IMO, Fastmail + Bitwarden is a much stronger feature set than Proton + SimpleLogin. Which is nuts considering Proton/SimpleLogin’s close relationship.

If I ever want to migrate from Fastmail, it’s a DNS change…

I’ll echo everything above. I moved from LastPass as soon as I heard it got bought by a private equity firm and I’ve loved Bitwarden. Well worth the small amount they charge.

Does indeed work fine on all of the above and I can confirm iOS is good to go.

Nah let admins admin. It would piss me off to have chosen a product just to have Microsoft effectively veto my decision as the machine owner.

If companies are going to buy stuff that crashes, let em. Don’t ask Microsoft to hand hold.