aaronmdjones

MCUs refers to all sorts these days.

For example, the RP2350 is a $1 MCU that includes 2x ARM Cortex-M33 cores or 2x Hazard3 RISC-V cores running at 150 MHz.

The RISC-V cores have M-mode and U-mode, and a Physical Memory Protection unit.

The ARM cores have a Security Attribution Map and an Implementation-Defined Attribution Unit which tags accesses to devices like GPIO/PWM/ADC/... based on the security level of the code performing that access. It also has 2 Double-Precision Coprocessors for each ARM core, one for secure and one for non-secure code. It also has secure boot support if you run its cores in ARM mode.

TLS uses TCP, and TCP has checksums and retry logic. It therefore assumes any data corruption that made it all the way to the TLS layer is an unrecoverable scenario, probably indicative of an attack.

The problem here is that the thing computing the TCP checksum on the outgoing frame was the WLAN firmware running on the WLAN NIC itself; this is known as checksum offloading. It saves CPU time if the CPU can just hand off a TCP segment to the NIC and let the NIC checksum it before it sends it out. This only works properly if the data given to the NIC doesn't get corrupted in the meantime.

I'd hazard a guess that it's because Starlink service is denied in Russian territory and not denied in Ukrainian territory, and provides a way for Ukrainian citizens to remain informed and connected to their communities even with the Russian onslaught on their power and communications infrastructure.

The UK has Dinorwig power station, a pumped hydro station capable of storing over 9 GWh of energy. This alone rivals the entire combined 10.5 GWh of battery storage across the whole country. It certainly seems much more feasible when you have the terrain to allow it.

Some of their customers have even asked them to redesign their cameras so they don't look like Flock cameras.

No. Your calculated landing speed doesn't change depending on the winds, so you'll always be touching down at roughly the same airspeed for the same aircraft type, weight, and flap setting. Touching down with a headwind just means you don't need to use the brakes as hard.

It's beneficial on takeoff because headwind already factors into your airspeed before you even start rolling, which gives you more lift for the same groundspeed yes, enabling you to rotate sooner than you otherwise would.

That they passed their minimums and still weren't set up correctly is shocking, yes. How can you commit to landing instead of going around when you're not configured for landing?

The more egregious thing to me though is ignoring the GPWS callouts on approach because they were chasing the glideslope. If you can't maintain a stable approach, you need to go around, it's the first thing you learn.

You expect this behaviour from a first-timer in the sim, not a commercial cargo pilot.

This is true for takeoffs but not for landings. You want to land with a headwind because this means that for the same airspeed you have a lower groundspeed, i.e. when you actually touch down you're going slower on the runway than if you touched down at the same airspeed but with a tailwind.

> (unclear how speed didn't increase)

Large high-bypass turbofan engines take several seconds to spool up from idle (as they would be on landing) to full thrust. The 4 seconds that the thrust levers spent in the full thrust position in this accident was not long enough.

RSA operations are performed modulo n, where n is the product of 2 primes. A 2048-bit RSA key is an n that is 2048 bits long (with the most significant bit set by definition).

There are no consumer CPUs that have 2048-bit-wide registers; even AVX10 tops out at 512 bits. Thus, mathematical operations on RSA keys are performed using arbitrary precision integer libraries like OpenSSL's own BN (BigNum) library, or GMP (the GNU Multiple Precision Arithmetic Library) as used by GNUTLS, in software.

For example, adding 1 to an arbitrary precision integer is not a CPU add or increment instruction, nor is multiplying 2 integers (or an integer and a constant factor) a CPU multiplication instruction.

Sort of. Rolls Royce voluntarily developed this software modification in response to learning that their reasoning about it never being able to happen was incorrect and being unable to concretely account for how it happened. EASA, which was not even the relevant safety authority for this incident, upon learning of its existence, only then required it to be installed on all A380 Trent 900 engines.

The thing visible on the bus is the interface chip, not the sensor. Most cameras which I've seen hardwire their activity LEDs (it is impossible to grab stills or record video without lighting up the LED) do so by connecting the activity LED to the sensor power rail. With the sensor powered off, the device is still visible on the bus but you get no usable image data.