12:34:03 <maledictium> Hi guys. I have a doubt. Whenever there is an update to monero (in this case 0.18.1.1), I always recompile the source code to the new release. My node is on another machine. Should I also move and use the resulting binary for the monerod daemon on the machine running the node?
12:34:49 <grumblemobile> Always best to build on the machine you're running on if you can, unless you know they're the same libwise.
12:35:16 <grumblemobile> But yes, copying binaries is ok too if it's too much hassle (eg, not enough RAM).
12:36:12 <grumblemobile> In general, if it starts on the second machine, it'll be alright.
12:37:22 <grumblemobile> If the second machine is an ARM without HW AES insns, you might get into trouble and need to run with... I forget... some randomx umask env var to disable usage of those.
12:38:01 <maledictium> Yes, they are different versions of debian (stable vs testing) so I will have to recompile due to the lib diferences anyway. My doubt was actually if I could still use the old monerod daemon on the node
12:38:15 <sech1> IIRC that randomx aes thing was fixed in v0.18
12:38:21 <sech1> or even v0.17
12:38:54 <grumblemobile> Old as in previous version ? Not a good idea. New "small number" increases typically fix bugs. Including security ones.
12:39:00 <maledictium> or if it is always a good ideia to run the most recent version of the node in case of security vulnerabilities
12:39:46 <maledictium> grumblemobile: great! It's clarified then. Thanks 
12:40:24 <grumblemobile> sech1: as in, it now detects HW AES at runtime ?
12:46:10 <sech1> yes
12:46:18 <grumblemobile> Nice.