Bug#991797: the distributed ssh_config
looks like this: *# Site-wide defaults for some commonly used options. * For a comprehensive # list of available options, their meanings and defaults, please see the # ssh_config(5) man page. #Include /etc/ssh/ssh_config.d/*.conf Host * # ForwardAgent no # ForwardX11 no # ForwardX11Trusted yes # PasswordAuthentication yes # HostbasedAuthentication no # GSSAPIAuthentication no # GSSAPIDelegateCredentials no # GSSAPIKeyExchange no # GSSAPITrustDNS no # BatchMode no # CheckHostIP yes # AddressFamily any # ConnectTimeout 0 # StrictHostKeyChecking ask # IdentityFile ~/.ssh/id_rsa # IdentityFile ~/.ssh/id_dsa # IdentityFile ~/.ssh/id_ecdsa # IdentityFile ~/.ssh/id_ed25519 # Port 22 # Ciphers aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc # MACs hmac-md5,hmac-sha1,umac...@openssh.com # EscapeChar ~ # Tunnel no # TunnelDevice any:any # PermitLocalCommand no # VisualHostKey no # ProxyCommand ssh -q -W %h:%p gateway.example.com # RekeyLimit 1G 1h *# UserKnownHostsFile ~/.ssh/known_hosts.d/%k* SendEnv LANG LC_* HashKnownHosts yes GSSAPIAuthentication yes And without changing this default ssh looks into the non-existing directory *~/.ssh/known_hosts.d/%k!* There is another bug in the default settings: Without adding "hmac-sha2-256" this way "MACs hmac-md5,hmac-sha1,hmac-sha2-256,umac...@openssh.com" ssh does not connect to any of my own sshd servers on Debian 10, Ubuntu 18.04 and 20.04 and Oracle Linux 8. This change I have to make for this openssh-client on Debian 11 only. This bug needs to be reopened. FMF **
Bug#991797: openssh-client: UserKnownHostsFile default wrong
Package: openssh-client Version: 1:8.4p1-5 Severity: important Dear Maintainer, The default setting of UserKnownHostsFile has changed in this version to: ~/.ssh/known_hosts.d/%k But existing former versions have placed it in: ~/.ssh/known_hosts This renders ssh connections impossible, unless I change it back to the former default by adding to ssh_config: UserKnownHostsFile ~/.ssh/known_hosts ~/.ssh/known_hosts2 Regards, FMF -- System Information: Debian Release: 11.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/2 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openssh-client depends on: ii adduser 3.118 ii dpkg 1.20.9 ii libc6 2.31-13 ii libedit2 3.1-20191231-2+b1 ii libfido2-1 1.6.0-2 ii libgssapi-krb5-2 1.18.3-6 ii libselinux1 3.1-3 ii libssl1.1 1.1.1k-1 ii passwd 1:4.8.1-1 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages openssh-client recommends: ii xauth 1:1.1-1 Versions of packages openssh-client suggests: pn keychain pn libpam-ssh pn monkeysphere pn ssh-askpass -- Configuration Files: /etc/ssh/ssh_config changed: Include /etc/ssh/ssh_config.d/*.conf Host * UserKnownHostsFile ~/.ssh/known_hosts ~/.ssh/known_hosts2 SendEnv LANG LC_* HashKnownHosts yes GSSAPIAuthentication yes -- no debconf information
Bug#920957: workaround
The workaround for this display disturbing issue: unplug the USB mouse while working in the command line console, plug it back in when using X. Regards, Michael
Bug#920957: linux-image-4.9.0-8-amd64: USB HID devices disconnect and reregister frequently - correction
After more testing here is my correction and additional info: * The issue shows with 4.19.0-0.bpo.1-amd64, too, just less often. * With 4.19.0-0.bpo.1-amd64 it shows only when using command line. Using keyboard and mouse with X produces no disconnects. Using a console under X (CTRL-ALT-F1), however, gives me frequent disconnects again. Annoying, because the disconnect messages pop up in the middle of text I am keying into the console. * With 4.19.0-0.bpo.1-amd64 the disconnect happens with mouse only, never with the keyboard in use. Regards, Michael kern.log.gz Description: GNU Zip compressed data
Bug#920957: linux-image-4.9.0-8-amd64: USB HID devices disconnect and reregister frequently
Yes, the issue remains with kernel version 4.9.144-2. Regards, FMF Am 2019-01-30 23:35, schrieb Salvatore Bonaccorso: > Hi Michael, > > On Wed, Jan 30, 2019 at 11:02:30PM +0100, Michael Fischer wrote: > >> Package: src:linux >> Version: 4.9.130-2 >> Severity: important >> Tags: upstream >> >> Dear Maintainer, >> >> Having USB keyboard and/or USB mouse connected leads to the problem. >> Same is true on three other systems, running 686-pae or 686 with the >> same kernel version Installing linux-image-4.19.0-0.bpo.1-amd64 >> fixes the problem reliably. Also in case of 686 or 686-pae kernels > > Can you confirm, does the issue still persist as well with the > 4.9.144-2 version currently pending in proposed-updates (and to be > included in the next point release)? > > Regards, > Salvatore
