[–] 1 point 1 year ago

This reminds me of prop 65. It's so broad that everything is labeled as causing cancer to the point of being a worthless label. I suspect this will have a similar problem on top of the privacy ones

  • source
  • [–] 16 points 1 year ago* (1 child)

    The reason for initramfs is because if you build your block or filesystem drivers as modules the kernel can't boot without loading the modules and can't load the modules without said modules and therefore causing a chicken and egg problem. Reading a folder without all necessary boot drivers just isn't possible. That's why the bootloader is responsible for loading initramfs into system memory, the kernel can read it with 0 drivers required. Getting rid of it can be done but ALL of your boot drivers need to be statically linked into the kernel image so that the kernel doesn't need any modules to get the rootfs mounted. Ironically EFI can be used to obsolete initramfs in theory since the kernel can read data from the ESP without any drivers being required so putting modules in a folder on the ESP would work for EFI enabled systems

  • source
  • parent
  • context
  • [–] 2 points 1 year ago* (2 children)

    OpenVPN operates in kernel space as of 6.16. Well specifically for the data channel. Control channel is still managed in userspace so you don't have to do asymmetric TLS in the kernel. This also reduces the overhead and increases performance substantially. It is slightly more complicated to setup but barely tbh (I'm speaking from the server side). Is the crypto outdated? Not as far as I'm aware.

  • source
  • parent
  • context
  • view more: ‹ prev next ›