You can review the changes for 6.44.4 and 6.44.5 to determine if any of them will affect you?So i also can go from 6.44.3 (stable) to 6.44.5 (LT) without any major changes/problems ?
Yes strong-crypto=yes was already set.You have set strong-crypto=yes? I think it depends on that setting.I noticed that after upgrade from 6.43.16 to 6.44.5, allow-none-crypto=yes was set in /ip ssh. This seems to be a new setting and is documented as defaulting to no.
!) radius - use MS-CHAPv2 for "login" service authentication;
PCI DSS Requirements
8.1.8 If a session has been idle for more than 15 minutes, require the user to re-authenticate to re-activate the terminal or session.