

Encryption lengths are getting long so you’d think it was high time.
that’s unrelated - AES-256 for example can be executed just fine on either a 32- or 64-bit machine. in theory there’s nothing stopping you from running it on an 8-bit or 16-bit CPU (although other considerations related to the size of AES’s lookup tables make this unlikely). from some random googling, here is an implementation of Chacha20, another 256-bit encryption algorithm, for 8-bit microcontrollers.
when we talk about 32 vs 64-bit CPUs, in general we’re only talking about the address space - the size of a pointer determines how much RAM the computer is able to use. 32-bit machines were typically limited to 4GB (though PAE helped kick that can down the road)
CPU registers can also be sized independently of the address space - for example AVX-512 CPUs have a register that is 512 bits wide even though the CPU is still “64-bit”.
congrats to HP on the launch of their new “you thought inkjet printers were shitty now? hold my aquifer and watch this” division.
but also:
this is a relatively cheap way for HP to set itself up as an AI patent troll and extract rent from other companies that are trying to do AI-related bullshit. (from 2017: Stupid Patent of the Month: HP Patents Reminder Messages)