• 24 Posts
  • 59 Comments
Joined 2 years ago
cake
Cake day: February 22nd, 2023

help-circle






  • My understanding of debbootstrap is that it’s for installing a minimal system, which is very much not what I want to do when rescuing an existing system as it’d probably overwrite things I’d like to keep. And the mount commands in the docs there to bind virtual filesystems before a chroot are similar to the sorts of things I’m hoping to find a memorable shortcut for yes. However, I already know what I want to bind mount, just looking for a more convenient way to go about it in a panic. Thanks for the suggestion.


  • Yes I recognise this post was more typing than a few decades of system rescuing but it’s also more relaxing because my laptop already works and a one character typo won’t be as much of a hassle here. It’d make an unpleasant chore more pleasant if there were a simple alias for this, which I occasionally speculate on proposing but ehhh I don’t need it so often.

    So it appears this time I’m motivated enough to make a post here. But not quite motivated enough to:

    • figure out how to wedge something to do this into the filesystem on my rescue ISO (because I’ll either lose that USB or need to remember to repeat it for the next Debian stable release which might come out before I need this again — I’m thinking on a longer time scale)

    • learn how to formally engage with the Debian community (which seems lovely and welcoming but also extremely bureaucratic for sensible reasons and like I’ll have a pretty long road ahead of me to get a patch together and properly formatted and somehow applicable to all architectures and documented/internationalised and a lot of other steps I’m insufficiently motivated to undertake but perhaps eventually once I have a critical mass of contributions in mind that it feels worthwhile to dive in).




  • Thanks, that’s a significant detail. It also seems like Bluetooth 5.4 adds nothing relevant to my expected use cases: https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/whats-new-in-bluetooth-v5-4-an-overview

    Is there such a thing as a particularly good PCIE -> m.2 E key adapter or are they all pretty much equivalent? Specifically, are some antennae better than others or they’re pretty much simple enough devices that they’re going to be equivalent if they’re remotely aiming at the same spec?

    Unfortunately, it seems like Intel may be a bad bet in terms of use as an AP:

    Intel cards are only usable as access points either in the 2.4 GHz band or (very rarely) on channel 36. This hardware restriction is stemming from the fact that they don’t have the circuitry required for reacting to radar pulses, and therefore rely on the “proper” access point to tell them about radars.

    Also it needs a USB header on my motherboard as apparently the BT aspect is based on that bus. So perhaps I’d be better off with a fully USB adapter, I wonder if there is a downside to that approach… Edit: PCIE is the way to go




  • I got a nice deal on the x280 and am happy with it, was also looking at the various X1 carbon. Two criteria I had were I wanted USB-C charging (since I have those chargers around and they can handle these laptops) and a single battery (eg. the T470s I have from work is nice but it has two small capacity batteries that each cost the same to replace as the full size single ones in the carbon and x280). One thing to keep in mind is some of the earlier X1 carbon don’t support NVME SSD (I think it started with 5th gen?)

    Edit: another thing to consider is soldered RAM. Part of why my x280 was cheap was it’s only 8gb and can’t be upgraded. Since you’re looking at lighter weight things and using FOSS (and perhaps open to tinkering with things like ZRAM) that might be a useful aspect to focus on because there is probably a glut of such machines given how memory inefficient things are lately with every trivial app running a whole browser engine. OTOH, depending how many tabs you tend to have open and how many electron apps you tend to keep floating around, 8gb might start to feel cramped. Especially if you think you might want some VMs around.



  • Next time I look for a small laptop to have handy one thing I’m going to be sure to prioritise is: how much battery does it use while suspended? I’d really like to not need to have it switch to hibernate after 30m of sleep or w/e and ideally just plug it in overnight like a phone.










  • Really appreciate you taking the time to write that. I have a sense of most of that (“defense in depth” and “threat model” are good lenses to think about such things through for sure!) but what I was trying to get a better grasp on was how much risk from automated attack was a normal person without worries of an “advanced persistent threat” taking on by using a device past EOL. Like you say, “Quantifying how much of a difference it makes is not trivial” so I feel less conflicted to know that you’re comfortable with your dad taking that risk.

    I would think that the main thing at stake for a typical user isn’t just browsing history or email though but rather identity theft since a successful attacker can use the device to get through 2FA.


  • It seems like the attack surface is limited to RF (bluetooth/wifi can be turned off if one is willing to make that compromise), app install (many just use a small selection of well-trusted apps), and messaging/browser which are regularly updated if the device is properly configured. Apps that aren’t pulling in random untrusted content are far less of an attack vector (eg. one’s bank app isn’t connecting to everything, just to the bank, pinterest is hopefully escaping user content, etc.)

    Based on helpful details at the other thread (eg. Project Mainline, baseband isolation) I’m beginning to form the opinion that it is not unreasonably foolhardy for someone to continue to use an unsupported device if they are willing to make the compromises necessary to limit their exposure. Which wouldn’t necessarily mean “giving up bluetooth entirely”, just not using it when you’re in bluetooth range of an untrustworthy party eg. if you just use your headset to make zoom calls at home and are fine not having it on the subway.

    Thanks for the reply. Definitely appreciate the point that lacklustre updates mean we need to pay attention even if we’re vaguely covered by our vendor. I think you’ve convinced me to subscribe to CVEs for android too, I’ve only had alerts for my browser. Really too bad they don’t make smaller Pixels.


  • I don’t think they are things that can be fixed on the app level?

    Indeed not. So I’m trying to better understand how vulnerabilities at the system level are exploited. It seems like the attack surface is limited to RF (bluetooth/wifi can be turned off if one is willing to make that compromise), app install (many just use a small selection of well-trusted apps), and messaging/browser which are regularly updated if the device is properly configured.

    Based on this thread I’m beginning to form the opinion that it is not unreasonably foolhardy for someone to continue to use an unsupported device if they are willing to make the compromises necessary to limit their attack surface.