Dear Tumbleweed users and hackers,

This week, we were finally getting some fixes together for the glibc/i586 issues that plagued us for a while. Unfortunately, also for the x86_64 users, this meant once again a full rebuild of the distribution (which was published just recently with snapshot 0311). But the 4 snapshots published during this week (0305, 0306, 0307, and 0311) also had something for everybody anyway.

The main changes in those 4 snapshots include:

• glibc: Disable x86 ISA level for now
• Linux kernel 5.11.2 & 5.11.4
• gnutls 3.7.0
• openssl 1.1.1j, based on a centralized crypto-policy package
• Libvirt 7.1.0
• KDE Applications 20.12.3
• KDE Plasma 5.21.2
• LibreOffice 7.1.1.2

That actually almost is everything I had listed last week as coming soon. Only GCC 11 as the default compiler remained, and that one is still going to be with us for a few weeks. But things did not stop there, and the stagings are already filled with other things again:

• Linux kernel 5.11.6
• Python 3.9 modules: besides python36-FOO and python38-FOO, we are testing to also shop python39-FOO modules; we already have the interpreter after all. Python 3.8 will remain the default for now.
• UsrMerge is gaining some traction again, thanks to Ludwig for pushing for it
• GCC 11 as default compiler

Esta semana se va a celebrar la 1ª Cumbre Software Libre y Educación y este blog está promocionándolo al máximo (supongo que tanto que los lectores estarán desertando). Hoy toca comentar que Richard M. Stallman presentará la reedición en español del libro «Software Libre para una Sociedad Libre» en la 1ª Edición de la Cumbre Software Libre y Educación. Una oportunidad única para conocer a fondo esta obra fundamental del conocimiento libre.

Richard M. Stallman presentará la reedición en español del libro «Software Libre para una Sociedad Libre» en la 1ª Edición de la Cumbre Software Libre y Educación

Ya he hablado de la Conferencia «La era de la digitalización en las aulas» de Javier Sepúlveda, de la mesa redonda «Software Libre y Educación en la Comunitat Valenciana» con Richard M. Stallman y la Conferencia «El Software Libre, la Libertad y la Educación» que realizará Richard M. Stallman el próximo domingo a las 17.00 horas.

Solo me queda comentar que con motivo de la presencia de Richard M. Stallman en los actos de la 1ª Cumbre Software Libre y Educación, por fin se puede hacer la presentación del libro, que fue aplazada en marzo de 2020 debido a la pandemia el próximo domingo a las 18:45 horas CET.

Según podemos leer en el anuncio de la asociación el año pasado se solicitó en una nueva reimpresión del libro de Richard Stallman «SOFTWARE LIBRE PARA UNA SOCIEDAD LIBRE». Esta fue la primera reimpresión desde el año 2004, de esta traducción al castellano del libro original «Free software Free Society«. La editorial Traficantes de Sueños  tuvo la cortesía de realizarnos una impresión especial de tirada aquella para la serie de conferencias de Richard Stallman que programaron y tuvieron que suspender por la pandemia del Covid-19.

Los precios del libro son:

Precio en mano (cuando sea posible) 10€

Con envío por correo ordinario 14€

Con envío por correo certificado 17€

¡¡¡Solo se cuenta con 150 ejemplares!!! ¡¡Daos prisa!!

Y para finalizar, os pongo el vídeo del presidente de GNU/Linux València promocionando el evento.

1ª Edición de la Cumbre Software Libre y Educación

Este viernes empieza la 1ª Edición de la Cumbre Software Libre y Educación organizando la Asociación de Software Libre GNU/Linux València y Las Naves es altamente recomendable para todos y todas ya que contará con

Además, cuenta con un invitado de máximo nivel: Richard M. Stallman, fundador del movimiento del software libre, del sistema operativo GNU, de la Free Software Foundation (Fundación para el Software Libre) y defensor acérrimo de la Cultura Libre.

Más información: GNU/Linux València

By default, openSUSE Leap 15.x is using the firewalld firewall implementation (and the firewalld backend is using iptables under the hood).

