u/Khyta

I'm having a bit of an issue finding out how much of my paycheck I can invest (aka move to a tracking account inside YNAB) while still being a month (or more) ahead. I have budgeted pretty much everything up to January 2027 currently.

I have targets on everything and it looks like every month in the future they're higher than my salary. Am I living over my standards? I never do spend all my money that I assign to a category so there's still money being rolled over into the next month. My average spent over multiple months is also roughly 60% of my income. I semi-regularly go over my assigned money and use the "Reduce Overfunding" feature.

I'm just very much confused by the targets and how much money is being assigned to them.

Does anyone have any tips or experience on figuring out how much money can be set aside for investments or putting it towards retirement savings (3a pillar or similar)?

PS: Had to move in April + pay 40% of my Taxes as well as paying 30% of my Taxes in June.

I do need a main light, but I'm not sure what kind of shape or style to get. Some plants would probably also help maybe?

https://github.com/V4bel/dirtyfrag

Mitigations are this from the Repo: `sh -c "printf 'install esp4 /bin/false\ninstall esp6 /bin/false\ninstall rxrpc /bin/false\n' > /etc/modprobe.d/dirtyfrag.conf; rmmod esp4 esp6 rxrpc 2>/dev/null; true"`

Note that this breaks IPSec and RxRPC.

Timeline of disclosure:

2026-04-30: Submitted detailed information about the esp vulnerability and a weaponized exploit that achieves root privileges on several major distributions to security@kernel.org.

2026-04-30: Submitted the patch for the esp vulnerability to the netdev mailing list. Information about this issue was published publicly.

2026-04-30 (+9h): Kuan-Ting Chen submitted a vulnerability report for the esp vulnerability with a reproducer to security@kernel.org.

2026-05-04: Kuan-Ting Chen submitted the shared-frag approach patch to the netdev mailing list.

2026-05-07: The patch was merged into the netdev tree.

2026-05-07: Submitted detailed information about the vulnerability and the exploit to the linux-distros mailing list. The embargo was set to 5 days, with an agreement that if a third party publishes the exploit on the internet during the embargo period, the Dirty Frag exploit would be published publicly.

2026-05-07: Detailed information and the exploit for this vulnerability were published publicly by an unrelated third party, breaking the embargo.

2026-05-07: After obtaining agreement from distribution maintainers to fully disclose Dirty Frag, the entire Dirty Frag document was published.