InnerScientist

I have linkwarden set up for this.

On Android I share to the linkwarden app to save, on pc i use the Firefox addon.

Sure it's fragmented but I'm already used to doing things different between mobile and pc anyways.

1024 Gibibytes

doesn't cover ISP or commercial equipment

The foreign backdoors will stay for critical infrastructure

Status: Closed

That means it wasn't accepted, see also the last comment before closing:

It's an optional field in the userdb JSON object. It's not a policy engine, not an API for apps. We just define the field, so that it's standardized iff people want to store the date there, but it's entirely optional.

Hence, please move your discussion elsewhere, you are misunderstanding what systemd does here. It enforces zero policy, it leaves that up for other parts of the system.

And sorry, I am really not interested in these discussions here. it's not the right place for this, and please don't bring it here. Thank you.

Not true, looking at systemd main branch shows the field still exists. Here's the state as of posting this comment:

https://github.com/systemd/systemd/blob/494c65236b19e160ade48315edfa0f089f3d4154/man/homectl.xml#L370

Also ping @Gonzako@lemmy.world fyi

Weren't they though? Like they were absolutely horrible but last I remember most everything else in WH was also somehow worse than them so they are the "good"-er guys.

because all the other programs, protocol are working fine.

With the shown firewall configuration nothing but NTP should work? You're dropping outgoing packets by default.

Update your nftables rulefile or use nft commands to update your firewall to the following:

# extract
chain OUT {
    type filter hook output priority 0; policy drop;
    udp dport 123 accept

    limit rate 3/second log prefix "Nftables Blocked: OUT: "
}

chain IN {
    type filter hook input priority 0; policy drop;
    ct state established, related accept

    limit rate 3/second log prefix "Nftables Blocked: IN: "
}

Blocked pakets will show up in the kernel log (dmesg/journalcl)

If you want more information on why it is blocked then enable nftrace for those packets

nft add rule inet/ip/ip6 tablename OUT udp dport 123 meta nftrace set 1
nft add rule inet/ip/ip6 tablename IN udp dport 123 meta nftrace set 1
nft monitor trace

Or

nft add rule inet/ip/ip6 tablename OUT meta nftrace set 1

Or maybe even

nft add rule inet/ip/ip6 tablename PREROUTING udp dport 123 meta nftrace set 1

Additionally you can use tcpdump -i to show network packets before they enter the firewall, there you should be able to tell what it's a trying to do.

Successfully merging this pull request may close these issues.

None yet

Pretty sure they renamed it to Copilot

Pro tip: If you're using openwrt or other managed network components don't forget to automatically back those up too. I almost had to reset my openwrt router and having to reconfigure that from scratch sucks.