But since a while, openSUSE also has nftables support available - but neither YaST nor other special tooling is currently configured to directly support it. But we have some machines in our infrastructure, that are neither straight forward desktop machines nor do they idle most of the time. So let's try out how good we are at trying out and testing new things and use one of our central administrative machines: the VPN gateway, which gives all openSUSE heroes access to the internal world of the openSUSE infrastructure.

This machine is already a bit special:

• The "external" interface holds the connection to the internet
• The "private" interface is inside the openSUSE heroes private network
• We run openVPN with tun devices (one for udp and one for tcp) to allow the openSUSE heroes to connect via a personal certificate + their user credentials
• In addition, we run wireguard to connect the private networks in Provo and Nuremberg (at our Sponsors) together
• And before we forget: our VPN gateway is not only a VPN gateway: it is also used as gateway to the internet for all internal machines, allowing only 'pre-known traffic' destinations

All this makes the firewall setup a little bit more complicated.

BTW: naming your interfaces by giving them explicit names like "external" or "private", like in our example, has a huge benefit, if you play along with services or firewalls. Just have a look in /etc/udev/rules.d/70-persistent-net.rules once your devices are up and rename them according to your needs (you can also use YaST for this). But remember to also check/rename the interfaces in /etc/sysconfig/network/ifcfg-* to use the same name before rebooting your machine. Otherwise your end up in a non-working network setup.

Let's have a short look at the area we are talking about:

As you hopefully notice, none of the services on the community side is affected. There we have standard (iptables) based firewalls and use proxies to forward user requests to the right server.

On the openSUSE hero side, we exchanged the old SuSEfirewall2 based setup with a new one based on nftables.

There are a couple of reasons that influenced us in switching over to nftables:

• the old SuSEfirewall2 worked, but generated a huge iptables list on our machine in question
• using ipsets or variables with SuSEfirewall2 was doable, but not an easy task
• we ran into some problems with NAT and Masquerading using firewalld as frontend
• Salt is another interesting field:
  • Salt'ing SuSEfirewall2 by deploying some files on a machine is always possible, but not really straight forward
  • there is no Salt module for SuSEfirewall2 (and there will probably never be one)
  • there are Salt modules for firewalld and nftables, both on nearly the same level
• nftables is integrated since a while in the kernel and should replace all the *tables modules long term. So why not jumping directly to it, as we (as admins) do not use GUI tools like YaST or firewalld-gui anyway?

So what are the major advantages?¶

1. Sets are part of the core functionality. You can have sets of ports, interface names, and address ranges. No more ipset. No more multiport. ip daddr { 1.1.1.1, 1.0.0.1 } tcp dport { dns, https } oifname { "external", "wg_vpn1" } accept; This means you can have very compact firewall sets to cover a lot of cases with a few rules.
2. No more extra rules for logging. Only turn on counter where you need it. counter log prefix "[nftables] forward reject " reject
3. You can cover IPv4 and IPv6 with a single ruleset when using table inet, but you can have per IP protocol tables as well. And sometimes even need them e.g. for postrouting.

Starting from scratch¶

A very basic /etc/nftables.conf would look something like this

#!/usr/sbin/nft -f

flush ruleset

# This matches IPv4 and IPv6
table inet filter {
    # chain names are up to you.
    # what part of the traffic they cover, 
    # depends on the type line.
	chain input {
		type filter hook input priority 0; policy accept;
	}
	chain forward {
		type filter hook forward priority 0; policy accept;
	}
	chain output {
		type filter hook output priority 0; policy accept;
	}
}

But so far we did not stop or allow any traffic. Well actually we let everything in and out now because all chains have the policy accept.

#!/usr/sbin/nft -f

flush ruleset

