Let's dust off our Amigas, hook up our mice and joysticks, and see what elegant software and hardware could do back in the 80s and 90s!

I have been known to talk anybody I held presentations with into using odpdown.

Hackweek 21?

As the automation became a standard within Maintenance QA work, I would like to became more familiar with the whole magic behind. Plan is to go through internal docu a try to setup openQA and write some simple tests (and adjust the docu once there are any gaps):

Project Description

Project Description

Plan

The goal of Project MySelf is to build a system to collect data about yourself in a safe and private way, so that you control your data and you can decide what happens with it.

The Linux kernel already has cryptographic support for signature verification on data. This is used to digitally sign kernel modules at build time, and verify integrity and provenance at load time. Likewise the 802.11 subsystem on the Linux kernel had historically in parallel prior to Linux's own kernel signing facility implemented and integrated support to verify file integrity and provenance for use on the Linux regulatory database. The 802.11 subsystem's components that provide this facility are CRDA and wireless-regdb. CRDA and wireless-regdb technically are split up as two separate trees for development, wireless-regdb helps provide the 802.11 regulatory database while CRDA exists as a udev helper to feed to the Linux kernel a regulatory domain when needed. By using a regulatory database in userspace the Linux kernel is able to get updates for regulatory rules without requiring a rebuild. Linux distributions need the digitally signed regulatory.bin file from wireless-regdb tree and the CRDA binary from the CRDA tree. Linux distributions often combine both into one package, some distributions separate the two. The regulatory database is digitally signed by the wireless-regdb maintainer, and distributions that have have compiled in support for digital signature support on CRDA verify the integrity of the file before feeding a regulatory domain to the Linux kernel. Since the kernel module signing facility was merged upstream on Linux we could replace both CRDA and wireless-regdb distribution mechanism by adding cryptographic file signature verification support on Linux on the firmware_class module which provides the APIs to load firmware, and having the regulatory.bin file merged and updated through the linux-firmware tree.

The SMBIOS specification includes an informative annex providing conformance guidelines for DMI table implementations. I would like to write a checker tool to verify the conformance of DMI tables, based on this document. Such a tool could be useful for system firmware writers.

Fix https://gitlab.com/m2crypto/m2crypto/issues/204, see more discussion therein.

Abstract:

• Cloud hosted applications are now composed of many microservices often deployed in containers. When things go wrong, are slow, or just not understood, where can we turn?
  

The goal of this project is to create video tutorial describing configuration of SUSE Manager for Retail.

Summary

Project Description

Project Description