From: Peter Board <p_board@hotmail.com>
To: Takashi Yano <takashi.yano@nifty.ne.jp>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Cygwin 3.1.5, 3.1.6 and 3.1.7 builds reporting tty errors with OpenSSH Services in indows Event Logs
Date: Fri, 18 Sep 2020 01:44:53 +0000 [thread overview]
Message-ID: <PSXP216MB032696840E5AAAB9B74EB0219A3F0@PSXP216MB0326.KORP216.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20200918091031.97e86be2a89ecdecc8373c93@nifty.ne.jp>
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
Hi Takashi,
Attached is the ssh_config and sshd_config.
Peter
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
From: Takashi Yano<mailto:takashi.yano@nifty.ne.jp>
Sent: Friday, 18 September 2020 10:10 AM
To: cygwin@cygwin.com<mailto:cygwin@cygwin.com>
Cc: Peter Board<mailto:p_board@hotmail.com>
Subject: Re: Cygwin 3.1.5, 3.1.6 and 3.1.7 builds reporting tty errors with OpenSSH Services in indows Event Logs
On Thu, 17 Sep 2020 22:44:52 +0000
Peter Board wrote:
> F:\cygwin64\bin>cygrunsrv -V -L
> Service : cygsshd
> Display name : CYGWIN cygsshd
> Current State : Running
> Controls Accepted : Stop
> Command : /usr/sbin/sshd -D
> stdin path : /dev/null
> stdout path : /var/log/cygsshd.log
> stderr path : /var/log/cygsshd.log
> Environment : CYGWIN="CYGWIN"
> Process Type : Own Process
> Startup : Manual
> Dependencies : tcpip
> Account : LocalSystem
No suspicious settings other than meaningless
> Environment : CYGWIN="CYGWIN"
Could you please attach /etc/ssh_config and /etc/sshd_config ?
--
Takashi Yano <takashi.yano@nifty.ne.jp>
[-- Attachment #2: sshd_config --]
[-- Type: application/octet-stream, Size: 3103 bytes --]
# $OpenBSD: sshd_config,v 1.103 2018/04/09 20:41:22 tj Exp $
# This is the sshd server system-wide configuration file. See
# sshd_config(5) for more information.
# This sshd was compiled with PATH=/bin:/usr/sbin:/sbin:/usr/bin
# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented. Uncommented options override the
# default value.
#Port 22
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::
#HostKey /etc/ssh_host_rsa_key
#HostKey /etc/ssh_host_ecdsa_key
#HostKey /etc/ssh_host_ed25519_key
# Ciphers and keying
#RekeyLimit default none
# Logging
#SyslogFacility AUTH
#LogLevel INFO
# Authentication:
#LoginGraceTime 2m
#PermitRootLogin prohibit-password
#StrictModes yes
#MaxAuthTries 6
#MaxSessions 10
#PubkeyAuthentication yes
# The default is to check both .ssh/authorized_keys and .ssh/authorized_keys2
# but this is overridden so installations will only check .ssh/authorized_keys
AuthorizedKeysFile .ssh/authorized_keys
#AuthorizedPrincipalsFile none
#AuthorizedKeysCommand none
#AuthorizedKeysCommandUser nobody
# For this to work you will also need host keys in /etc/ssh_known_hosts
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# HostbasedAuthentication
#IgnoreUserKnownHosts no
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes
# To disable tunneled clear text passwords, change to no here!
#PasswordAuthentication yes
#PermitEmptyPasswords no
# Change to no to disable s/key passwords
#ChallengeResponseAuthentication yes
# Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no
# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes
# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication. Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
#UsePAM no
#AllowAgentForwarding yes
#AllowTcpForwarding yes
#GatewayPorts no
#X11Forwarding no
#X11DisplayOffset 10
#X11UseLocalhost yes
#PermitTTY yes
#PrintMotd yes
#PrintLastLog yes
#TCPKeepAlive yes
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#UseDNS no
#PidFile /var/run/sshd.pid
#MaxStartups 10:30:100
#PermitTunnel no
#ChrootDirectory none
#VersionAddendum none
# no default banner path
#Banner none
# override default of no subsystems
Subsystem sftp /usr/sbin/sftp-server
# Example of overriding settings on a per-user basis
#Match User anoncvs
# X11Forwarding no
# AllowTcpForwarding no
# PermitTTY no
# ForceCommand cvs server
[-- Attachment #3: ssh_config --]
[-- Type: application/octet-stream, Size: 1484 bytes --]
# $OpenBSD: ssh_config,v 1.34 2019/02/04 02:39:42 dtucker Exp $
# This is the ssh client system-wide configuration file. See
# ssh_config(5) for more information. This file provides defaults for
# users, and the values can be changed in per-user configuration files
# or on the command line.
# Configuration data is parsed as follows:
# 1. command line options
# 2. user-specific file
# 3. system-wide file
# Any configuration value is only changed the first time it is set.
# Thus, host-specific definitions should be at the beginning of the
# configuration file, and defaults at the end.
# 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.
# Host *
# ForwardAgent no
# ForwardX11 no
# PasswordAuthentication yes
# HostbasedAuthentication no
# GSSAPIAuthentication no
# GSSAPIDelegateCredentials 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-64@openssh.com
# EscapeChar ~
# Tunnel no
# TunnelDevice any:any
# PermitLocalCommand no
# VisualHostKey no
# ProxyCommand ssh -q -W %h:%p gateway.example.com
# RekeyLimit 1G 1h
next prev parent reply other threads:[~2020-09-18 1:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 8:18 Peter Board
2020-09-15 16:22 ` Stephen Carrier
2020-09-15 23:46 ` Peter Board
2020-09-17 16:16 ` Stephen Carrier
2020-09-17 16:51 ` Takashi Yano
[not found] ` <PSXP216MB03268C87FE0C80D06B7A79E99A3E0@PSXP216MB0326.KORP216.PROD.OUTLOOK.COM>
2020-09-18 0:10 ` Takashi Yano
2020-09-18 1:44 ` Peter Board [this message]
2020-09-19 1:18 ` Takashi Yano
2020-09-23 5:45 ` Peter Board
2020-09-24 11:21 ` Takashi Yano
2020-09-24 23:51 ` Peter Board
2020-09-27 4:25 ` Andrey Repin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=PSXP216MB032696840E5AAAB9B74EB0219A3F0@PSXP216MB0326.KORP216.PROD.OUTLOOK.COM \
--to=p_board@hotmail.com \
--cc=cygwin@cygwin.com \
--cc=takashi.yano@nifty.ne.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).