


https://www.publico.pt/2025/07/11/azul/opiniao/armas-mundo-chamas-2139779
#criseclimática
https://www.publico.pt/2025/07/11/azul/opiniao/armas-mundo-chamas-2139779
#criseclimática
https://www.publico.pt/2025/07/11/azul/opiniao/armas-mundo-chamas-2139779
#criseclimática
Depending on the available Landlock ABI version your kernel supports, you might even restrict
connect(…)
calls to ports 80, 443 and maybe whatever else has been configured in the subscription list.

https://lyse.isobeef.org/waldspaziergang-2025-07-12/
I think my main takeaway is this: Knowing that technologies like Landlock/pledge/unveil exist and knowing that they are very easy to use, will probably nudge me into writing software differently in the future.
jenny was never meant to be sandboxed, so it can’t make *great* use of it. Future software might be different.
(And this is finally a strong argument for static linking.)
I think my main takeaway is this: Knowing that technologies like Landlock/pledge/unveil exist and knowing that they are very easy to use, will probably nudge me into writing software differently in the future.
jenny was never meant to be sandboxed, so it can’t make *great* use of it. Future software might be different.
(And this is finally a strong argument for static linking.)
>This extension was turned off because it is no longer supported
Thanks Google.
This browser was uninstalled because it absolutely sucks!
So only the first line should be a quote.
>This extension was turned off because it is no longer supported
Thanks Google.
This browser was uninstalled because it absolutely sucks!
So only the first line should be a quote.
$ setpriv \
--landlock-access fs \
--landlock-rule path-beneath:execute,read-file:/bin/ls-static \
--landlock-rule path-beneath:read-dir:/tmp \
/bin/ls-static /tmp/tmp/xorg.atom
The first argument
--landlock-access fs
says that nothing is allowed.--landlock-rule path-beneath:execute,read-file:/bin/ls-static
says that reading and executing that file is allowed. It’s a statically linked ls
program (not GNU ls).--landlock-rule path-beneath:read-dir:/tmp
says that reading the /tmp
directory and everything below it is allowed.The output of the
ls-static
program is this line:─rw─r──r────x 3000 200 07-12 09:19 22'491 │ /tmp/tmp/xorg.atom
It was able to read the directory, see the file, do
stat()
on it and everything, the little x
indicates that getting xattrs also worked.3000
and 200
are user name and group name – they are shown as numeric, because the program does not have access to /etc/passwd
and /etc/group
.Adding
--landlock-rule path-beneath:read-file:/etc/passwd
, for example, allows resolving users and yields this:─rw─r──r────x cathy 200 07-12 09:19 22'491 │ /tmp/tmp/xorg.atom
$ setpriv \
--landlock-access fs \
--landlock-rule path-beneath:execute,read-file:/bin/ls-static \
--landlock-rule path-beneath:read-dir:/tmp \
/bin/ls-static /tmp/tmp/xorg.atom
The first argument
--landlock-access fs
says that nothing is allowed.--landlock-rule path-beneath:execute,read-file:/bin/ls-static
says that reading and executing that file is allowed. It’s a statically linked ls
program (not GNU ls).--landlock-rule path-beneath:read-dir:/tmp
says that reading the /tmp
directory and everything below it is allowed.The output of the
ls-static
program is this line:─rw─r──r────x 3000 200 07-12 09:19 22'491 │ /tmp/tmp/xorg.atom
It was able to read the directory, see the file, do
stat()
on it and everything, the little x
indicates that getting xattrs also worked.3000
and 200
are user name and group name – they are shown as numeric, because the program does not have access to /etc/passwd
and /etc/group
.Adding
--landlock-rule path-beneath:read-file:/etc/passwd
, for example, allows resolving users and yields this:─rw─r──r────x cathy 200 07-12 09:19 22'491 │ /tmp/tmp/xorg.atom
setpriv
on Linux supports Landlock.If this twt goes through, then restricting the filesystem so that jenny can only write to
~/Mail/twt
, ~/www/twtxt.txt
, ~/.jenny-cache
, and /tmp
works.
setpriv
on Linux supports Landlock.If this twt goes through, then restricting the filesystem so that jenny can only write to
~/Mail/twt
, ~/www/twtxt.txt
, ~/.jenny-cache
, and /tmp
works.
https://gist.github.com/villares/560e231da78cd1b8f5701c5a6897348f




