• 22 Posts
  • 1.84K Comments
Joined 1 year ago
cake
Cake day: July 6th, 2023

help-circle
  • You’re going to become fast friends with the postal inspector. They will most likely require you to maintain a list of every sender and receiver.

    Ignoring that, let’s compare this to the standard I don’t want you to know where I live strategy: a post office box. Let’s say a streamer or some famous YouTuber who doesn’t want people to actually have their home address.

    Anybody can send to a post office box, they just need the address. It’s not entirely clear, but your service would require both the sender and receiver to have an account and relationship with you.

    The privacy conscious person cannot take packages directly home from the post office, they need to be scanned for trackers, air tags etc, or opened in a neutral location. Your service would send directly to a destination address, so a single air tag would destroy all privacy, unless the destination was a PO box, but at which point what is the customer benefiting from?

    I think it’s an interesting service, but I don’t see it working. The closest I would see it to is virtual post mail, or other virtual mailbox services. They scan mail when it comes in, and then email or reship that to another destination up to you. That’s kind of the privacy arbitrage layer. Otherwise there’s the post office boxes for people who want to receive without giving away their location.

    If two people want to have a transaction without any third party knowing, shipping it via the post is always difficult. Labels are scanned at every office. And I think your service will quickly have tracking requirements put onto it, quite frankly your early adopters will almost certainly only be sending illegal material.







  • I don’t believe it requires a Google account.

    I just used it on grapheneos, it does recommend you use a separate Google account for the private space, but I don’t have Google account on the phone, I was able to create a private space without any issue.

    This feels very much like a second profile, like a workspace. So now you can have three profiles on your main phone login. Normal, private, work.

    That’s nice. I would have liked it if the lock button wasn’t there, better to not reveal it at all… Upon checking the settings, there is a hide option. So yeah this is great

    I hid my private space, and now I can’t unhide it. I have to go through settings to show it again. Supposedly you should be able to open it by searching for “private space”. Might be a GOS bug.

    This is perfect for banking apps, password managers, anything that you don’t need to get notifications from













  • I wish it were that easy, there’s a lot of shared architecture in CPU design. So maybe there’s cache lines that are shared, those have to be disabled.

    Architecturally, maybe memory tagging for cash lines that in addition to looking at the TLB and physical addresses also looks at memory spaces. So if you’re addressing something that’s in the cache Even for another complete processor, you have to take the full hit going out to main memory.

    But even then it’s not perfect, because if you’re invalidating the cache of another core there is going to be some memory penalty, probably infotesimal compared to going to main memory, but it might be measurable. I’m almost certain it would be measurable. So still a side channel attack

    One mitigation that does come to mind, is running each program in a virtual machine, that way it’s guaranteed to have completely different physical address space. This is really heavy-handed, and I have seen some papers about the side channel attacks getting leaked information from co guest VMs in AWS. But it certainly reduces the risk surface