Edit: The link.
There were lots of good titles for this submission, as in "Breaking news: Poettering clueless?" to finally disprove Betteridge's law, or "systemd surprisingly not as good as advertised" or "Breaking new: systemd broken" or "Poettering censors critics after epic fail".
Systemd implementation of "rm -rf .*" will follow ".." to upper directory and erase /
How to reproduce:
# mkdir -p /foo/dir{1,2}
# touch /foo/.bar{1,2}
# cat /etc/tmpfiles.d/test.conf
R! /foo/.* - - - - -
Reboot.
After the issue was fixed, finally Poettering added this gem of wisdom:
I am not sure I'd consider this much of a problem. Yeah, it's a UNIX pitfall, but "rm -rf /foo/.*" will work the exact same way, no?
The answer to this question, as many clarified for him, obviously is a loud "NO!". After being told a couple of times in no uncertain terms, the thread was closed for non-developers
poettering locked and limited conversation to collaborators 4 hours ago
for which I proposed the "freedom-of-speech" department (although I admit it is a weak proposal).
(Score: 3, Funny) by aristarchus on Tuesday April 18 2017, @09:23AM
"'E's not quite dead, yet!"
"I know, but he will be soon. Can you take 'im on the cart?"
"No, I cannot. It' against regulations! I could loose my license!"
"I feel happy, so happy! I think I'll take a walk!"
"Shut up! You're not fooling anyone, you know!"
"Isn't there any thing you could do?"
Thunk.
"Bring out your dead ACs! Bring out your dead ACs!"
"Who's that, then?"
"Must be Lennart Poettering."
"How can you tell?"
"'E's got shit all over him!"
[Apologies to Monty Python's Flying Circus. Or Fliegender Zirkus [youtube.com] ]