As soon as a volume is decrypted, initrd will write `volume-key` to PCR 15, so any further executables can no longer access the data stored in the TPM.
Of course you cannot unseal the secret from the TPM anymore.
As soon as a volume is decrypted, initrd will write `volume-key` to PCR 15, so any further executables can no longer access the data stored in the TPM.
Of course you cannot unseal the secret from the TPM anymore.
When you're talking about functions operating on mixed, variable length, types, what meaningful logic can you actually apply, that doesn't fall into requiring the types to implement an interface anyway?
When you're talking about struct/classes/etc, what do you need over and above defining a class/record/dataclass? It would seem to me, you're just skipping the part where you give your tuple a name, but is that even a good idea to do?
To be clear, I did not find the examples in the post convincing, as they represent mostly wrappers/adapters for implementing or consuming arbitrary types, but there are no examples for how that might actually be useful downstream.
Imagine each packet requires a size header. When you want to send multiple packets at once, you now want to optimize that and only write a single initial header to the interface, preceding the data.
With variadic generics, you can enable a syntax like `interface.write_packets(packet1, packet2, packet3, /* ... */);` which writes the packets in the desired optimized way. It can internally construct a serializable data tuple from the variadic generics and add the correct header only to the beginning.
Without variadic generics a similar syntax is only possible with macros, which means that it cannot be implemented as a reusable trait.
> It would seem to me, you're just skipping the part where you give your tuple a name, but is that even a good idea to do?
Sometimes you explicitly don't want to require naming the tuple for flexibility, like in the example above.
Oh and none of the involved entities ever acknowledged the leaks. I'd also be highly interested in the rates other people encounter.
If you want higher time resolution, there are several fully integrated hall effect current measurement ICs out there, like for example the ACS723.
If you need even better accuracy or resolution and you can spare 100 bucks, just buy one of the Nordic Power Profiler Kits.
In my ideal utopia I will wear (normal) glasses which include a tiny camera in the frame. When I'm in a gathering of people I would be able to frown or scrunch my nose which would trigger the camera to take an image of the person I'm looking at. The image uploads somewhere where some facial recognition software runs and returns a name to me - possibly in audio form (like a whisper in my ear). The image is not retained, but I would have the information I need to start/continue a conversation with that person without looking like an idiot for not remembering who they were in the first place.
There's barrel-loads of privacy concerns around this ideal utopia of mine. But I'm selfish and fed up with my disability which has, in the past, caused me serious social anxiety.
[1] - Also known as face blindness: https://www.nhs.uk/conditions/face-blindness/
His blog also covers other topics in a similar style - it's a real treasure trove.
[1]: https://github.com/oddlama/nix-topology