- html - 出于某种原因,IE8 对我的 Sass 文件中继承的 html5 CSS 不友好?
- JMeter 在响应断言中使用 span 标签的问题
- html - 在 :hover and :active? 上具有不同效果的 CSS 动画
- html - 相对于居中的 html 内容固定的 CSS 重复背景?
如何配置 SSHD 以在 Docker 中运行?我正在尝试编写一个单元测试来检查一些 SSH 登录命令,但我无法让容器通过 SSH 登录到自身。
我有 Dockerfile:
FROM ubuntu:18.04
ENV PYTHONUNBUFFERED 1
USER root
RUN apt-get -yq update --fix-missing && apt-get -yq install sudo
# Enable Supervisord/SSH.
RUN apt-get -yq update && apt-get install -yq openssh-server supervisor
RUN mkdir -p /var/run/sshd /var/log/supervisor
COPY supervisord.conf /etc/supervisor/conf.d/supervisord.conf
EXPOSE 22 80
COPY ./id_rsa.pub /home/ubuntu/.ssh/authorized_keys
RUN chmod og-wx /home/ubuntu/.ssh/authorized_keys
# Install code.
RUN mkdir -p /myproject
COPY . /myproject/
WORKDIR /myproject
CMD ./runtest.sh
runtest.sh
同时启动 SSHD 和我的测试命令,例如:
#!/bin/bash
set -e
echo "Starting Supervisord..."
/usr/bin/supervisord &
sleep 5
echo "Running tests..."
ssh -o "StrictHostKeyChecking=no" -i ./id_rsa ubuntu@localhost echo 'hello world'
echo 'Tests run!'
Starting Supervisord...
Running tests...
/usr/lib/python2.7/dist-packages/supervisor/options.py:298: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
'Supervisord is running as root and it is searching '
2019-11-25 20:23:56,060 CRIT Supervisor running as root (no user in config file)
2019-11-25 20:23:56,067 INFO supervisord started with pid 8
2019-11-25 20:23:57,071 INFO spawned: 'sshd' with pid 12
2019-11-25 20:23:58,073 INFO success: sshd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts.
Permission denied, please try again.
Permission denied, please try again.
ubuntu@localhost: Permission denied (publickey,password).
OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: resolving "localhost" port 22
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to localhost [127.0.0.1] port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: SELinux support disabled
debug1: key_load_public: No such file or directory
debug1: identity file ./id_rsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file ./id_rsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH* compat 0x04000000
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to localhost:22 as 'ubuntu'
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent
debug3: receive packet: type 20
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,ext-info-c
debug2: host key algorithms: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-ed25519-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib@openssh.com,zlib
debug2: compression stoc: none,zlib@openssh.com,zlib
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug2: peer server KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1
debug2: host key algorithms: ssh-rsa,rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib@openssh.com
debug2: compression stoc: none,zlib@openssh.com
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug3: send packet: type 30
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug3: receive packet: type 31
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:suhccUuYtkjZxG1IWq4nvKlLIQ9i6IcLBG16c4+Fhmk
Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts.
debug3: send packet: type 21
debug2: set_newkeys: mode 1
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug3: receive packet: type 21
debug1: SSH2_MSG_NEWKEYS received
debug2: set_newkeys: mode 0
debug1: rekey after 134217728 blocks
debug2: key: ./id_rsa ((nil)), explicit
debug3: send packet: type 5
debug3: receive packet: type 7
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521>
debug3: receive packet: type 6
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug3: send packet: type 50
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey,password
debug3: start over, passed a different list publickey,password
debug3: preferred gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Trying private key: ./id_rsa
debug3: sign_and_send_pubkey: RSA SHA256:sGFbfZpSWfA5zo84FcTlI5SHR0DKGlQmGROFlnhKVsE
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
Connection closed by 127.0.0.1 port 22
key_load_public: No such file or directory
表示它找不到 id_rsa key ,虽然我不确定为什么,因为它 id_rsa 和 id_rsa.pub 肯定存在于 CWD 中并且具有正确的权限。
最佳答案
从错误消息中不清楚,但问题是我的 ssh 命令(ubuntu)中的用户与 Docker 容器中的用户(root)不匹配。一旦我匹配了它们,我就可以 ssh 进入容器。
关于docker - 如何在 Docker 容器中启动 SSHD,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/59039607/
从我在 Linux 上的测试来看,似乎是 服务 sshd 重新加载 仅在 sshd 已运行时有效 如果 sshd_config 文件有问题,则停止 sshd 即使 sshd_config 文件有问题也
关闭。这个问题不符合Stack Overflow guidelines .它目前不接受答案。 这个问题似乎不是关于 a specific programming problem, a softwa
sshd 限制登陆的几种方法总结 1. 在 /etc/hosts.allow 写: ?
我正在尝试构建一个ssh服务以允许推/拉到phabricator仓库。我已经对所有服务进行了docker化,并且当前遇到了一个奇怪的错误,该错误无法执行ssh所需的身份验证脚本。 docker镜像同时
好的,我想到了这个,并且很好奇它是否可能。在 linux 系统上,有什么方法可以生成有效的算法密码组合来登录 SSH,我们可以用一个小的应用程序或设备生成有效的密码(比如一些银行的互联网界面,如果你愿
我的情况是 sshd 应该只允许 sftp 访问一组用户。 这很容易通过添加一个匹配部分来完成 Match Group groupname ChrootDirectory /srv/ftp
我正在尝试构建一个 hadoop Dockerfile。 在构建过程中,我添加了: && apt install -y openssh-client \ && apt install -y o
有没有办法运行sshd以便它可以(至少对于有限数量的登录)成功返回提示(可能是 busybox),即使 fork 不可用(例如,PID 不足)? 在我看来,这应该是可能的,例如,sshd 预 fork
由于/var/log/secure 中的以下错误(根据调试日志),我无法登录 SSH: Dec 19 18:01:05 hostname sshd[25119]: debug1: trying pub
谁能给我指出一些使用 SSHD 访问服务器并从 JAVA 应用程序执行一些命令的示例代码。我浏览了 Apache SSHD 网站和下载,但就文档和示例代码而言,还没有发现任何有用的东西。我还用谷歌搜索
我在 ubuntu 上遇到 SSHD 问题。我试图通过使用 AllowGroups 来限制可以远程登录的帐户,从而在 SSH 服务器上提供更强大的安全性。不幸的是,不在允许组中的用户似乎仍然可以登录并
我正在尝试安装 hadoop,我需要重新启动 sshd 服务以配置节点之间的连接...但是,每当我写:service sshd restart 消息错误将显示告诉我此服务无法识别。 安装这个系统有什么
我正在尝试获取服务器的公钥。这是我尝试过的: val serverKey = sshClient.connect("dyn mem", "localhost", "2222") .verify()
关闭。这个问题是off-topic .它目前不接受答案。 想改进这个问题吗? Update the question所以它是on-topic用于堆栈溢出。 关闭 10 年前。 Improve thi
1,服务器链接不上 ? 1
我正在尝试关注 Apache MINA 的 guide用于设置 SSHD 服务器,但在使用 PuTTY 连接到它时遇到问题。我开始输入用户名,但随后收到以下错误消息: 下面是我的服务器的代码。我是否必
我找到了这个 Dockerfile sample here : // version 1 FROM ubuntu:latest RUN apt update && apt install ssh -
如何配置 SSHD 以在 Docker 中运行?我正在尝试编写一个单元测试来检查一些 SSH 登录命令,但我无法让容器通过 SSH 登录到自身。 我有 Dockerfile: FROM ubuntu:
我有一个docker容器,需要使用-d标志作为守护进程运行。 有没有办法指定我要运行/ usr / sbin / sshd作为此容器的启动过程? 我已经尝试过了,但是我的容器没有停留在周围: 须藤 j
我目前正在制作一个简单的安全审计脚本,它将为配置中的每个不匹配打印 OK/Error。 场景是下一个 - 例如,对于 SSHD_Config,如果情况下,我会放在下一个: if [ "`grep -E
我是一名优秀的程序员,十分优秀!