I can confirm that e.g. there has definitely been e.g. a batch of enterprise SSDs from Intel a couple years ago which failed en masse after a certain amount of powered-on time.
they appear to be bragging about 12GiB/s of aes-256-gcm per crypto accelerator. This is equivalent performance to about 2.6 cores of epyc milan, but let's be generous and say 3 cores. At retail, 3 cores of epyc milan costs $240-$360. How much does one of those crypto accelerators cost?
Though there are attempts underway to do inline signing of JWT (https://datatracker.ietf.org/doc/draft-jordan-jws-ct/), though that's still not nearly as bad as XML-DSIG of course. I'm sure some vulns will shake out of it.
You'll have to write some glue code, but if all you need is standard Ed25519 signatures, current-gen Yubikeys can do this. Somebody's implemented a python library that does that here https://github.com/tschudin/sc25519
Yup; you could do every minute with no real problems if you like. I believe you start to run into performance issues with high (1000+) snapshot counts, and then mostly when actually doing snapshot operations, so you'd want to have something to trim snapshots so you only keep your minutely snapshots for an hour and so forth.
If you have to actually compare the files on both ends, however, that's still many more round trips than necessary for zfs send, which is just sending all blocks with a birth time after the previous snapshot
It remains a _delightfully_ straightforward way to do backups; I do incremental zfs send with hourly snapshots to my local NAS and also to an rsync.net ZFS account (https://www.rsync.net/products/zfsintro.html); it's incredibly resource un-intensive relative to your traditional scan-everything backup methods and I can trivially mount a past snapshot for browsing or spot restore or just do zfs send on the whole thing for catastrophic recovery.
> for example you can't create a kubernetes cluster then add a resource to it
I have no love for HCL, but you can do this by creating a kubernetes provider with the auth token pointing at the resource output for the auth token you generated for the cluster.
yeah, funny how antivirus software would complain about the website of somebody known, among other things, for demonstrating a lot of security flaws in antivirus software.
I'm fairly confident the nodes are half width; if you look at the latches it very much would appear you can pull out half of every 2u at once, and if you look at the rear there's 2 net cables going into each side.
See also the (compatible, same middle server by default) golang port, https://github.com/psanford/wormhole-william, complete with static binaries for mac/win/linux. I've found this helpful when I've needed to send files to somebody who would have problems getting a whole pythonpile of dependencies installed.
Go is extremely easy to cross-compile, but adding C libraries will mean you also need a C cross-compiler (and the various go headers & libs for CGO built for that platform)
Do you, realistically? The standard behavior for most things afaik on looking up a domain name is to send out an A query and (simultaneously ideally) A queries with searchdomains appended. That's not gonna get anywhere near 512 bytes for a fly .internal service name, I'd expect.
sure, but that's why BPF is so great; I'd guess a reasonable program that assumes port 53, parses the packet enough to look at the first question and compare domain against .internal and then rewrites address + updates checksum is maybe... 300-400 LOC? can probably get a bit fancier, but it shouldn't be too painful to write and will execute plenty fast enough.