Recently, I had to connect to a hidden WiFi network with an EAP-TLS authentication. When configured via the NetworkManager UI on Ubuntu, it would work. However, on Debian Unstable running Gnome 42 and on Arch, the same process didn’t work. The problem seems to be an empty configuration line for domain-suffix-match that gets created. To solve it, you can remove the domain-suffix-match using nmcli:
When trying to mount SMB share using gio you might encounter the following error:
$ gio mount smb://ptnas1.cellebrite.local gio: smb://nas.corp.local/: Location is not mountable
This error might be due to a missing gvfs backend. The smb backend should be located in /usr/share/gvfs/mounts/smb.mount. If it is missing, you should install the gvfs-backends package and it should resolve the mounting issue.
If the mount was successful, but you can’t see it under $XDG_SESSION_DESKTOP/gvfss/, you are probably missing the FUSE server that makes the mounted filesystem available to all applications and not only to GIO aware applications. You can install the FUSE server by installing the gvfs-fuse package. The server will automatically run after reboot. If you want to start the server immediately, you can start it manually:
After the latest PipeWire upgrade on Debian, sound stopped working for. The bluetooth headset would not connect, and in the output options I had only one device labeled dummy output.
This was caused by a recent upgrade of the pipewire-media-session package to version 0.4.1-3. Debian decided that media-session is deprecated in favor of WirePlumber. As part of the package installation, the /usr/share/pipewire/media-session.d/with-pulseaudio file, signalling media-session it should handle audio, gets removed. As I didn’t have WirePlumber installed, nothing managed the audio configuration. The solution is to recreate the file and restart the relevant PipeWire servcies.
SPF allows one to specify which SMTP servers can send emails on behalf of a domain. The SPF record is defined as a DNS TXT record and specifies the list of allowed senders for the domain.
"v=spf1 a ip4:220.127.116.11 include:_spf.mx.cloudflare.net include:_spf.google.com ~all"
v=spf1 specifies that this TXT record is indeed an SPF record.
a include the IP addresses of the domain, as returned by the A or AAAA records. This is required to let your own server send emails.
ip4:18.104.22.168 allows a specific server by IP address to send emails. You can also use netmasks (ie /20) to allow ranges.
include:_spf.mx.cloudflare.net allows Cloudflare Email Routing to forward emails for your domain.
include:_spf.google.com allow sending emails via Google Workspace/Gmail.
~all This marks every other server not listed so far as insecure/spam, but the email will be accepted. This can be replaced by -all which would tell the recipient to reject emails from unauthorized servers.