Re: buster ssh problem
On Wed, Nov 1, 2017 at 12:47 AM, Sven Hartge <firstname.lastname@example.org> wrote:
> There are. Both sides exchange a symmetric session key to use for the
> connection. The public/private key which can be used with SSH has
> nothing to do with this.
Yeah. That what I thought it was all about -- the login keys.
> What do you mean? Just create ~/.ssh/config and put a Host statement
> like above inside it.
No prob, and will do. I'm used to ssh creating files in config
directories for me.
> No, this is not the solution, as this will a) set this for every
> connection and b) restrict the Cipher list to *only* this insecure
> Please read "man ssh_config". The Ciphers statement recongnizes + and -
> as prefixes to add or remove values without replacing the whole setting.
17 pages long. But will wade through it...