openssh

Git配置了秘钥认证后,tortoisegit仍需要认证的问题

余生颓废 提交于 2019-12-05 11:51:31
github和gitee都支持ssh秘钥配置,配置完毕后使用命令行就可以直接访问仓库而不用每次都输入密码,但是如果你安装了Tortoisegit的话,会发现配置的SSH对他无效。 这是因为TortosseGit默认使用putty格式的私钥,而git默认使用的是OpenSsh格式的私钥。 如果想使用同一ssh私钥,TortosseGit提供了这个功能,右键,打开TortosseGit的setting。将network中的ssh-client改为git目录下的ssh.exe即可 来源: oschina 链接: https://my.oschina.net/u/2745108/blog/3030683

搭建跳板机

偶尔善良 提交于 2019-12-05 09:57:16
什么是跳板机? 首先,贴一段跳板机的介绍。 跳板机属于内控堡垒机范畴,是一种用于单点登陆的主机应用系统。跳板机就是一台服务器,维护人员在维护过程中,首先要统一登录到这台服务器上,然后从这台服务器再登录到目标设备进行维护。但跳板机并没有实现对运维人员操作行为的控制和审计,此外,跳板机存在严重的安全风险,一旦跳板机系统被攻入,则将后端资源风险完全暴露无遗。 对于个别资源(如telnet)可以通过跳板机来完成一定的内控,但是对于更多更特殊的资源(ftp、rdp等)来讲就显得力不从心了。 什么是堡垒机? ... 环境问题 1.需要用到多台服务器测试环境 2.自己的坠机堡垒配置太低,用Vmware开多台服务器就太卡了 3.公司台式配置高,16G 开个6 7台虚拟机还是很OK的 Windows跳板机搭建 1.打开windows的SSH服务 打开设置-->应用和功能-->管理可选功能-->打开安装OpenSSH 服务器 错误 如果无法安装ssh服务端的话,可能是因为之前在服务里面把windows update服务关掉了,先来起来安装完成后再禁用即可 2.配置ssh环境 管理员权限打开powershell Get-WindowsCapability -Online | ? Name -like 'OpenSSH*' 输出结果应该是这样 Name : OpenSSH.Client~~~~0.0.1

How can I run git commands on Windows with SSH verbose mode?

 ̄綄美尐妖づ 提交于 2019-12-05 09:11:48
This is the Windows version of How can I run git push/pull commands with SSH verbose mode? There are times where you just need to debug git's usage of SSH. OpenSSH has a -v flag for verbose output, but how do you get git to use it? How can I run git commands on Windows with SSH verbose mode? If your PATH is correctly set: you don't need OpenSSH-Win64 (ssh is already included in Git) you don't need to specify the full path for SSH You need: set GH=C:\path\to\git set PATH=%GH%\bin;%GH%\usr\bin;%GH%\mingw64\bin;%PATH% Then set GIT_SSH_COMMAND=ssh -vvv You can force git to provide verbose ssh

Sync local and remote folders using rsync from php script without typing password

眉间皱痕 提交于 2019-12-05 08:38:14
How can I sync local and remote folders using rsync from inside a php script without beeing prompted to type a password? I have already set up a public key to automate the login on remote server for my user. So this is running without any problem from cli: rsync -r -a -v -e "ssh -l user" --delete ~/local/file 111.111.11.111:~/remote/; But, when I try to run the same from a PHP script (on a webpage in my local server): $c='rsync -r -a -v -e "ssh -l user" --delete ~/local/file 111.111.11.111:~/remote/'; //exec($c,$data); passthru($c,$data); print_r($data); This is what I receive: 255 And no file

bash: ssh-host-config: command not found

試著忘記壹切 提交于 2019-12-05 07:03:46
Does anyone have ANY ideas what could be causing this. I am on win 7. I have successfully setup everything using this tutorial: http://www.kgx.net.nz/2010/03/cygwin-sshd-and-windows-7/ I am up to this command: ssh-host-config ..but I receive the error in the title. I have searched google and many other places. I cannot find one instance of somebody having this problem. Any ideas? See http://allthingsmarked.com/2006/08/17/how-to-set-up-a-windows-ssh-server-for-vnc-tunneling/ You probably forgot to check the openssh. I forgot this when downloading to a folder using the setup. Don't download all

Why does OpenSSH RequestTTY cause stderr redirected to stdout?

