Linux

I know of CryFS and encFS which both failed an Audit.

I know LUKS and veracrypt which work but are both tedious and not useful for my use case.

I want to encrypt folders on Linux and then sync them with a cloud or just store them locally.

There is goCryptFS which is in Go, i.e. memorysafe which is good. It also failed the audit when it comes to cloud sync.

The issue: if an attacker has access to the encrypted files over time, if you always upload changes, they can crack you.

This would not be relevant for local file stores, but for synced ones it is.

There I used Cryptomator, which has many downsides though

• the app is GUI only, the CLI variant is last released 2021, which I dont consider maintained when it comes to security? Or is it?
• the GUI App is in electron, no Wayland support
• the app devs dont care about flatpak rules and store secrets outside the app container, meaning the app is unconfined by default, you need to manually add an override and it is still pretty insecure in the case that all untrusted apps are flatpaks

KDE KVaults only supports insecure algorithms, goCryptFS would be the most secure for local only stuff, but that was abandoned as a Fedora package and is only available from COPR, currently. (I should learn RPM packaging once again).

Cryptomator seems to be the only one 1. Suitable for cloud sync (not encrypting everything always again) 2. That passed an audit.

The CLI may be fine if it just interacts with the GUI app? I wonder how that would work with the Flatpak.

Do you know any alternatives?

cross-posted from: https://discuss.tchncs.de/post/23483164

On Thursday, the Bundestag's Budget Committee decided to increase the funding for the Sovereign Tech Fund (STF) with the majority of the parliamentary groups in the traffic light coalition. A total of almost 29 million euros is now available for 2025. This is around 4 million euros or 15 per cent more than initially planned by the Federal Cabinet. Almost 3.4 million euros of this is directly attributable to the STF, whose budget for 2025 was initially set at 15 million euros.

590,000 more than planned will also flow into the ‘Bug Resilience Programme’ coordinated by the STF, for which a total of 2 million euros will now be available in 2025. It is intended to ensure that security vulnerabilities in software are not only found, but also actually fixed. In total, the STF will end up with around 19 million euros, compared to just 17 million in 2024.

The SFT plays a central role in the development of open source software as a basic digital technology. Among other things, the STF managers organised competitions to promote active collaboration on open source infrastructures. The government has so far disappointed free software advocates

‘These investments make us less dependent on large providers, more resilient to digital crises and promote Germany's digital sovereignty,’ emphasised Anna Kassautzki, digital policy rapporteur for the SPD parliamentary group. Maik Außendorf, digital policy spokesperson for the Greens, emphasised that Germany is thus taking on a ‘pioneering role in open source’

The Open Source Business Alliance (OSB) and the Free Software Foundation Europe (FSFE) had expressed their disappointment with the course taken by the Ampel in 2022. In its coalition agreement, the government had explicitly emphasised the importance of open standards and interfaces as well as open source for digital sovereignty. However, there are no concrete plans for an alternative hyperscaler, especially for cloud projects.

Instead, dependencies on Microsoft, for example, would be further cemented. The federal government's licence costs for proprietary software providers have recently reached a high level in the billions. The OSB Alliance has just called for the administration to switch its IT completely to open source.

Translated with DeepL.com (free version)

cross-posted from: https://feddit.org/post/3679507

What has your experience with Linux been like so far? How long has been your Linux journey? Mine began while I was studying computer science, and I've been in love with Linux since.

cross-posted from: https://lemmy.ml/post/21244508

The Kubuntu Team is happy to announce that Kubuntu 24.10 has been released, featuring the new and beautiful KDE Plasma 6.1 simple by default, powerful when needed.

Codenamed “Oracular Oriole”, Kubuntu 24.10 continues our tradition of giving you Friendly Computing by integrating the latest and greatest open source technologies into a high-quality, easy-to-use Linux distribution.

Under the hood, there have been updates to many core packages, including a new 6.11 based kernel, KDE Frameworks 5.116 and 6.6.0, KDE Plasma 6.1 and many updated KDE gear applications.

I hear that a lot but, how bad is it really? Does it affect you (if you use Debian)? Aren't there ways to install newer versions of most things that actually matter?

cross-posted from: https://lemmy.ml/post/21161182

