Kdenlive is the top-ranked FOSS video editor on AlternativeTo.

I agree with that ranking, having also tried 5 or 6 of the other entries on the list.

Trust isn’t really the point. Everyone knows Israel and Hamas don’t trust each other. I’m more concerned with whether the violent conflict can be reduced, and a stable peace achieved.

Are Hamas’s arms doing Gaza any favours? Not that I can see.

AFAICT, if Hamas disarmed:

• Israel’s only(?) excuse for mass military action in Gaza would disappear.
• International support (already shaky) for Israeli military presence in Gaza would decrease.
• One or more of Australia, Canada, Costa Rica, Ecuador, Honduras, Israel, Japan, New Zealand, Paraguay, Trinidad and Tobago, the United Kingdom, the United States, or the European Union might end their designation of Hamas as a terrorist organisation, which could in turn increase the aid and other international support available to Gaza.

If you think I’m wrong, I’d be glad to know why.

Terrorism arises in defense to oppression.

Technical point: that isn’t exhaustively true. Terrorism can be, and sometimes is, committed against vulnerable parties by more privileged ones.

Progress report 1

• I’m ruling out HMAC-SHA1, because:
  • Plain vanilla HMAC-SHA1 uses a shared secret. I don’t want the PC/server to have a copy of the credential. May also be susceptible to MITM/relay attacks.
  • Rolling-code HMAC-SHA1 only partially solves those problems.
  • Encrypted rolling code HMAC-SHA1 solves those problems, but I haven’t found a reliable source for using it with LUKS.
• If using systemd, pick FIDO2:
  • Avoids flaws of HMAC-SHA1.
  • Native support in systemd, so “future-proof”.
  • Wider support than OpenPGP. More HST vendors to choose from, including cheaper options than NitroKey or Yubikey: useful if each sysadmin (or colleague, or relative) needs an HST.
  • Compatible with QubesOS.
• Otherwise, OpenPGP:
  • Like FIDO2, solves HMAC-SHA1 flaws.
  • However:
    • smartcard-key-luks seems unmaintained on GitHub and on GitLab.
    • LUKS with OpenPGP isn’t well-documented for non-Debian-based distros.
• TBD: Clevis/Tang:
  • Remote/network-based unlocking.

Thank you for this! That thread is helpful in itself, and also links to other relevant resources - including by Lennart Poettering (controversial guy, but the canonical source on systemd).

Thanks! I didn’t know they were normally made of composites.

Looks like there are some ways (1, 2) to reuse/recycle the latter, but I agree wood would be better for this.

Aren’t turbine blades usually aluminium? How is wood more “recyclable” than that?

This coverage has a better headline: Trump blames Minnesota governor for cyberattacks against the state. Cites no evidence.

Funding restrictions and denialism, plus starting a war against a cyberattack-capable nation, made infrastructure attacks inevitable.

Security researchers have been publicly raising the alarm about SCADA vulnerabilities for 20+ years.

If it’s a server for self hosting you definitely don’t want anything that requires interaction at boot.

Depends on use-case. If you only plan to boot it when you’re physically present, it’s fine.

i believe a much better secure layer is something similar to what Novacustoms, Purism attempt to do: verify if somebody else not you try to access the laptop.

You’re thinking of Heads, which I agree is ideal for supported motherboards.

tang

Thanks. TIL about Clevis/Tang.

I can only see three ways to get FOSS firmware on your printer:

1. If someone reverse engineers the firmware to create a FOSS version.
2. If the Software Freedom Conservancy, who recently raised funds to tackle Bambu Labs’s license violations, finds a violation in BL firmware and succeeds in legally compelling BL to release the corresponding source code.
3. If you sell your BL printer and replace it with one that already has FOSS firmware.

I read them before writing my OP. I’m still not sure what you’re getting at.

I would be grateful if you could say what you mean, instead of initiating an oblique guessing game.

Yes. Here are some common self-hosting scenarios:

• Home server containing family files: scans, photos, device backups, …
• Office server containing business files: sensitive documents, device backups, …
• Web or email server containing websites, Fediverse instances, emails, etc

In all those cases, full disk encryption (FDE) is a sensible precaution to protect the data in case the server is physically stolen.

Linux is probably the most common OS kernel for self-hosting. On Linux, LUKS (Linux Unified Key Setup) is probably the best FDE system. It’s mature and reliable. But anyone self-hosting a Linux server with LUKS FDE is faced with the question of where to store the keys.

Hardware security tokens (HSTs) are widely considered a safer place for keys than SSDs, HDDs, or USB storage. They follow the smartcard principle: a private key can be written to an HST but not read from it (security vulnerabilities excepted). Instead, they implement cryptographic algorithms to prove possession of the private key. So, anyone self-hosting a Linux server with LUKS FDE should strongly consider storing their private key(s) on an HST.

However, there is more than one way to do that. Hence the question in my OP.

Which of the 4 recipes I posted are you referring to as “this”?

Thanks, please post relevant steps if you have specific recommendations.

Great to see Europe leading the way here. If other jurisdictions pass similarly responsible legislation, then those jurisdictions will gain similar benefits.

The article has an interesting passage about how Irish aluminium is currently being sold to Russia for weapons, and the EU is (rightly) trying to stop this.

For plain text & Markdown, you don’t even need Collabora. Since 2019, NextCloud has a built-in collaborative text editor.