https://www.dn.pt/sociedade/viticultores-manifestam-se-na-r%C3%A9gua-deixam-carrinhas-e-tratores-e-a-p%C3%A9-bloqueiam-ponte-da-r%C3%A9gua
#douro
https://www.dn.pt/sociedade/viticultores-manifestam-se-na-r%C3%A9gua-deixam-carrinhas-e-tratores-e-a-p%C3%A9-bloqueiam-ponte-da-r%C3%A9gua
#douro
https://www.dn.pt/sociedade/viticultores-manifestam-se-na-r%C3%A9gua-deixam-carrinhas-e-tratores-e-a-p%C3%A9-bloqueiam-ponte-da-r%C3%A9gua
#douro






O Gandi subiu imenso os preços, e estou a olhar para o OVH, mas antes de mergulhar queria saber o que se usa por aí
O Gandi subiu imenso os preços, e estou a olhar para o OVH, mas antes de mergulhar queria saber o que se usa por aí
> Bluesky: Users verify their age by adding a payment method or uploading a photo ID.
>
> Mastodon: Users verify their age by posting pictures of the vintage computer equipment in their homes.
https://beige.party/@maxleibman/114848276288629121
😏
> Bluesky: Users verify their age by adding a payment method or uploading a photo ID.
>
> Mastodon: Users verify their age by posting pictures of the vintage computer equipment in their homes.
https://beige.party/@maxleibman/114848276288629121
😏
Tech is no longer interesting. I need to find a new field.
Tech is no longer interesting. I need to find a new field.



https://www.bitecode.dev/p/brett-cannon-on-python-humans-and



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.