Plasma 6 has come into its own over the last two releases. The wrinkles that always come with a major migration have been ironed out, and it’s time to start delivering on the promises of the new Qt 6 and Wayland technology platforms that Plasma is built on top of.

Plasma 6.2 includes a smorgasbord of new features for users of drawing tablets. It implements more complete support for the Wayland color management protocol, and enables it by default. There is also improved brightness handling for HDR and ICC profiles, as well as HDR performance. A new tone mapping feature built into Plasma’s KWin compositor will help improve the look of images with a brightness or set of colors greater than what the screen can display, thus reducing the “blown out” look such images can otherwise exhibit.

When it comes to power management You can now override misbehaving applications that block the system from going to sleep or locking the screen (and thus prevent saving power), and you can also adjust the brightness of each connected monitor machine separately.

Plasma’s built-in app store and software management tool, Discover, now supports PostmarketOS packages for your mobile devices, helps you write better reviews of apps, and presents apps’ license information more accurately.

In Plasma 6.2, KDE have overhauled System Settings’ Accessibility page and added colorblindness filters. They've also added support for the full “sticky keys” feature on Wayland.

This and more in full anounncement and changelog.

I want to create a collage of 20 screenshots from a video, arranged in a 5x4 grid, regardless of the video’s length. How can I do this efficiently on a Linux system?

Specifically, I’d like a way to automatically generate this collage of 20 thumbnails from the video, without having to manually select and arrange the screenshots. The number of thumbnails should always be 20, even if the video is longer or shorter.

Can you suggest a command-line tool or script that can handle this task efficiently on Linux? I’m looking for a solution that is automated and doesn’t require a lot of manual work.

Here's what I've tried but I only get 20 black boxes:

#!/bin/bash

# Check if input video exists
if [ ! -f "$1" ]; then
    echo "Error: Input video file not found."
    exit 1
fi

# Get video duration
duration=$(ffprobe -v error -show_entries format=duration -of default=noprint_wrappers=1:nokey=1 "$1")

# Calculate interval between frames
interval=$((duration / 20))

# Extract 20 frames from the video
for i in {1..20}; do
    ffmpeg -ss $((interval * ($i - 1))) -i "$1" -vf scale=200:-1 -q:v 2 "${1%.*}_frame$i.jpg"
done

# Create collage
montage -mode concatenate -tile 5x4 -geometry +2+2 "${1%.*}_frame*.jpg" output_collage.jpg

# Clean up temporary files
rm "${1%.*}_frame*.jpg"

echo "Collage created: output_collage.jpg"

• Many Porcelain commands that internally use the merge machinery were taught to consistently honor the diff.algorithm configuration.

• A few descriptions in "git show-ref -h" have been clarified.

• A 'P' command to "git add -p" that passes the patch hunk to the pager has been added.

• "git grep -W" omits blank lines that follow the found function at the end of the file, just like it omits blank lines before the next function.

• The value of http.proxy can have "path" at the end for a socks proxy that listens to a unix-domain socket, but we started to discard it when we taught proxy auth code path to use the credential helpers, which has been corrected.

• The code paths to compact multiple reftable files have been updated to correctly deal with multiple compaction triggering at the same time.

• Support to specify ref backend for submodules has been enhanced.

• "git svn" has been taught about svn:global-ignores property recent versions of Subversion has.

• The default object hash and ref backend format used to be settable only with explicit command line option to "git init" and environment variables, but now they can be configured in the user's global and system wide configuration.

• "git send-email" learned "--translate-aliases" option that reads addresses from the standard input and emits the result of applying aliases on them to the standard output.

• 'git for-each-ref' learned a new "--format" atom to find the branch that the history leading to a given commit "%(is-base:)" is likely based on.

• The command line prompt support used to be littered with bash-isms, which has been corrected to work with more shells.

• Support for the RUNTIME_PREFIX feature has been added to z/OS port.

• "git send-email" learned "--mailmap" option to allow rewriting the recipient addresses.

• "git mergetool" learned to use VSCode as a merge backend.

• "git pack-redundant" has been marked for removal in Git 3.0.

• One-line messages to "die" and other helper functions will get LF added by these helper functions, but many existing messages had an unnecessary LF at the end, which have been corrected.

• The "scalar clone" command learned the "--no-tags" option.

