Yes, this is a know problem caused by the 20181029 snapshot. I’ve been following that bug report. It looks as if they are close to a solution.
My own workaround was to revert to the previous “openssh” version. But it might be fixed soon enough that it’s not worth doing that now – especially if they put the fixed package in the update repo so that it is available without waiting for a new snapshot.
Thanks for all the replies, it was that “known” problem, that costed me some hours of my life But it is solved, because there is a correction via online update. Thanks for your help and and all your replies. You helped me not to waste more hours of my life .