两盒软妹~` 提交于 2019-12-05 01:18:10
问题 When running the same ssh command with -T and -t, any stderr output arrives on stderr vs. stdout, respectively. No pty allocated: ssh -T user@host "echo >&2 foo" 1>/tmp/out 2>/tmp/err Output is written to /tmp/err . With pty allocation: ssh -t user@host "echo >&2 foo" 1>/tmp/out 2>/tmp/err Output is now written to /tmp/out . I somewhat understand that with pty a full pseudo screen is simulated and that the output is in raw mode. The output sent to the screen then are sent via stdout back to

upgrade openSSH 7.2p in ubuntu 14.04

匆匆过客 提交于 2019-12-04 20:11:52
问题 I have a server running Ubuntu 14.04, but I have an issue with PCI requirements. I have installed in my server OpenSSH 6.6p1, then I upgraded it to OpenSSH 7.2p, compiling the code with make and make install directly from repositories from OpenSSH , but it seems something is broken because I continue getting the old version after I check dpkg -l openssh\* : ii openssh-client 1:6.6p1-2ubunt amd64 secure shell (SSH) client, ii openssh-server 1:6.6p1-2ubunt amd64 secure shell (SSH) server, ii

阿里云=>RHSA-2019:1884-中危: libssh2 安全更新

只愿长相守 提交于 2019-12-04 18:40:48
由于项目构建时间比较长,近期安全检查发现openssh有漏洞。所以要升级openssh到7.9p1版本。由于ssh用于远程连接,所以要谨慎操作。 建议生成环境要先做测试,之后再在生产环境升级。 1 前期准备 1.1 依赖安装 1、 OpenSSL版本:目前OpenSSH7.9不支持OpenSSH1.1.x以上。否则编译的时候会报错。 2、 Zlib1.1.4或1.2.1.2或更高版本 3、 gcc:因为编译需要gcc 4、 openssl-devel:编译时需要 1.2 注意事项 1、 前期多打开一个xshell窗口。保证连接正常。因为可能出现升级失败。结束后要确定好再关闭。 2、 备份sshd_config配置文件(方便后期使用或者方便升级失败使用) 3、 最好关闭防火墙,如不关闭防火墙请开启ssh需要的端口和telnet需要的端口。如果ssh不是22端口最好打开22端口。因为ssh配置文件默认22端口。所以建议关闭防火墙。 2、升级之后要重建xshell的session不然会出项下面提示 1 安装telnet 1.1 安装telnet 为防止openssh升级失败。所以安装telnet。保证openssh升级失败也可以通过telnet连接服务器,进行恢复操作。并不用去机房。 #yum install -y telnet-server #yum install -y xinetd

WinSCP之Windows与Windows之间传输文件

旧街凉风 提交于 2019-12-04 17:45:20
WinSCP之Windows与Windows之间传输文件 参考文献:https://winscp.net/eng/docs/guide_windows_openssh_server 方法:WinSCP+ OpenSSH (1)在需要远程访问的windows电脑上安装OpenSSH的server:具体步骤如下: 1. 访问https://github.com/PowerShell/Win32-OpenSSH/releases,下载PC对应的二进制包,如OpenSSH-Win64.zip,并解压到本地; 2. 在C:\Program Files文件夹中新建OpenSSH文件夹,并将(1)中解压的所有文件copy到OpenSSH文件夹中,此处都需要Administrator的权限; 3. 管理员权限运行command,并切换到C:\ProgramFiles\OpenSSH这个文件夹,运行以下命令:powershell.exe -ExecutionPolicy Bypass -File install-sshd.ps1 4. 设置防火墙:Control Panel > System and Security > Windows Firewall >Advanced Settings > Inbound Rules ,右键新建rule,选择port,tcp,固定端口22,Name写sshd

How to ssh on Debian

混江龙づ霸主 提交于 2019-12-04 17:45:01
How to ssh on Debian 1. installation >>> apt-get install ssh PS: This is a convenient way to install both the OpenSSH client and the OpenSSH sever. More details: aptitude show ssh OR: >>> apt-get install openssh-sever openssh-client 2. Generating public/private key >>> ssh-keygen Generating public/private rsa key pair. Enter file in which to save the key (/root/.ssh/id_rsa): Created directory '/root/.ssh'. Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /root/.ssh/id_rsa. Your public key has been saved in /root/.ssh/id_rsa.pub. The