notepad is blue
filmed with unregistered hypercam 2
Website | https://refi64.com/ |
Vaccinated? | x5 |
Pronouns | he/they |
New post: Placing Functions
https://blog.yoshuawuyts.com/placing-functions
I wrote a blog post about placing functions: functions which can return without moving. This is useful for referentially stable constructors, including immovable types, C++ interop, and dyn async traits.
A lot of useful stuff, packaged up in a declarative interface. Oh and: I have a prototype of this working already (albeit entirely using proc macros).
This is all very efficient to secure services, but it's also a bit opaque: since it's the daemon you sandbox, and your admin tools are outside of that sandbox it's sometimes hard to analyze how the daemon sees things.
No more. With v258 there's a new verb "unit-shell" in systemd-analyze. You specify a service name, and it opens you a shell inside that specified services' sandbox (which must be running for this). You can look around and check if everything is like you expected it to be.
"Arbitrary File Read via file:// Protocol in cURL"
Well, you see... 🤦♂️
I am now hearing that using three of something in writing is a sign of AI now.
And not literally a long standard and super effective way of writing.
Delighted to have fucking incurious proud illiterates playing AI whisperer.
I hope you step on a lego em-dash in the dark.
With v258 we are adding a 4th reason to declare directories like this:
4. There is now StateDirectoryAccounting= and StateDirectoryQuota= for accounting disk usage per-service, and for enforcing limits on it. (similar options for the other two dirs exist too)
These fields can be set during runtime via "systemctl set-property". They are implemented via new-style "quota project IDs", which are fully automatically managed (i.e. no need to patch around in /etc/projid), …
Yes, a file full of zero bits transfers faster over USB2.0 than a file full of one bits.
I've known this forever but it still feels ridiculous when you actually test it and it's true!
USB truly is cursed.
A poorly kept secret is that the X11 graphics stack is under-maintained as resources shift towards the maintenance of Wayland’s graphics stack instead. To some extent, technical steering committees in major distributions have been watching this situation develop for the past few years with increasing concern, as limited maintenance becomes a security risk: bugs accumulate and already burdened distribution security teams have to carry the security maintenance load in an absence of new releases.
Y'all wanna see an excessively cute trick LLVM's optimizer can do?
Swift String contains roughly this method:
```
func _fastCStringContents() -> UnsafePointer<UInt8> {
if isASCII {
return contentsPointer
}
return nil
}
```
Where `isASCII` is defined as `(flags & 0x8000_0000_0000_0000) != 0`
Would you expect this to generate (solution in reply)