Project maintains their tools in , giving them a base platform delivered with and the rest of the Debian users get a better maintained Debian.

I'd like to have something that automatically convert links to the preserving version in the browser. Like play links in , etc. There seems to be things like but for me the question is which one to trust, is maintained, works well enough, etc. Once I find a tool that I think it generally applicable, then I work to get it into so its easy for others to make this decision. Is there a browser extension for this that is worth getting into Debian?

After using /#macOS from 1994-2012, I reached the same conclusion as Ken Thompson: "I've become more and more depressed, and what is doing to something that should allow you to work is just atrocious... And I have come, within the last month or two, to say, even though I've invested, you know, a zillion years in Apple — I'm throwing it away. And I'm going to Linux. To in particular."

As a , I'd like to say: Welcome!

Just tagged v2.2.1 of fdroidserver tools package, and uploaded it to, , and our PPA. This version has passed autopkgtest in Debian/bookworm, so it looks like it should make it into bookworm without further work

was almost mentioned at : one key point was that mobile operating systems in 2008 were in a race to get developers. and were tiny newcomers with no developers. The idea from app stores came from free software and hackers. APT started in the 90s, was on iOS when was still saying web apps were the only way. And of course, used as a key strategy to get interested in their platform.

Started syncing work on the package between and , bookworm's libsmali-java provides an update over Kali's own smali package, but there is still a bit more to be done. Hoping this is the start of more cooperation!

Just uploaded to the key inspection tools 2.7.0 and the latest from git, ahead of 2.5.2. All sorts of tools like and more rely on these for inspecting Android APK files.

Just uploaded v3.4.0 to . It is an easy way to get started with analyzing APK files to see what is in them.

and require signature verification, and is built on top of 's APK signing. This improves things a lot but does not mean they are immune. Debian and F-Droid repos can still override packages lower priority repos. It could make sense to have a "no overrides allowed" setting, but that would restrict useful features. Maybe F-Droid could implement "no new signing keys when overriding" rule by default, I wonder how much that would break what people are doing now? 2/2

Show thread

I'm sad to say that my new still needs non-free firmware blobs for working WiFi, Bluetooth, audio, and power management. Now will include those in the installer. Are we losing this fight? At least the graphics driver is and included in upstream Linux, that is progress. I specifically avoided for that purpose.

How are others feeling on the firmware blob fight?

@ljacomet I just saw your slides for your talk "Protecting your organization
against attacks via the
build system", a great overview! I'm a dev who has worked on packaging . We'd love to make it as close to your version as possible. There is a proprietary build dependency that blocks that from happening.

Hosting code with automated publishing into well known namespaces is looking more and more like a broken model. A better approach is human verification of package names like in , @fdroidorg, . Then other pieces can be safely automated

I'd love to see data on what verified boot actually stops. The ideal malware implants itself at the lowest level possible. Is there good public data on these kinds of exploits on etc? Does standard spyware do that? Writing to /system requires a root exploit, lots of malware never gets root. How often there are vulns in itself. Here's a real world full of verified boot:

created an ecosystem where the software available there is reviewed and trusted, so the system can prioritize flexibility over security. In Play, there are many apps we feel forced to use, despite knowing they are unethical or are tracking us. Google responds by locking down to reduce data leaks, which also reduces the system's flexibility. puts the user in control so we can build user-friendly systems without being forced into bad decisions.

If anyone is looking for a / project to hack around with, jtorctl now builds with (from or ), , and with sketches of Ant. The idea is that if all the build tools make the same JAR, no need to trust the build tool. or

Key parts of the tools package suite no longer build on anything but x86. This is also true with the new 10.0.0 version. I'd love to see the and packages make it into . We need contributors! If you can help, see:

image/svg+xml Librem Chat image/svg+xml