table inet filter {
    chain base_checks {
        ## another set, this time for connection tracking states.
        # allow established/related connections
        ct state {established, related} accept;

        # early drop of invalid connections
        ct state invalid drop;
    }

   	chain input {
		type filter hook input priority 0; policy drop;
        
        # allow from loopback
        iif "lo" accept;

        jump base_checks;

        # allow icmp and igmp
        ip6 nexthdr icmpv6 icmpv6 type { echo-request, echo-reply, packet-too-big, time-exceeded, parameter-problem, destination-unreachable, packet-too-big, mld-listener-query, mld-listener-report, mld-listener-reduction, nd-router-solicit, nd-router-advert, nd-neighbor-solicit, nd-neighbor-advert, ind-neighbor-solicit, ind-neighbor-advert, mld2-listener-report } accept;
        ip protocol icmp icmp type { echo-request, echo-reply, destination-unreachable, router-solicitation, router-advertisement, time-exceeded, parameter-problem } accept;
        ip protocol igmp accept;
        
        # for testing reject with logging
        counter log prefix "[nftables] input reject " reject;
	}
    chain forward {
		type filter hook forward priority 0; policy accept;
	}
	chain output {
		type filter hook output priority 0; policy accept;
	}
}

You can activate the configuration with nft --file nftables.conf, but do NOT do this on a remote machine. It is also a good habit to run nft --check --file nftables.conf before actually loading the file to catch syntax errors.

So what did we change?

1. most importantly we changed the policy of the chain to drop and added a reject rule at the end. So nothing gets in right now.
2. We allow all traffic on the localhost interface.
3. The base_checks chain handles all packets related to established connections. This makes sure that incoming packets for outgoing connections get through.
4. We allowed important ICMP/IGMP packets. Again this is using a set and the type names and not some crtyptic numbers. YAY for readability.

Now if someome tries to do a ssh connect to our machine, we will see:

[nftables] input reject IN=enp1s0 OUT= MAC=52:54:00:4c:51:6c:52:54:00:73:a1:57:08:00 SRC=172.16.16.2 DST=172.16.16.30 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=22652 DF PROTO=TCP SPT=55574 DPT=22 WINDOW=64240 RES=0x00 SYN URGP=0 

and nft list ruleset will show us

counter packets 1 bytes 60 log prefix "[nftables] input reject " reject

So we are secure now. Though maybe allowing SSH back in would be nice. You know just in case.
We have 2 options now. Option 1 would be to insert the following line before our reject line.

tcp dport 22 accept;

But did we mention already that we have sets and that they are great? Especially great if we need the same list of ports/ip ranges/interface names in multiple places?

We have 2 ways to define sets:

define wanted_tcp_ports {
  22,
}

Yes the trailing comma is ok. And it makes adding elements to the list easier. So we do them all the time.
This will change our rule above to

tcp dport $wanted_tcp_ports accept;

If we load the config file and run nft list ruleset, we will see:

tcp dport { 22 } accept

But there is actually a slightly better way to do this:

    set wanted_tcp_ports {
        type inet_service; flags interval;
        elements = {
           ssh
        }
    }

That way our firewall rule becomes:

tcp dport @wanted_tcp_ports accept;

And if we dump our firewall with nft list ruleset afterwards it will still be shown as @wanted_tcp_ports and not have variable replaced with the value.
While this is great already, the 2nd syntax actually has one more advantage.

$ nft add element inet filter wanted_tcp_ports \{ 443 \}

Now our wanted_tcp_ports list will allow port 22 and 443.
This is of course often more useful if we use it with IP addresses.

    set fail2ban_hosts {
        type ipv4_addr; flags interval;
        elements = {
           192.168.0.0/24
        }       
    }

Let us append some elements to that set too.

$ nft add element inet filter fail2ban_hosts \{ 192.168.254.255, 192.168.253.0/24 \}
$ nft list ruleset

... and we get ...

        set fail2ban_hosts {
                type ipv4_addr
                flags interval
                elements = { 192.168.0.0/24, 192.168.253.0/24,
                             192.168.254.255 }
        }

Now we could change fail2ban to append elements to the set instead of creating a new rule for each new machine it wants to block. Fewer rules. Faster processing.

But with reloading the firewall we dropped port 443 from the port list again. Oops.
Though ... if you are happy with the rules. You can just run

$ nft list ruleset > nftables.conf

