K. Ryabitsev 🍁
@monsieuricon
Moderator
Posts
2041Following
230Followers
2517This account is for Linux/Kernel/FOSS topics in general: #linux, #kernel, #foss, #git, #sysadmin, #infrastructure.
For my personal account, please follow @monsieuricon@castoranxieux.ca.
Montréal, Québec, Canada 🇨🇦🇺🇦
K. Ryabitsev 🍁
monsieuricon
Santa: So, have you been naughty or nice?
Me: Oh, I've been naughty, Santa.
Santa: Oh, really? And how so?
Me: When replying to emails, I've been writing below the "Please do not write below this line".
Santa: What kind of monster are you?
Me: Oh, I've been naughty, Santa.
Santa: Oh, really? And how so?
Me: When replying to emails, I've been writing below the "Please do not write below this line".
Santa: What kind of monster are you?
0
3
5
K. Ryabitsev 🍁
monsieuricon
b4 0.11.0 is available
Many improvements to the contributor-oriented features (b4 prep, b4 trailers, b4 send). If you haven't tried those out yet, please check them out, they are documented here:
https://b4.docs.kernel.org/en/stable-0.11.y/contributor/overview.html
Release announcement:
https://lore.kernel.org/tools/20221219213715.2qozw5emt5j7t3xr@nitro.local/
#b4
Many improvements to the contributor-oriented features (b4 prep, b4 trailers, b4 send). If you haven't tried those out yet, please check them out, they are documented here:
https://b4.docs.kernel.org/en/stable-0.11.y/contributor/overview.html
Release announcement:
https://lore.kernel.org/tools/20221219213715.2qozw5emt5j7t3xr@nitro.local/
#b4
0
3
8
K. Ryabitsev 🍁
monsieuricon
@jonmasters as usual, we get into the morass of key distribution, revocation, and trusting the infra. If you add a signed document like "I am userfoo@social.kernel.org" and add it to your profile, that doesn't actually certify every post you make. I can post things as any user on social.kernel.org, so I (or someone who hacks me) can impersonate anyone there.
I am currently leaning towards webfinger-level certification -- you can easily verify that mricon@kernel.org is actually monsieuricon@social.kernel.org, and I think this is good enough for most purposes.
I am currently leaning towards webfinger-level certification -- you can easily verify that mricon@kernel.org is actually monsieuricon@social.kernel.org, and I think this is good enough for most purposes.
0
0
2
K. Ryabitsev 🍁
monsieuricon
@dirkhh let's hope so! I'm guessing this is highly dependent on your immediate local reality. Where I am, using CCS chargers still requires fumbling with several cards and hoping for the best. :/
0
0
0
K. Ryabitsev 🍁
monsieuricon
@dirkhh Sadly, a widespread and *reliable* fast-charge network is still the core consideration for many, and until Chademo/CCS wars are over, Tesla's fast-chargers will remain a much better option hands-down.
0
0
0
K. Ryabitsev 🍁
monsieuricon
PSA: just having a DKIM-Signature: header in your email isn't really enough, unless it has a d= part matching your From: address.
E.g., this is good:
From: foo@example.com
DKIM-Signature: v=1; d=example.com; [...]
This, on the other hand, serves no real purpose outside of Google:
From: foo@example.com
DKIM-Signature: v=1; d=example-com.20210112.gappssmtp.com; [...]
When there is no DKIM alignment, DMARC-enforcing servers will fall back to only using the SPF record, which doesn't work at all with mailing lists unless they rewrite the From: header.
So, please-please properly set up your DKIM infrastructure if you send messages to mailing lists. Or at the very least don't put p=reject into your DMARC policy.
E.g., this is good:
From: foo@example.com
DKIM-Signature: v=1; d=example.com; [...]
This, on the other hand, serves no real purpose outside of Google:
From: foo@example.com
DKIM-Signature: v=1; d=example-com.20210112.gappssmtp.com; [...]
When there is no DKIM alignment, DMARC-enforcing servers will fall back to only using the SPF record, which doesn't work at all with mailing lists unless they rewrite the From: header.
So, please-please properly set up your DKIM infrastructure if you send messages to mailing lists. Or at the very least don't put p=reject into your DMARC policy.
0
0
5
K. Ryabitsev 🍁
monsieuricon
Does the Tesla executive board loudly beep at you when everyone's asleep at the wheel? I think we're at the point where they have to consider cordoning off the Twitter dumpster fire.
0
0
2
K. Ryabitsev 🍁
monsieuricon
@cafkafk I intend to — unless, of course, Tesla goes bust and one of the botched updates bricks the car or something. :)
0
0
0
K. Ryabitsev 🍁
monsieuricon
I need a "don't blame me, I bought this car before Elon went gaga" sticker.
0
0
5
K. Ryabitsev 🍁
repeated
repeated
Linux Security Summit 🐧
LinuxSecSummit
📢
The #LinuxSecuritySummit announcement channel has moved here, to social.kernel.org, from Twitter (previously: https://twitter.com/LinuxSecSummit).
#kernel #linux #security #infosec #selinux #apparmor #smack #landlock #lsm #linuxfoundation #lf #conference
The #LinuxSecuritySummit announcement channel has moved here, to social.kernel.org, from Twitter (previously: https://twitter.com/LinuxSecSummit).
#kernel #linux #security #infosec #selinux #apparmor #smack #landlock #lsm #linuxfoundation #lf #conference
0
10
8
K. Ryabitsev 🍁
monsieuricon
@dirkhh since there is no set meaning of "several," technically it hasn't lied to you since 08:05.
0
0
1