putty

I'm using Twisted to implement a server, of sorts. When I test it, the first line it receives is always strange: Starting Server... New connection from 192.168.1.140 192.168.1.140: ÿûÿû ÿûÿû'ÿýÿûÿý\NAME Blurr 192.168.1.140: \NAME Blurr (for both inputs I sent \NAME Blurr .) This is the code that prints the input: def lineReceived(self, line): print "{0}: {1}".format(self.name, line) I'm connecting via Putty through Telnet to a remote host. Is this a telnet protocol I'm missing, or what? When I use Unix's telnet program and connect locally, the first line is fine. You can find an explanation of

I have a git repository that I pull using a path similar to this: git pull ssh://username@host.com:1234/path/to/repository.git When GitExtensions then tries to pull from the repo using plink, it makes this call: plink -T username@host.com:/path/to/repository.git This ends up failing because it's actually pinging port #22, and not #1234. The right call to make would be plink -T -P 1234 username@host.com:/path/to/repository.git If I create an alias "hostCom" in my ~/.ssh/config, it seems to work correctly (connecting to #1234) if I just do this: plink -T username@hostCom But as soon as I add the

Excited about being ready to do my first git push ever, I created an alias for PuTTY in my cygwin environment: alias ssh="/cygdrive/c/PROGRA~2/putty/PUTTY.EXE" Then invoked (inside my working directory, of course), just as explained in page 47 in the git community book : git push ssh://mylinuxserver/~winwin/gitrepo master:master My excitement didn't last very long, as it immediately failed with a fatal error: error: cannot run ssh: No such file or directory fatal: unable to fork Considering that I am able to run successfully, from the same exact command line and shell instance , ssh winwin

备份 PuTTY 的设置 用 PuTTY 最不爽的就是，它把所有的设置都保存到注册表了，本来这不是什么问题。但是难免会重装一下机器，用下面的命令可以备份 PuTTY 的所有设置 regedit /e PuTTY.config.reg "HKEY_CURRENT_USERSoftwareSimonTathamPuTTY" 删除 PuTTY 的设置 如果只是在其他机器上临时用了一个 PuTTY，用完以后想删除 PuTTY 的配置，就在控制台里输入如下的命令： putty.exe –cleanup 用 PuTTYgen 来生成密钥，以后可以不用密码登录服务器了 PuTTYgen 是密钥生成器，用来生成一对公钥和私钥供 PuTTY、PSCP、Plink、Pagent 来使用。直接运行 PuTTYgen 可以看到如下的界面。 点击 Generate 按钮就开始生成一个公钥和私钥对，生成完毕后，点下面的 Save private key 就可以把私钥保存起来，扩展名是 .ppk 的文件。Load 按钮可以把先前保存的私钥重新打开，然后做些修改，比如修改注释和私钥口令，或者把 PuTTY 格式的私钥转换为OpenSSH 格式的。 开始用 PuTTYgen 创建密钥 单击 Generate 按钮，然后你会看到进度条上面有个提示“Please generate some radomness by

用 SSH 来传输文件 PuTTY 提供了两个文件传输工具 • PSCP (PuTTY Secure Copy client) • PSFTP (PuTTY SFTP client) PSCP 通过 SSH 连接，在两台机器之间安全的传输文件，可以用于任何 SSH（包括 SSH v1、SSH v2） 服务器。PSFTP 则是 SSH-2 中新增的特性，使用的是新的 SFTP 协议，使用上与传统的 FTP 类似。事实上 PSCP 如果发现 SFTP 可用，PSCP 就会使用 SFTP 协议来传输文件，否则还是 SCP 协议。PSFTP 与 PSCP 相比，PSFTP 的优点是可以与服务器进行交互，遍历服务器上的文件系统，在一个会话中上传或下载多个文件。而 PSCP 只能一次传输一个文件，传输完毕后立刻终止会话。 PSCP 的使用 在控制台直接执行 pscp 可以看到帮助 C:>pscp PuTTY Secure Copy client Release 0.58 Usage: pscp [options] [user@]host:source target pscp [options] source [source...] [user@]host:target pscp [options] -ls [user@]host:filespec Options: -V print

为了兼顾客户端和服务器的开发，同时需要使用windows和linux，那么ssh至服务器总是不错的选择，那么一款合适的ssh软件和相对应配置此时就体现出它的价值来了。废话不多说，开门见山，直奔主题。; 一． 主菜：putty 曾经用过SecureCRT，恩，两个字，不爽，这个纯属个人爱好。我的软件理念就是能不用收费就不用收费，不行就用破解，绝对不去缴费。相对于 CRT，putty小巧（几百K和几M的区别，啧啧）免费，默认色彩也挺不错的（不过个人不能忍），配置简单，界面干净清爽，十分适合写代码。相对 的，SecureCRT就显得复杂和臃肿，配置那个繁琐啊。 java集合对象排序 主要的几个Putty设置。其实原封不动的putty（也就是default）已经不错了，不过既然把putty当终端在用的话么，一些锦上添花的东东还是不错的。 1. Window -> Lines of scrollback 这里是设置窗口buffer的，一般我设置1W行，这样就能回滚查看自己的命令了。 2. Window -> translation: 选择编码方式为utf-8，作为通用编码方式，不解释。 3. Window -> colours顾名思义，这里就是设置你的putty色彩了，按个人喜好设置就好。 4. Connection -> Seconds between keepalives

I am using Plink to run a command on remote machine. In order to fully automate the process I need to save the execution log somewhere. I am using a bat file: C:\Ptty\plink.exe root@<IP> -pw <password> -m C:\Ptty\LaunchFile.txt The C:\Ptty\LaunchFile.txt contains my command that i want to run. ./Launch.sh jobName=<job name> restart.mode=false Is there a way to save the execution log so that I can monitor it later... ? Martin Prikryl The plink is a console application. Actually that's probably it's only purpose. As such, its output can be redirected to a file as with any other command-line

I have a .bat file on my Windows machine. This .bat file uses plink.exe to connect to an Ubuntu machine and execute an .sh script. However, I get different behaviors on the script depending on how Plink is used: log onto Ubuntu directly (in person) -- script succeeds ssh via Bitvise client -- script succeeds ssh via Plink (by calling plink.exe ) and calling script from interactive shell (it's a Ubuntu shell within windows cmd.exe ) -- script succeeds ssh via .bat which then calls Plink -- script fails The script fails w/ message: error while loading shared libraries: libCint.so: cannot open