When you are using all the sets instead of the variables, all your firewall rules will still look nice.

Our complete firewall looks like

table inet filter {
        set wanted_tcp_ports {
                type inet_service
                flags interval
                elements = { 22, 443 }
        }

        set fail2ban_hosts {
                type ipv4_addr
                flags interval
                elements = { 192.168.0.0/24, 192.168.253.0/24,
                             192.168.254.255 }
        }

        chain base_checks {
                ct state { established, related } accept
                ct state invalid drop
        }

        chain input {
                type filter hook input priority filter; policy drop;
                iif "lo" accept
                jump base_checks
                ip6 nexthdr ipv6-icmp icmpv6 type { destination-unreachable, packet-too-big, time-exceeded, parameter-problem, echo-request, echo-reply, mld-listener-query, mld-listener-report, mld-listener-done, nd-router-solicit, nd-router-advert, nd-neighbor-solicit, nd-neighbor-advert, ind-neighbor-solicit, ind-neighbor-advert, mld2-listener-report } accept
                ip protocol icmp icmp type { echo-reply, destination-unreachable, echo-request, router-advertisement, router-solicitation, time-exceeded, parameter-problem } accept
                ip protocol igmp accept
                tcp dport @wanted_tcp_ports accept
                counter packets 12 bytes 828 log prefix "[nftables] input reject " reject
        }

        chain forward {
                type filter hook forward priority filter; policy accept;
        }

        chain output {
                type filter hook output priority filter; policy accept;
        }
}

For more see the nftables wiki

Desde hace unos días el foro oficial en español de openSUSE está inaccesible

Sois varias personas las que me habéis preguntando por la caída del servicio de forosuse.org

Desde hace unos días el sitio está inaccesible, primero por problemas con el certificado y ahora porque está inutilizable.

Contacté hace unos días con el supermoderador, Diablo Rojo que se puso en contacto con Riven,el administrador del foro.

El problema es que la empresa de hosting donde está alojado el foro está migrando a un nuevo servidor.

Por lo que de momento no se puede hacer otra cosa que esperar a que termine la migración.

Esperemos que la espera sea corta y pronto se restablezca el servicio de nuestro foro. El foro oficial en español de la comunidad de openSUSE.

Nos leemos pronto por forosuse.org

Voy a cambiar el nombre del blog de KDE Blog a Event Blog… y es que esta semana la estoy dedicando integramente a promocionar el evento de este fin de semana la 1ª Cumbre Software Libre y Educación… y no el el primer evento que estoy promocionando. He hablado de la Conferencia «La era de la digitalización en las aulas» de Javier Sepúlveda, de la mesa redonda «Software Libre y Educación en la Comunitat Valenciana» con Richard M. Stallman y hoy toca hablar del plato fuerte, la Conferencia «El Software Libre, la Libertad y la Educación» que realizará Richard M. Stallman el próximo domingo a las 17.00 horas.

Conferencia «El Software Libre, la Libertad y la Educación» por Richard M. Stallman

De nuevo hago un pequeño copia y pega de la información que nos ofrece la página oficial de GNU/Linux València y que explica qué nos vamos a encontrar el domingo 14 a las 17:00 horas CET (hora penínsular de España).

Tras los actos celebrados el viernes y el sábado, hoy domingo contaremos con la presencia de Richard M. Stallman, Fundador del Movimiento del Software Libre, del sistema operativo GNU y de la Free Software Foundation.

Una vez más, retransmitiremos desde https://streaming.gnulinuxvalencia.org/fsed-summit.webm utilizando Software Libre BigBlueButton, emitido a través de un servidor de difusión gracias al software libre IceCast.

1ª Edición de la Cumbre Software Libre y Educación

Este viernes empieza la 1ª Edición de la Cumbre Software Libre y Educación organizando la Asociación de Software Libre GNU/Linux València y Las Naves es altamente recomendable para todos y todas ya que contará con

Además, cuenta con un invitado de máximo nivel: Richard M. Stallman, fundador del movimiento del software libre, del sistema operativo GNU, de la Free Software Foundation (Fundación para el Software Libre) y defensor acérrimo de la Cultura Libre.

