Wednesday, June 24, 2015

Prevent TortoiseCVS from converting LF to CRLF in checkout


If you have used a UNIX-like CVS client to check in a file, and the file has CRLF at the end of each line -- that means the file is in DOS format, when you check out the file with TortoiseCVS, the file will have CRCRLF at the end of each line.

That is because when TortoiseCVS checks out the file, it converts LF to CRLF for each line by default.

We can make TortoiseCVS stop this behavior by using an option during the checkout:
  • On an Windows Explorer, right click and choose menu CVS Checkout...
  • The TortoiseCVS - Checkout Module dialog is shown.
  • Select the Options tab on the dialog.
  • At the bottom, check the Use UNIX line endings checkbox.
  • Continue the checkout process and the files will be checked out without the LF to CRLF conversion.

Saturday, June 20, 2015

Copy files from local drive to remote desktop


In order to copy files from the local drive to the remote desktop or vice versa, we make the local drive available as a network drive on the remote desktop. To do that, follow these steps when logging in to the remote desktop.

  • On Windows Start menu, select All Programs -> Accessories -> Remote Desktop Connection.
  • On the dialog, click on the Options button.
  • Select the Local Resources tab.
  • Click the More... button at the bottom Local devices and resources section.
  • On the new dialog, expand the Drives item.
  • Select the drives we want to be visible to the remote desktop. Click OK button to close the dialog.
  • Click Connect button to login to the remote desktop.
  • After login, the local drive can be found at the Network place on the remote desktop. We can drag and drop files from or to it.



Sunday, June 14, 2015

Free SSH Servers for Windows


KpyM Telnet/SSH Server

KpyM Telnet/SSH Server is open source. It uses the BSD license.

The downlaod URL is http://www.kpym.com/2/kpym/download.htm and the license can be viewed there.

There is not GUI interface for it. Neither a GUI configuration.

The password authentication is straightforward but the public key authentication is somehow strange. How to use the public key authentication is described in their forum. You need to add the public key into a configuration file c:\program files\kts\publickey_logon.ini. And you also need to write the login credentials (username and password) together with the public key. It seems the software does not really do the public key authentication. Instead, it uses the public key to find the password in the configuration file and authenticate the user with the password. The big problem is that the password must be in clear text in the file.

Copssh free version

Copssh comes with a free version and a commercial version. The free version can be downloaded at https://www.itefix.net/content/copssh-free-edition.

The free version does not support Windows Server. And it allows only one local user.

It has a GUI for the configuration. You can add users there and set up public key authentication etc.

freeSSHd

freeSSHd can be downloaded from http://www.freesshd.com/?ctt=download. Although it is free to use, the source code is not free.  The license information is found here http://www.freesshd.com/?ctt=terms.

A step by step installation and configuration document can be found on IBM's: ftp://ftp.software.ibm.com/software/iea/content/com.ibm.iea.wpi_v6/wa/6.2/FTP/WBPMv62_IEA_AdapterInstallConfigureSSHServerLab.pdf.

It has a GUI setup and we can also use the public key authentication. They are all written in detail in IBM's document.

Their website promotes a commercial product with source code, which they claim contains the source code of freeSSHd.

 
Get This <