Interests: News, Finance, Computer, Science, Tech, and Living

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

help-circle

  • flatbield@beehaw.orgtoLinux@lemmy.mlAlternatives to VirtualBox?
    link
    fedilink
    English
    arrow-up
    11
    ·
    edit-2
    4 days ago

    Virtualbox should not run slowly in terms of compute. Make sure your allocating enough cores and memory, and VT/AMD-V is enabled in the BIOS of the host. Also Guest additions should be installed. Not sure but that might help IO speeds.

    What might be slow, Graphics may not be acceralerated. Exactly what VM software to use, what it works with, and actually getting it to work can be challanging. Installing guest drivers though is probably required.

    For Linux KVM solutions are probably preferred and more native solution but more technical to use. Getting graphics acceleration with KVM has been challenging, though may be possible. KVM is used widely on servers, but is not that desktop friendly.

    All VM solutions are resource intensive. Use containers and/or native software to reduce/avoid that.

    Edit: I myself have used VirtualBox but these days I use KVM including on my workstation.


  • flatbield@beehaw.orgtoLinux@lemmy.mlLinux is fucking awesome
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    4 days ago

    At work the only issue I ever found is the requirement to use Power Point for presentations and Word for filing patents. LibreOffice just did not translate well enough. Have not tried OnlyOffice.

    Edit: Complex Excel sheets especially with macros would be a problem too. These are not always cross version Excel compatible for that matter. One reason I shifted that stuff to Python long ago and voided that issue.


  • The system is complex plus a lot of legacy history. APTs for example (Advanced Persistent Threats). I think I have heard, that you can no longer guarantee that wiping the system and reinstalling the OS will eliminate them in all cases. They could for example burrow into the Firmware and Microcode.

    Or look at Windows, MS has had huge problem with old drivers and other stuff they run at very high permission levels. Windows is full of stuff from 25 years ago when security did not matter.









  • Servers are harder and not preconfigued if you want unattended boot. The first key has to come from somewhere typically to unlock the root partition. The other keys can then be stored on that encrypted partition and are typically referenced by crypttab for auto unlock.

    The first key can come from anywhere you want such as attached media like a flash drive, a over the network say via ssh, from a key server, or from the TPM. Or you could remotely connect to the console. There are bunch of how tos out there. It amounts to customizing the boot process and the initramfs. It is not simple. What makes sense depends on the threat model.


  • Disk encryption does not impact file sharing over the network.

    Sure if you sharing by a USB portable drive you have to unlock and lock it every time you use it. That is separate thing though.

    The bigger issues of encryption are one should have a good backup and recovery plan both for media and for the keys. One has to consider legacy planning too. How do your personal representatives access.



  • Android uses verified boot then encrypts the various profiles and the new private space seprately. This is how my GrapheneOS phone works.

    Linux has a bunch of options. Ubuntu use to suggest per user encryption by ecryptfs but has since gone to partition based encryption via dm-crypt/LUKS. I still use either or both depending though ecryptfs seems depricated/discontinued and on the next upgrade I may discontinue.

    Linux can support vaults too. Just locking certain folders. Encfs, and gocryptfs can do this for example. I use encfs though perhaps gocryptfs is a better choice these days. One can also use partition based solutions like dm-crypfs/LUKS or maybe even veracrypt too.





  • Keep in mind that you have to decide where your going to get the primary unlock key from and how your going to secure it. Standard way is to supply the primary key for the root partition on boot via the console and then the other keys are stored in the root partition.

    There are other ways to get the primary key. You can get it from a TPM, a network key server, from other media, etc. These are not standard and have to be set up. What is best depends on threat model.