Más información: GNU/Linux València

Let’s gehts los! The openSUSE Project is one of about 200 mentoring organizations selected for this year’s Google Summer of Code.

The openSUSE Project has participated in several GSoC events since 2006 and the project’s mentors have helped more than 60 students become familiar with open-source software development.

openSUSE website dedicated to GSoC offers several projects for GSoC students. Projects are available for software testing with openQA, Artificial Intelligence development with Phoeβe and configuration and infrastructure management through the Uyuni Project. Some of the projects listed with the openSUSE organization within the GSoC program work with Kubernetes like the carrier project and Rancher.

Projects listed on the mentoring website 101.opensuse.org include projects also related to Debian, Ubuntu, KDE, AWS and Windows.

Programming languages in the listed projects include Go, Ruby, Perl, Python, Rust and c/c++.

The list of 101.opensuse.org projects are:

• Dynamic detection of error conditions from openQA test results
• Container-based backend for openQA
• Logging Pipeline Plumber
• ibus customized pre-edit themes
• Refactor client OS support in kits
• Add new client OS
• Translate Uyuni to language X
• Package Uyuni for Debian
• Windows client support
• Amazon Linux 2 support
• Add KDE support
• Enhance Debian and Ubuntu support
• Breakdown Uyuni into plugins architecture
• Convert Virtual Systems page to ReactJS
• PaaS on Kubernetes
• Update Kanidm project
• Enhancements to the ML models
• Implementing libseccomp in PRoot
• Porting PRoot to Rust
• Root / CARE and Intel SGX
• Unprivileged containers with PRoot
• Improve adding options in Yast security modul

As a mentoring organization, eligible students will have an opportunity between March 29 and April 13 to submit an application proposal to the GSoC program site. The program is open to university students aged 18 or over.

The annual international program focuses on bringing student developers into open source software development. Students work with open-source organizations on a 10-week programming project during the school break.

After the students submit their applications, there will be a review period from April 13 and May 17. Accepted projects will be announced on May 17 and the coding will begin on June 7 and continue throughout the summer.

If you are interested in participating in GSoC, please visit the 101.opensuse.org mentoring website and Google Summer of Code website for more information about the projects and the application process.

Accepted students with openSUSE are encouraged to blog about their experience during GSoC on news.opensuse.org through submitting a pull request here.

1. news-o-o: Kami ingin semua “berita komunitas” diterjemahkan ke dalam empat bahasa yang paling banyak digunakan dalam komunitas (Indonesia, Spanyol, Portugis, Rusia – ini hanya permulaan, hubungi kami jika Anda ingin mengusulkan diri Anda sebagai penerjemah untuk bahasa lainnya)
2. Sebuah nawala (newsletter) komunitas baru: Terinspirasi dari para pendahulu, kami ingin membuat buletin komunitas yang isinya:
   1.  Menampilkan individu-individu luar biasa dari seluruh komunitas, menyoroti apa yang mereka lakukan dan bagaimana mereka melakukannya, melalui wawancara atau liputan
   2.  Membagikan tutorial dan panduan yang berguna tentang cara menggunakan sistem openSUSE Anda dan bagaimana Anda dapat segera mulai berkontribusi
   3.  Menampilkan fitur dari paket menarik yang mungkin membutuhkan perhatian
   4.  Menunjukkan tempat-tempat dalam komunitas di mana minat dan keterampilan Anda paling baik digunakan
   5.  Mengumumkan acara & aktivitas komunitas, sehingga Anda memiliki kesempatan untuk bertemu geeko lainnya
   6.  …secara keseluruhan, kumpulan postingan blog, artikel, dan ulasan yang muncul dalam beberapa minggu terakhir atau lebih, untuk memastikan hal-hal tertentu menonjol dari aliran waktu yang tak terhindarkan.

• https://t.me/openSUSE_newscom
• https://matrix.to/#/#newscom:opensuse.org
• https://discord.gg/opensuse#newscom