• 2 Posts
  • 24 Comments
Joined 2 years ago
cake
Cake day: June 30th, 2023

help-circle




  • TBH even the way you phrased your question kind of proves it’s orthogonal. Yes, you can have the full matrix:

    encrypted | backed up
    ----------|----------
           no |        no
           no |       yes
          yes |        no
          yes |       yes
    

    In each case, you have a different set of problems.

    • Encrypting a particular medium only means that it’s going to be harder to gain access to the data on that medium (harder for everyone, but trillions of less harder for someone who knows the password.
      • That’s regardless of whether you also have a backup.
    • Backing up just means that a copy of the data exists somewhere else.
      • That’s regardless of whether this or the other copy is encrypted.

    Sure, eventually, the nature of your data’s safety will be affected by both.

    Disclaimer: I’m by no means a security expert, don’t take what I write here as advice!

    Eg. I encrypt my disks. When I do, I basically encrypt everything, ie. all partitions (except /boot). Then on those partitions, most of the data is not worth backing up since it’s either temporary or can be easily obtained anyway (system files). Well, some of the data is backed up, and some of that even ends up on disks that are not encrypted (scary, I know!) :)

    To be fair, just encrypting the disks does not solve all. If someone broke to my house, they would with almost 100% chance find my computer on, which means that the disks are not encrypted (technically still are, just that LUKS provides unencrypted versions as well…) So the barrier they would have to face would be basically just the desktop lock.

    For that reason I don’t encrypt hard drives on my remote server, since the server is always running in a virtual environment so by definition anyone who’s maintaining the hardware can already open files from the unencrypted drives, ie. I think it would be pointless.


  • but if somebody is eager and skilled enough to break in my home to get my disks, honestly they “deserve” the content.

    The problem with “my disks” is there’s always some other’s people on it, in one way or another.

    But of course, it’s your call. We all have gaps in our “walls” and it’s not like I’d be pretending that LUKS is all that matters.


  • I do, laptops and workstations.

    It’s just too easy not to, and there’s almost no downsides to it. (I only need to reboot, once a month or two.)

    Well, unless you consider the possibility of forgetting the password a downside, so for that reason I keep the password in a password manager.

    In case my laptop was stolen, there would quite a couple fewer things to worry about. Especially things like client’s data which could be under NDA’s, etc…


  • More nuanced reply: I do tend to complain

    • less about certain bugs and limitations, where I can understand that the problem is harder than it seems
    • and more about others, where I have to imagine a poor intern dragged around by bad advice for several sprints, finally marking the task done (forehead sweating and all), even though they did not really know what they were doing even for a minute.

  • Thank you for the post, especially the interview links; I’ll check them out.

    I’m sorry, but it is a software engineering term. Maybe not from the area you are familiar with, but cloud native was the raging buzzword…about 10 years ago

    I guess my point would be the same, but conclusion is the opposite. Yes, I’ve heard “cloud native” tons of times, but that is the problem with buzzwords: because they are overused (and often used a lot by people who don’t really know what they are talking about), for many people like me, they lose meaning in that period. It’s like “AI” nowadays, or “NFT” few years ago. The term loses its specificity (if it ever had one), and collects all the “bad smell” from people overusing – not just the term but sometimes also the methodology behind.

    Honestly, for me rpm-ostree and Flatpak would be excellent terms to convey the architecture of Bazzite. I did have to go to here and to Wikipedia to learn that.


  • The buzz word is not aimed at the regular gaming nerd. It is aimed at gaming nerds who are also developers.

    I’m a gaming nerd and a developer and I did not get it.

    Lot of explanations in this thread seem to be: “we just use cloud spec for testing and deployment”. That’s absolutely fine.

    But context matters a lot. If I open a main page of the project, I don’t have my developer’s hat on. I will assume that the main page is intended to describe the core value of the project. What the heck does “cloud native” mean? To a gamer? Pretty much nothing. (At best they will think you want to run their games like Google Sheets, I guess). To a SW engineer with 8 years of experience in distro QE? Pretty much nothing. It’s the kind of lingo you hear on meeting with C-suites. (Before you go back to your office, sit down with your PO and tech lead and try to decrypt/guess what they want us to do.) I mean, seriously, who talks like that? I’m pretty sure it’s neither SW engineers nor gamers.

    Don’t get me wrong, I appreciate your explanation, it’s really well written. Given what I’ve learned from this thread, Bazzite seems like worth trying out.

    Just the marketing seems weird. I mean, the whole reason I even found the page is because I’m someone who cares about whose SW I’m using and how it’s ran and maintained. And I do understand tech. Tossing around meaningless terms at me is not going to make me feel a lot of trust…





  • I suspect the “cloud native” marketing term in this context just means you can run the same image file in a vm, vps, bare metal, whatever.

    …yeah that’s what makes it suspicious. Alone it can be a good thing but why rush to mention it for a fricking gaming/home distro? As if running gaming/home distro anywhere else than as close to the hardware as possible was somehow inherently normal or even good.

    (The idea of cleanly separating “user user space” does sound inherently good, if achievable…)

    Again, who are they marketing to?



  • Thanks for sharing, I haven’t read it yet but it looks like there’s lot of interesting stuff there. (Definitely not a “14 min read” 😉 )

    I moved from (10+ years) Vim to Neovim about last year an I actually used Kickstart, but honestly, while it’s nice to give you a start (especially from people coming from other, more “rich-by-default” editors), there definitely is the problem that I don’t get to really understand how my own config works. …which makes it harder to debug problems but also to ask for help.

    And problems will inevitably come, especially with such an active ecosystem of plugins.

    I’ve been planning to do a deeper dive into my config–perhaps even rewrite parts of it—so your article is going to be a good source.







  • netvor@lemmy.worldtoLinux@lemmy.ml33 years ago...
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    10 months ago

    Funny how he made it basically for his desktop computer.

    33 years later, and Linux is dominating in every part of the OS world except … the desktop.

    (I’m paraphrasing his quote – he said something like this years ago, can’t find it, though.)

    (Edit: to be more fair with quotes, it might be the case that I “hallucinated” the quote. he might not have said that, or he might have just said part of it and other part would be someone else’s comment. This cio.com article is probably a better source on his position )