• The environment GIT_ADVICE has been intentionally kept undocumented to discourage its use by interactive users. Add documentation to help tool writers.

...

cross-posted from: https://lemmy.nz/post/15137443

Hello everyone!

I'd like to announce the start of development and the public availability of what we currently refer to as Leap 16.0 pre-Alpha. Since this is a pre-Alpha version, significant changes may occur, and the final product may look very different in the Alpha, Beta, Release Candidate, or General Availability stages. The installer will currently offer you Base, GNOME, and KDE.

Users can get our new Agama install images from get.opensuse.org/leap/16.0. The installer will currently offer you Base, GNOME, and KDE installation.

Leap 16.0 is a traditional distribution and a successor to Leap 15.6 with expected General Availability arriving in the Fall of 2025.

We intend to provide users with sufficient overlap so that 15.6 users can have a smooth migration, just like they're used to from previous releases.

Further details are available on our roadmap. The roadmap is subject to change since we have to respond to any SUSE Linux Enterprise Server 16 schedule changes.

Users can expect a traditional distribution in a brand new form based on binaries from the latest SLES 16 and community packages from our Factory development codebase.

There is no plan to make a Leap 15.7, however, we still need to deliver previously released community packages from Leap 15 via Package HUB for the upcoming SLES 15 SP7. This is why there are openSUSE:Backports:SLE-15-SP7 project and 15.7 repos in OBS.

The target audience for pre-Alpha are early adopters and contributors who would like to actively be part of this large effort. Adopters should consider booting Agama Media from time to time just to check compatibility with their hardware.

For non-contributor users, I highly recommend waiting until we have a Beta, which is expected in the late Spring of 2025.

Specifically for Agama I highly recommend using github.com/agama-project and collaborating with the YaST team on suggestions and incorporating any changes.

For the rest of the components, the workflow isn't changing; just select version 16.0 for bug submissions.

Feature requests will be reviewed every Monday at a feature review meeting where we'll convert code-o-o requests into JIRA requests used by SUSE Engineering where applicable.

The factory-auto bot will reject all code submit requests against SLES packages with a pointer to code-o-o. You can get a list of all SLFO/SLES packages simply by running osc ls SUSE:SLFO:1.1:Build.

Just for clarification SLFO, SUSE Linux Framework One, is the source pool for SLES 16 and SL Micro 6.X.

I highly recommend using code-o-o to co-ordinate larger community efforts such as Xfce enablement, where will likely need to update some of SLES dependencies. This allows us to share the larger story and better reasoning for related SLES update requests. The list of features is also extremely valuable for the Release article.

For quality control, we have basic test suites based on Agama installations in Leap 16.0 job group. Later, we plan to rework the existing Leap 16.0 Images job group for testing the remaining appliance images.

The project where we maintain community packages is subject to change as we have not fully finalized yet how to make Package HUB; we may use a similar structure with Backports as in 15.3+).

Further test suite enablement is one of the areas where we currently need the most help. Related progress.opensuse.org trackers poo#164141 Leap 16.0 enablement and poo#166562 upgrade from 15.6.

Another area where you can help is new package submissions and related maintainer review of package submissions to Leap 16.0. These reviews make sense as we'd like to check with maintainers whether that software in a given version makes sense for inclusion into Leap 16.0, rather than blindly copying all packages over.

Do you want to help us on this front? Spread the news and feel free to join the #openSUSE_Marketing Telegram channel(https://t.me/openSUSE_Marketing)! https://en.opensuse.org/openSUSE:Marketing_team

Many thanks to all who helped us to reach this point.

Lubos Kocman on behalf of the openSUSE Release team

cross-posted from: https://lemmy.world/post/20535629

ZLUDA is a compatibility layer for Nividia’s CUDA on other processors

cross-posted from: https://slrpnk.net/post/13942074

cross-posted from: https://biglemmowski.win/post/2784381

I've remembered this exists and there seems to be some very recent activity in the repo so if you didn't know what was possible with TUI graphics now you know! (recommended watching with sound :)

Official site: https://notcurses.com/
Repo: https://github.com/dankamongmen/notcurses

PS: dank (the guy behind it) is definitely one of a kind, just read the releases haha

PPS: here is a doom running through notcurses in the terminal: https://www.youtube.com/watch?v=a_w5rh3c76g

