"""The CIS Benchmarks® are prescriptive configuration recommendations for more than 25+ vendor product families. They represent the consensus-based effort of cybersecurity experts globally to help you protect your systems against threats more confidently."""
https://learn.cisecurity.org/benchmarks - this seems broken at least right now. Are these benchmarks on github so that I can download and run it on a linux box?
Do you still have the details details about fixing Windows 11 boot over iscsi?
I love the idea of injecting drivers into windows and did a lot of experimenting along those lines (using WinPE to install drivers offline and edit the registry).
I upgraded my home network and am booting over iscsi using ipxe. My only two remaining issues are:
- Windows 11 25H2 fails to boot since 26200.7019 (and 24H2 since 26100.7019).
- Windows 10/11 S3 sleep+resume does not work with WinOF-2 (mlx5.sys) driver
Everything works well in linux, though!
I am using NixOS. I had to customize the initrd to use iscsistart to connect to the target. It is also important to run iscsid when the system boots to automatically reconnect (which annoyingly takes 10-15 seconds when I resume from sleep). I am using iSER (iscsi over rdma), but TCP worked fine too. I export ZFS zvols on the server over iscsi using targetcli (which configures the in-kernel iscsi target support, sometimes called LIO).
I thought this was pretty cool but the first video didn't play. All this write up and I really just want to see the damn demo in action first! (Edit: reloaded the page and it worked. I still would like to see it on rela hardware!)
> Analog signal processing is clearly less memory than a register, no?
You are going to have a hard time doing analog signal processing with memoryless elements. In the linear domain all you can do is apply gain and mix signals together. If you work with memoryless nonlinearities you can do waveshaping, which is generally only useful when applied to special signals (e.g. sine waves).
Any time you want to do frequency-dependent behavior (filtering, oscillation) you need energy storing elements, usually capacitors, sometimes inductors. A capacitor is just like a register: it stores charge, similarly, inductors store energy in the magnetic field. Needless to say these devices are not memoryless. In fact, since the quantity that they remember is a continuous variable, they store a lot of information.
I would say that there's a difference between simply a stateful circuit using capacitors etc and a digital register, at least in so far as a "hey look what I made" kind of post.
I have no qualms saying a stateful device can have no memory in the addressable memory sense.
> I have no qualms saying a stateful device can have no memory in the addressable memory sense.
I'm not sure where addressable comes in. A digital register is literally a flip-flop (or a bank of flip-flops). It's wired into a larger circuit the same way that a capacitor is.
They're a kind of analogue dynamic memory. I'd hesitate to call them RAM because the Access is not Random, but they are a kind of shift register and early computers used those for RAM.
Imagine a pair of MOSFETs connected to a pair of capacitors, and a bunch of those joined together in a chain. All the gates of each one of the pair of MOSFETS are connected together, giving you a "left" and "right" clock input.
When you put a signal in if you pulse the "left" and "right" inputs, it'll store the signal voltage in one capacitor, then pass it off to the next capacitor in turn, like old-timey firefighter handing buckets of water down a line of people.
They used to use this for delaying audio signals before digital memory and analogue to digital conversion was cheap enough to use.
bucket brigades were also used to read large scale sensors like a CCD camera. they are more efficient in their use of die space because you need fewer data paths; they don't need to be digital either, each bucket can be analog for "grey" scale
Yes, the three playback limit is so annoying. Just... why?! CEC is so stupid. Way overengineered yet completely undercooked. I'm imagining some day soon TVs/receivers will start proxying the CEC bus instead of sharing it globally.
I wrote a program in Golang to control my a/v setup. Included within are small pkgs to control Linux CEC and LIRC devices (ioctl/read/write) as well a pkg for LG TV commands over serial port. Link here: https://github.com/EBADBEEF/tvman
One really useful thing when getting started was to use `cec-ctl -M` to monitor the CEC traffic live. Like the author, I used the v4l-utils commands to interact with CEC but eventually got frustrated with them and rewrote my program in in Go!
I have found CEC to be flaky and hard to work with. I had to turn off CEC on my TV because it breaks everything, almost randomly switching inputs and turning on and off devices.
Did you enjoy Thunderhead even more than Scythe (like I am, 2/3rds done)? Some absolute insanity... poor "Scythe" Tyger's deception!
Book was recommended to me by my now-attorney, after rambling about LLMs enabling commoners access to lawfare during our initial consultation. Despite being "young adult fiction," Shusterman has definitely helped me to better understand my attorney brothers questing their powers [0].
[0] I am an avid reader, 70+ books per year, including all Wallace/Steinbeck/Vonnegut. The Scythe series hits. Just so good. So simple yet complex. Doesn't require thinking to read, but leaves you thinking about what you read.
I meant that they train their system on pictures where they have the underlying medical data. Their system might still be total crap (teehee), but I'm guessing that they at least try to make it predictive/generalized.
There are two issues to consider: security updates and software compatibility.
The LTSC version is good for security updates, but I worry that software could stop supporting Windows 10 despite the LTSC version existing.
Coincidentally I am about to install Windows 10 Enterprise LTSC! I was experimenting (and struggling) with PXE boot with iSCSI. An update broke iscsi boot in Windows 11 25H2 (26200.6901 works, 26200.7019 fails) as well as LTSC (26100.6905 works, 26100.7178 fails). There were other issues with iscsi boot on the LTSC version - the network hardware needs to be enumerated before the first boot, but can't boot because it needs network (a chicken-and-egg style problem).
To expand upon the second issue: I believe Nvidia stopped releasing driver updates for the version of Windows 10 a still supported version of LTSB was based upon at one point leaving users with no further driver updates for a Microsoft supported system. I don't know how common of a problem this is but it did seem to happen once. I also use LTSC but this is a potential pitfall.
"""The CIS Benchmarks® are prescriptive configuration recommendations for more than 25+ vendor product families. They represent the consensus-based effort of cybersecurity experts globally to help you protect your systems against threats more confidently."""
reply