https://gist.github.com/villares/177c2323d424d5b2b0de49570fb4e2fd?permalink_comment_id=5673097#gistcomment-5673097
#ptpol 
#ptpol 
#ptpol 
#fridayreads #bookstodon 
#fridayreads #bookstodon 
#fridayreads #bookstodon 
https://git.suckless.org/st/file/x.c.html#l1984
The exact timings are configurable.
This is the PR that changed the timing in VTE recently (2023):
https://gitlab.gnome.org/GNOME/vte/-/issues/2678
There is a long discussion. It’s not a trivial problem, especially not in the context of GTK and multiple competing terminal widgets. st dodges all these issues (for various reasons).
https://git.suckless.org/st/file/x.c.html#l1984
The exact timings are configurable.
This is the PR that changed the timing in VTE recently (2023):
https://gitlab.gnome.org/GNOME/vte/-/issues/2678
There is a long discussion. It’s not a trivial problem, especially not in the context of GTK and multiple competing terminal widgets. st dodges all these issues (for various reasons).
My shell prompt and cursor look like this:
$ █
When I keep Enter pressed, I expect to see several lines like so:
$
$
$
$
$
$
$ █
With the affected terminal emulators, the lines actually show up in the following sequence. First, we have the original line:
$ █
Pressing Enter yields this as the next frame:
$
█
And then eventually this:
$
$ █
In other words, you can see the cursor jumping around very quickly, all the time.
Another example: Vim actually shows which key you just pressed in the bottom right corner. Keeping
j
pressed to scroll through a file means I get to see a j
flashing rapidly now.(I have no idea yet, why *exactly* XTerm in X11 is fine but flickering in Wayland.)
My shell prompt and cursor look like this:
$ █
When I keep Enter pressed, I expect to see several lines like so:
$
$
$
$
$
$
$ █
With the affected terminal emulators, the lines actually show up in the following sequence. First, we have the original line:
$ █
Pressing Enter yields this as the next frame:
$
█
And then eventually this:
$
$ █
In other words, you can see the cursor jumping around very quickly, all the time.
Another example: Vim actually shows which key you just pressed in the bottom right corner. Keeping
j
pressed to scroll through a file means I get to see a j
flashing rapidly now.(I have no idea yet, why *exactly* XTerm in X11 is fine but flickering in Wayland.)
name
and class
.Wayland (or rather, the XDG shell protocol – core Wayland knows nothing about this) only has a single field called
app_id
.When you run X11 programs under Wayland, you use XWayland, which is baked into most compositors. Then you have to deal with all three fields.
Some compositors map
name
to app_id
, others map class
to app_id
, and even others directly expose the original name
and class
.Apparently, there is no consensus.
name
and class
.Wayland (or rather, the XDG shell protocol – core Wayland knows nothing about this) only has a single field called
app_id
.When you run X11 programs under Wayland, you use XWayland, which is baked into most compositors. Then you have to deal with all three fields.
Some compositors map
name
to app_id
, others map class
to app_id
, and even others directly expose the original name
and class
.Apparently, there is no consensus.
Europa: só estamos disponíveis a propor fazer uma redução de 90% nas emissões e lá para 2040
Direita: vamos deixar a extrema-direita controlar esta agenda
Extrema-direita: hahaha, no way.
Obrigado a todos os envolvidos, this is fine.
https://www.publico.pt/2025/07/09/azul/noticia/extremadireita-vai-controlar-aprovacao-nova-meta-climatica-ue-2040-2139651
#criseclimática #EU
Europa: só estamos disponíveis a propor fazer uma redução de 90% nas emissões e lá para 2040
Direita: vamos deixar a extrema-direita controlar esta agenda
Extrema-direita: hahaha, no way.
Obrigado a todos os envolvidos, this is fine.
https://www.publico.pt/2025/07/09/azul/noticia/extremadireita-vai-controlar-aprovacao-nova-meta-climatica-ue-2040-2139651
#criseclimática #EU
Europa: só estamos disponíveis a propor fazer uma redução de 90% nas emissões e lá para 2040
Direita: vamos deixar a extrema-direita controlar esta agenda
Extrema-direita: hahaha, no way.
Obrigado a todos os envolvidos, this is fine.
https://www.publico.pt/2025/07/09/azul/noticia/extremadireita-vai-controlar-aprovacao-nova-meta-climatica-ue-2040-2139651
#criseclimática #EU
Fico a aguardar o estudo do #Governo sobre o impacto destes aumentos nos níveis de emissão de CO2, e o plano de mitigação desses aumentos para garantia de cumprimento do Orçamento de Carbono 2026-2030, da Lei de Bases do Clima, e dos compromissos assumidos no Acordo de Paris.
#ptpol #TAP #CriseClimática
Fico a aguardar o estudo do #Governo sobre o impacto destes aumentos nos níveis de emissão de CO2, e o plano de mitigação desses aumentos para garantia de cumprimento do Orçamento de Carbono 2026-2030, da Lei de Bases do Clima, e dos compromissos assumidos no Acordo de Paris.
#ptpol #TAP #CriseClimática
Fico a aguardar o estudo do #Governo sobre o impacto destes aumentos nos níveis de emissão de CO2, e o plano de mitigação desses aumentos para garantia de cumprimento do Orçamento de Carbono 2026-2030, da Lei de Bases do Clima, e dos compromissos assumidos no Acordo de Paris.
#ptpol #TAP #CriseClimática
"Chega, IL e CDS abstêm-se no voto pelo ataque à companhia A Barraca"
https://www.noticiasaominuto.com/politica/2819198/chega-il-e-cds-abstem-se-no-voto-pelo-ataque-a-companhia-a-barraca
#ptpol
"Chega, IL e CDS abstêm-se no voto pelo ataque à companhia A Barraca"
https://www.noticiasaominuto.com/politica/2819198/chega-il-e-cds-abstem-se-no-voto-pelo-ataque-a-companhia-a-barraca
#ptpol
"Chega, IL e CDS abstêm-se no voto pelo ataque à companhia A Barraca"
https://www.noticiasaominuto.com/politica/2819198/chega-il-e-cds-abstem-se-no-voto-pelo-ataque-a-companhia-a-barraca
#ptpol
When the sun came out, colors were just beautiful:

But yeah, each to their own (expensive) hobbies. :-) I, for example, burn my money on tools that I don't really™ need. :-P