The Xfce 4.20 schedule can be found on the Xfce.org Wiki. Expect Xfce 4.20 to offer up more Wayland support improvements, bug fixes, translation updates, and other modernization improvements. The developers have been hoping that Xfce 4.20 will feature usable Wayland support while retaining X11 compatibility.

I was testing out Debian in a VM and trying to set up Timeshift to see if I can make snapshots and Timeshift didn't work because of how Debian sets up volumes with BTRFS.

Apparently Timeshift uses Ubuntu's way of setting up volumes and nothing else. Check this video to find out how to install Debian on BTRFS so it works with Timeshift.

Hello,

So I've been a long time Linux user (since 2000) and for the past 20 years, I've been using exclusively Ubuntu and its flavours. Lately I've been seeing posts and articles about how Ubuntu's Snaps are ruining the user experience and causing a lot of discontent. Since I was on the verge of scrapping Windows on my machine and going full Linux.

I started to explore the different distros out there. I installed Linux Mint, (K/L)Ubuntu, Ubuntu Budgie, Debian, Endeavour OS (Arch), Bazzite, Fedora, OpenSuse Tumbleweed, Elementary OS, Fedora Kinoite, Nobara, etc. I wanted to see which one could be my next long run install it and forget it distro. In the end, I was already comfortable with Kubuntu and the few tests I tried in a VM seemed like it was still pretty solid and I really didn't have any reason to change. So I installed Kubuntu as my main and only OS... And I'm starting to regret it dearly.

Snaps really is awful. And the only reason is because Canonical is forcing it on its users. Modifying APT to install Snap packages instead of Debian packages?! And having certain software exclusively available as Snaps? Firefox, Thunderbird, CUPS, FFMpeg, and some of their own utilities like Firmware Updater, and even some KDE core stuff apparently?

So as I was finishing configuring my freshly installed Kubuntu, I was having problems with SDDM. My computer would completely freeze whenever I logged out. Like nothing worked except the power button on my PC. I installed the NVidia drivers and that appeared to have fixed it. I also installed ZSH and set it as my default shell. However, upon reboot, I realized all my Snap based apps were gone from my application menu. I couldn't even set them as default apps in the control center. Firefox being one of them and that's why I noticed.

After checking in the Discover app, I saw it was still installed. I noticed a bunch other ones were missing, but they all appeared as installed. I tried uninstalling Firefox and reinstalling, but that didn't work. I don't know whether it's Snap or KDE that's broken. So I started removing all the Snap variants and installing their Flatpak counterpart instead. But I soon realized this couldn't be done with all software. Like CUPS. The printing system. It's only available as a Snap??? You can't even install it as a Debian package? Some apps are only available as Snaps and they won't show up in my KDE applications menu or anywhere else.

This is incredibly frustrating and disappointing. I feel like I'm being pushed in a corner by Canonical. I'm afraid I really have to switch distributions after all these years. I think I'll be installing Debian 12 stable. Besides, with Flatpak I can get fairly updated applications instead of the .deb packages. So the "old packages" reputation becomes almost irrelevant.

UPDATE:

So installing zsh and setting it as my default shell is what broke Snap. Apparently, zsh doesn't run any of the /etc/profile and /etc/profile.d/ scripts which run scripts that set up environment variables for snap and flatpak and stuff. Adding the following line to /etc/zsh/zprofile fixed my problem:

emulate sh -c 'source /etc/profile'

Anyway, it's still bullshit.

UPDATE 2:

Thanks @[email protected] for the advice. I've since reverted my default shell to bash in my /etc/passwd file and configured my console app to start ZSH instead to avoid any further problems. #LessonsLearned

Just got back from a long but enjoyable day as I've convinced yet another to escape Windows and join Linux

Hopefully they should feel more comfortable with building their own computer and using Linux in general as I went through the entire process with them; from having them insert their new CPU all the way to boot switching between Linux and Windows 10 via ~~BIOS~~ UEFI

They've got a few proprietary requirements remaining (hence the dual boot) but 95% of their apps are now on PopOS (they're planning to switch to Arch in about 3-4 months after some certain conditions are met)

Just wanted to share this as I've missed posting on the fedicomms and also wanted to provide an update for afking🤗

Anyways here's another to Windows's death ~~knell~~ null!🎉