• 0 Posts
  • 37 Comments
Joined 2 years ago
cake
Cake day: June 25th, 2023

help-circle
  • Fair enough, I got the wrong impression with the post (which I did read) finishing with

    It is not impossible to circumvent these issues, for instance by paying for a jmp.chat phone number with monero XMR. In this case you don’t actually have the sim, but rather access it remotely over XMPP. If you do this over Tor very little can be used against you.

    and so on, which I found wanting from a privacy perspective at the implied threat level. No phones (or perhaps faraday bags, or aircraft mode, if tested, depending on threat model) is a much more astute take home, hence the spycraft suggestion.

    Anyhow, best of luck.



  • So, your key takeaway seems to be getting an untraceable phone number. From an opsec point of view I see a few problems.

    First, this is implicitly aimed at going against state level actors, which is a whole other game than random internet services. With that in mind…

    You assume TOR is actually anonymous, but it has been shown that with enough compromised exit nodes that fails. It’s also a NSA project originally, which may or may not be relevant, the code may be good and is open and has had eyes on, but at the least shows they are intimately familiar with it.

    You assume acquisition of Monero is uncompromised and untraceable. Perhaps cash at a machine might be pretty good, but a camera could easily invalidate it, or the machine itself be compromised, wouldn’t be hard to imagine a profit motive or false flag driving that.

    What’s the security implications of the XMPP protocol ? Just using TOR may not be enough (I don’t know, just asking the questions). What about the other end of the phone call?

    One approach, especially for local efforts, is just using old school spycraft, dead drops, one time pads etc.

    You asked for feedback.



  • Seems like data integrity is your highest priority, and you’re doing pretty well, the next step is keeping a copy offsite. It’s the 3-2-1 backup strategy, 3 copies, 2 media (used to mean CDs etc but now think offline drives) 1 offsite (in case of fire, meteor strike etc), so look to that, stash a copy at a friends or something.

    In your case I’d look at getting some online storage to fill the offsite role while you’re overseas (paid probably, but a year of 1 or 2 Tb is quite reasonable) leaving you with no pressure on the selfhosting side, just tailscale in, muck around and have fun, and if something breaks, no harm done, data safe.

    I’ve done it for what seems like forever and I’d still be worried about leaving a system out of physical control for any extended period of time, at the very least having someone to reboot it if connectivity or power fails will be invaluable, but talking them through a broken update is another thing entirely, and you shouldn’t make that a critical necessity, too much stress.







  • MalReynolds@slrpnk.nettolinuxmemes@lemmy.worldWhats his problem?
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    2 months ago

    I have exactly this (AM4, 7800XT, 3440x1440 monitor) running bazzite. Almost every game I have maxes 165Hz, works great for LLM inference too, really the nutso expensive stuff is only necessary for 4K+, which I find diminishing returns at present, LLM training (rent a GPU instead), and probably modern VR. Just to let you know you’re barking up the right tree. :)

    Oh, and the 7800XT idles / youtubes ~ 14-20W, 7 with the monitor off. I’m actually using it as a backup NAS / home server in down time, system pulls ~40-45W at the wall and I haven’t even gone deep into power saving as it’s a placeholder for a new homelab build that’s underway.







  • MalReynolds@slrpnk.nettoLinux@lemmy.mlope, kernel panic :/
    link
    fedilink
    English
    arrow-up
    4
    ·
    2 months ago

    You’ll be wanting sudo ostree admin pin 1 seeing as 0 was broken. Double check with rpm-ostree status.

    Proceed to rpm-ostree update, if that does nothing it means 0 is up to date, personally I’d just wait for a new update using the working deployment, but you can blow away 0 and get it again if you’re keen.