Comment 3 for bug 2059874

> For me the biggest problem was the socket unit beeing re-enabled when I had it disabled it but still running sshd.service (ie without socket activation) - now you're unexpectidly switched back to using socket activation - something I explicitly opted out of.

Okay. We could probably adjust the check to ignore migration if the user is upgrading from kinetic or newer and has ssh.socket disabled.

> I could also see this causing problems if you have the socket unit masked (dont see why you would want that however) but the the service is enabled, now you are without sshd. Actually I think the postinst would also fail in that case, as systemctl enable fails enabling masked units.

This is a good point as well.