Unsafe

joined 10 months ago
[–] Unsafe@discuss.online 2 points 9 months ago

Nvim. autopair.nvim let's you autoclose "begin[]" macros. Luasnip let's you create custom snippets for every macro you use. I also use Emmet LSP for inline svg.

[–] Unsafe@discuss.online 1 points 10 months ago

Some seem to use Debian.

[–] Unsafe@discuss.online 1 points 10 months ago

Linux Libre makes Guix unusable on most hardware. It also requires much effort to configure. Learn scheme, how to use shepherD, etc.

[–] Unsafe@discuss.online 2 points 10 months ago* (last edited 10 months ago)

It's really cool, when automation tools create more problems than they actually solve.

[–] Unsafe@discuss.online 1 points 10 months ago* (last edited 10 months ago)

There is really no reason to implement extensively audited runC in C, but the Dev only has the journey, no goals.

[–] Unsafe@discuss.online 3 points 10 months ago

Ncmcpp, MPV with scripts

[–] Unsafe@discuss.online 2 points 10 months ago (2 children)

Not really. Void, alpine, gentoo are the only usable ones(besides non-systemd forks of arch and Debian). These are the only ones maintaining enough packages, providing enough documentation, not being just poorly maintained forks of X distro.

[–] Unsafe@discuss.online 2 points 10 months ago (2 children)

I deleted it. No need for two almost identical posts to exist.

[–] Unsafe@discuss.online 0 points 10 months ago (4 children)

Really? Didn't known. Lemmy.today seems to not work properly on mobile apps.

[–] Unsafe@discuss.online 0 points 10 months ago

It's a matter of probability. Probability of discovering vulnerabilities in multiple tools doing same thing is higher than in just one.

[–] Unsafe@discuss.online 0 points 10 months ago (1 children)

in there.

Whonix Dev quote:

Use a distribution with an init system other than systemd. systemd contains a lot of unnecessary attack surface... ©Linux Hardening Guide

[–] Unsafe@discuss.online 1 points 10 months ago

Because they don't execute million lines super thoroughly checked shell code or why exactly? Without any explanation total FUD.

Because they are not merged with journaling system, job scheduler and watchdog. More features→more attack surface.

 
  • Systemd-init has a larger attack surface compared to runit, openrc, or sysVinit.

  • Systemd-logind relies on systemd, so we need to adapt it for non-systemD distributions to ensure compatibility with certain applications like GNOME.

  • Udev also depends on systemd.

  • SystemD is specific to Linux, which makes porting software to *BSD even more challenging. It's uncertain what the future holds, and there may be circumstances where Linux becomes unusable for you (e.g., compatibility issues with your laptop). Having a good alternative that doesn't require relearning everything is generally beneficial.

  • SystemD-based distributions often come with more than just "systemd-init." They include additional components like logind, resolved, networkd, systemd-timers, etc. However, many people still prefer using the alternatives they were accustomed to before systemd became popular, such as dhcpcd and cron. Consequently, having both sets of tools installed can increase the attack surface.

view more: next ›