> > i'm also seeing this, and the solution was to comment
> > out the (identity ...) field of my machine-ssh-configuration.
>
>
> i spoke too soon. today it's again broken for me the same way, even
> though identity is commented out. lechner on IRC also reported that
> it's broken for him.
since
> i'm also seeing this, and the solution was to comment
> out the (identity ...) field of my machine-ssh-configuration.
i spoke too soon. today it's again broken for me the same way, even though
identity is commented out. lechner on IRC also reported that it's broken for
him.
random hint, maybe
i'm also seeing this, and the solution was to comment out the (identity ...)
field of my machine-ssh-configuration.
maybe my id_ed25519 key is not supported?
it seems to be able to talk to the target and even installed some stuff into
its store, and only dies when it's already deep into the pro
